This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc v3 & multilibs
> > If I paste your example into a shell and run it, I get what I think I
> > expect.
>
> What if foo is already set to '${FOO}'? Maybe I mis-remember...
Yes. That's the failure case and my bourne shell (but not my korn shell)
does share this behaviour.
$ cat x.sh
foo='${FOO}'
foo=${foo='${FOO}'}
(robertl) rjlhome:/tmp
$ sh -x x.sh
foo=${FOO}
foo=${FOO}}
> > 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?
>
> It is certainly possible. I'd grep 'MAGIC}' in all `configure'
> scripts and see if anything turns out.
Is 'MAGIC}' good or bad?
(robertl) rjlhome:/play/egcs
$ find . -name configure | xargs grep 'MAGIC}'
./libobjc/configure: lt_cv_file_magic_cmd='${MAGIC}'
./libobjc/configure: if test "$file_magic_cmd" = '${MAGIC}'; then
I did patch Makefile.am and acinclude.m4 earlier for the 'ar c without
a filename' issue. Which tool (libtool or autoconf) is responsible for
this?
RJL