octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: failed build


From: Ben Abbott
Subject: Re: failed build
Date: Tue, 27 Jul 2010 20:41:43 -0400

On Jul 27, 2010, at 7:23 PM, Jordi Gutiérrez Hermoso wrote:

> On 27 July 2010 17:52, Ben Abbott <address@hidden> wrote:
> 
>> Its been several days since I built, and weeks since I ran
>> autogen.sh ... today, when I tried the build failed.
> 
> I'm unable to reproduce this, but...
> 
>> ../libtool: line 844: X--tag=CC: command not found
>> ../libtool: line 877: libtool: ignoring unknown tag : command not found
>> ../libtool: line 844: X--mode=compile: command not found
>> ../libtool: line 1011: *** Warning: inferring the mode of operation is 
>> deprecated.: command not found
>> ../libtool: line 1012: *** Future versions of Libtool will require 
>> --mode=MODE be specified.: command not found
>> ../libtool: line 1155: Xgcc-4.2: command not found
>> ../libtool: line 1155: X-DHAVE_CONFIG_H: command not found
>> ../libtool: line 1155: X-I.: command not found
>> ../libtool: line 1155: X-I..: command not found
>> ../libtool: line 1155: X-I/sw/lib/flex/include: No such file or directory
>> ../libtool: line 1155: X-I/sw/include: No such file or directory
>> ../libtool: line 1155: X-m32: command not found
>> ../libtool: line 1155: X-I/sw/include/freetype2: No such file or directory
>> ../libtool: line 1155: X-I/sw/include/qhull: No such file or directory
>> ../libtool: line 1155: X-I/usr/include: No such file or directory
>> ../libtool: line 1155: X-I/sw/include: No such file or directory
>> ../libtool: line 1155: X-m32: command not found
>> ../libtool: line 1155: X-O2: command not found
>> ../libtool: line 1155: X-g: command not found
>> ../libtool: line 1155: X-D_THREAD_SAFE: command not found
>> ../libtool: line 1155: X-pthread: command not found
>> ../libtool: line 1155: X-MT: command not found
>> ../libtool: line 1155: Xclose-hook.lo: command not found
>> ../libtool: line 1155: X-MD: command not found
>> ../libtool: line 1155: X-MP: command not found
>> ../libtool: line 1155: X-MF: command not found
>> ../libtool: line 1155: X.deps/close-hook.Tpo: No such file or directory
>> ../libtool: line 1155: X-c: command not found
>> ../libtool: line 1208: Xclose-hook.lo: command not found
>> ../libtool: line 1213: libtool: compile: cannot determine name of library 
>> obje
> 
> Can you post a few of the relevant lines of the libtool script that
> errored out above?
> 
> My WAG is that this is a problem with spaces. Those X's make me think
> it may be referring to "Mac OS X" somewhere, introducing spaces, and
> making your libtool script unusuable.

The lines from libtool are below.

 843   case $arg in
 844   -*=*) optarg=`$echo "X$arg" | $Xsed -e 's/[-_a-zA-Z0-9]*=//'` ;;
 845   *) optarg= ;;
 846   esac

 872         if grep "^# ### BEGIN LIBTOOL TAG CONFIG: $tagname$" < "$progpath" 
> /dev/null; then
 873           taglist="$taglist $tagname"
 874           # Evaluate the configuration.
 875           eval "`${SED} -n -e '/^# ### BEGIN LIBTOOL TAG CONFIG: 
'$tagname'$/,/^# ### END LIBTOOL TAG CONFIG: '$tagname'$/p' < $progpath`"
 876         else
 877           $echo "$progname: ignoring unknown tag $tagname" 1>&2
 878         fi

1009   # Infer the operation mode.
1010   if test -z "$mode"; then
1011     $echo "*** Warning: inferring the mode of operation is deprecated." 
1>&2
1012     $echo "*** Future versions of Libtool will require --mode=MODE be 
specified." 1>&2
1013     case $nonopt in

1153 
1154       # Aesthetically quote the previous argument.
1155       lastarg=`$echo "X$lastarg" | $Xsed -e "$sed_quote_subst"`
1156 

1207 
1208     libobj=`$echo "X$libobj" | $Xsed -e "s/\.$xform$/.lo/"`
1209 

1210     case $libobj in
1211     *.lo) obj=`$echo "X$libobj" | $Xsed -e "$lo2o"` ;;
1212     *)
1213       $echo "$modename: cannot determine name of library object from 
\`$libobj'" 1>&2
1214       exit $EXIT_FAILURE
1215       ;;
1216     esac

I see the "X"'s earlier on. Some examples are below.

  79 # Sed that helps us avoid accidentally triggering echo(1) options like -n.
  80 Xsed="$SED -e 1s/^X//"

 471 # Check that we have a working $echo.
 472 if test "X$1" = X--no-reexec; then
 473   # Discard the --no-reexec flag, and continue.
 474   shift
 475 elif test "X$1" = X--fallback-echo; then
 476   # Avoid inline document here, it may be left over
 477   :
 478 elif test "X`($echo '\t') 2>/dev/null`" = 'X\t'; then
 479   # Yippee, $echo works!
 480   :
 481 else
 482   # Restart under the correct shell, and then maybe $echo will work.
 483   exec $SHELL "$progpath" --no-reexec ${1+"$@"}
 484 fi
 485 
 486 if test "X$1" = X--fallback-echo; then
 487   # used as fallback echo
 488   shift
 489   cat <<EOF
 490 $*
 491 EOF
 492   exit $EXIT_SUCCESS
 493 fi

 502 # Sed substitution that helps us do robust quoting.  It backslashifies
 503 # metacharacters that are still active within double-quoted strings.
 504 Xsed="${SED}"' -e 1s/^X//'
 505 sed_quote_subst='s/\([\\`\\"$\\\\]\)/\\\1/g'
 506 # test EBCDIC or ASCII
 507 case `echo X|tr X '\101'` in
 508  A) # ASCII based system
 509     # \n is not interpreted correctly by Solaris 8 /usr/ucb/tr
 510   SP2NL='tr \040 \012'
 511   NL2SP='tr \015\012 \040\040'
 512   ;;
 513  *) # EBCDIC based system
 514   SP2NL='tr \100 \n'
 515   NL2SP='tr \r\n \100\100'
 516   ;;
 517 esac

Can someone comment on what their libtool looks like? Are these "X"'s present?

TiA
Ben







reply via email to

[Prev in Thread] Current Thread [Next in Thread]