So, I looked into autotools since you mentioned it, and see that it is
autoconf, automake, libtool and gettext in a dist package (
https://www.lrde.epita.fr/~adl/autotools.html)
I had compiled the latest of each of those and my understanding is that
libtool creates "config.sub". Actually, just doing a quick search in my
build-dir, config.sub exists under both share/automake and share/libtool.
When I got tried ./autogen.sh and got "./autogen.sh: 1: cd: can't cd to
/cross-tools/bin/../share/libtool/config", that made me think libtool was
the problem. And when it was followed by ".../subversion/config.guess not
found (try setting the LIBTOOL_CONFIG environment variable)", that had me
instead try "LIBTOOL_CONFIG=/cross-tools/bin/libtoolize ./autogen.sh" which
caused the "config.sub"-mode problem.
When it said it couldn't cd to that config, I thought that was odd and
looked at the install.log I had "make" write to:
/usr/bin/install -c './build-aux/config.guess'
'/cross-tools/share/libtool/build-aux/config.guess'
/usr/bin/install -c './build-aux/config.sub'
'/cross-tools/share/libtool/build-aux/config.sub'
The config stuff is under build-aux. But none of that matters if it's using
the one from libtool which is looking for "mode" as opposed to
share/automake1.99a/config.sub which does not.
(this time, I now am noticing the reply will now go to you and the list. I
can only guess that I never chose reply-to-all before).
On Thu, Apr 3, 2014 at 4:57 PM, Philip Martin <philip.martin_at_wandisco.com>wrote:
> Nathan <naroyce_at_hotmail.com> writes:
>
> >> checking for g++ option to enable C++11 features... -std=gnu++11
> >> checking if g++ -std=gnu++11 accepts -std=c++98... yes
> >> checking if g++ -std=gnu++11 accepts -w... yes
> >> checking if g++ -std=gnu++11 accepts -Werror=unknown-warning-option...
> no
> >> checking how to run the C preprocessor... gcc -std=gnu11 -E
> >> checking for a sed that does not truncate output... /bin/sed
> >> configure: error: cannot run /bin/sh build/config.sub
> >>
> >> "configure:5076: error: cannot run /bin/sh build/config.sub"
> >>
> >> "# Grab target_cpu, so we can use it in the Solaris pkginfo file
> >> # Make sure we can run config.sub.
> >> $SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 ||
> >> as_fn_error $? "cannot run $SHELL $ac_aux_dir/config.sub" "$LINENO" 5"
> >>
> >> $ /bin/bash ./build/config.sub sun4
> >> Usage: /home/user/Desktop/subversion/build/config.sub [OPTION]...
> >> [MODE-ARG]...
> >> Try 'config.sub --help' for more information.
> >> config.sub: error: you must specify a MODE
>
> On my machine
>
> $ ../src/build/config.sub sun4
> sparc-sun-sunos4.1.1
>
> My config.sub does not contain the string "MODE" and so cannot produce
> the output you show. I'm using config.sub from Debian's autotools-dev
> 20120608.1
>
> I associate MODE-ARG with libtool and that error looks like the error
> libtool produces. Have you managed to get libtool and config.sub mixed
> up?
>
> --
> Philip Martin | Subversion Committer
> WANdisco // *Non-Stop Data*
>
Received on 2014-04-04 00:32:08 CEST