Re: libstdc v3 & multilibs

[Robert Lipe <robertlipe at usa dot net>]

> I had only seen this on Solaris before.  The problem is that, when
> `foo' is not set, the shell interprets:
> 
> foo=${foo='${FOO}'}
> 
> as
> 
> foo='${FOO}'}
>             ^
> instead of what one would expect:
> 
> foo='${FOO}'

If I paste your example into a shell and run it, I get what I think I
expect.   

	$ cat x.sh
	foo=${foo='${FOO}'}
	$ sh -x x.sh
	foo=${FOO}

So either this is a different problem, I'm misunderstanding, or you
over-optimized your description of it. :-)

> I'm pretty sure I've already worked around this problem in libtool,
> and the fix has already been merged into the GCC tree for a while, so

I think I see the change you're citing from Sep 30.

> the only thing I can think of is that the `configure' script of some
> target library is still using an old ltconfig.  Is this possible that
> your top-level directory is not up-to-date?

I've updated twice today. 'cvs status' shows neither sticky tags nor
anything in the top-level directory needing an update.   ltconfig is
version 1.12.   

Is it possible that someone has checked in a configure script of some
target library was generated and committed by a libtool that doesn't
have this change?

RJL