This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libtool version




   This fixes the problem:

CONFIG_SHELL=/usr/local/bin/bash

   Apparently /bin/sh on Mac OS X (which is hard linked with /bin/zsh) is 
borked.  Thankfully I saw another thread go by that mentioned 
CONFIG_SHELL.  I suppose the problem was that the quoting code was 
getting executed incorrectly by zsh which is why running bash on my 
trimmed down example didn't work.

-tim



On Sunday, May 19, 2002, at 06:50  PM, Timothy J. Wood wrote:

>
>
> On Sunday, May 19, 2002, at 06:22  PM, Stan Shebs wrote:
>
>> "Timothy J. Wood" wrote:
>>>
>>>    Ah crud.  Nevermind -- the offending shell code is in libtool 1.4.x
>>> too.  I just didn't see it since it gets generated by libtool.m4 and
>>> some quoting crud.
>>>
>>>    Guess I'll either have to fix the quoting or determine that Mac OS 
>>> X's
>>> /bin/sh is busted.
>>
>> Are you using zsh or bash?  bash would probably work better.
>>
>
>   Well, the libtool script starts with '#!/bin/sh',  and is executed as 
> './libtool' instead of '$SHELL libtool', so I'm guessing /bin/sh is 
> what I'm getting.
>
>   Either way, I tried running a trimmed down fragment in a freshly 
> built bash and it yaked too.
>
> % ./bash --version
> GNU bash, version 2.05a.0(1)-release (powerpc-apple-darwin5.4)
> Copyright 2001 Free Software Foundation, Inc.
> % cat /tmp/foo.sh
> #!/bin/sh
> archive_expsym_cmds="if test \\"x\\`head -1 nofile\\`\\" = xEXPORTS; 
> then  fi"
> % ./bash /tmp/foo.sh
> /tmp/foo.sh: command substitution: line 3: syntax error: unexpected end 
> of file
>
> -tim


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]