On mån, 2012-05-14 at 00:30 -0500, Jonathan Nieder wrote:
> The intended effect does seem to be that 'cc' would act just like a
> synonym for 'gcc', but unfortunately in the loop that scans the
> information for each tag to find a match for 'cc', the default
> settings for variables like $pic_flag
Peter Eisentraut wrote:
> The practical impact is probably low, but it's still wrong.
Hm. If the practical impact is very low, I suppose the best we could
do is to forbid 'cc' as a compiler without --tag.
*investigates*
Seems that upstream libtool does forbid 'cc' as a compiler without
--tag.
On lör, 2012-05-12 at 23:42 -0500, Jonathan Nieder wrote:
> I can reproduce this --- passing 'cc' instead of 'gcc' to libtool
> suppresses the -fPIC option. However, I'm not sure if it matters
> these days since passing --tag=CC makes libtool do the right thing and
> most authors of build systems
found 286341 libtool/2.4.2-1
quit
Hi Peter,
In 2004, you wrote:
> $ /usr/bin/libtool --mode=compile gcc -c test.c
> mkdir .libs
> gcc -c test.c -fPIC -DPIC -o .libs/test.o
> gcc -c test.c -o test.o >/dev/null 2>&1
>
> $ /usr/bin/libtool --mode=compile cc -c test.c
> cc -c test.c
> mv -f test
4 matches
Mail list logo
