On Aug 21 22:43:12, m...@mansr.com wrote:
> Jan Stary writes:
>
> >> However, the build eventually fails with a linking error:
> >>
> >> /bin/sh ../libtool --tag=CC --mode=link cc -g -O2
> >> -fstack-protector-strong -Wall -Wmissing-prototypes -Wstrict-prototypes
> >> -avoid-version
Jan Stary writes:
>> C_INCLUDE_PATH=/usr/local/include
>> LIBRARY_PATH=/usr/local/lib
>
> I never used any of these.
> Are they docummented anywhere?
Many compilers/linkers support such environment variables. The gcc
manual documents them here:
https://gcc.gnu.org/onlinedocs/gcc/Environment-Var
On Aug 22 11:10:10, m...@mansr.com wrote:
> Jan Stary writes:
>
> >> C_INCLUDE_PATH=/usr/local/include
> >> LIBRARY_PATH=/usr/local/lib
> >
> > I never used any of these.
> > Are they docummented anywhere?
>
> Many compilers/linkers support such environment variables. The gcc
> manual documents
> > > Is it because of the _order_ of the -L options?
Seems so:
cc -g -O2 -fstack-protector-strong -Wall -Wmissing-prototypes
-Wstrict-prototypes -fstack-protector-strong -Wl,--as-needed -o .libs/sox sox.o
-L/usr/local/lib -L./.libs -lsox -lpng -lltdl -lao -lgsm -lid3tag -lz -lmad
-lmp3lame -
On Aug 22 17:35:45, h...@stare.cz wrote:
> On Aug 22 11:10:10, m...@mansr.com wrote:
> > Jan Stary writes:
> >
> > >> C_INCLUDE_PATH=/usr/local/include
> > >> LIBRARY_PATH=/usr/local/lib
> > >
> > > I never used any of these.
> > > Are they docummented anywhere?
> >
> > Many compilers/linkers su
On Aug 22 17:43:28, h...@stare.cz wrote:
> > > > Is it because of the _order_ of the -L options?
>
> Seems so:
>
> cc -g -O2 -fstack-protector-strong -Wall -Wmissing-prototypes
> -Wstrict-prototypes -fstack-protector-strong -Wl,--as-needed -o .libs/sox
> sox.o -L/usr/local/lib -L./.libs -lsox
It seems ./configure is confused about which compiler it found.
When run without arguments, ./configure will look for (and find) gcc,
without ever bothering to look for cc.
With CC specified, using either of
./configure CC=cc
env CC=cc ./configure
this is what happens:
checking
Jan Stary writes:
> On Aug 22 11:10:10, m...@mansr.com wrote:
>> Jan Stary writes:
>>
>> >> C_INCLUDE_PATH=/usr/local/include
>> >> LIBRARY_PATH=/usr/local/lib
>> >
>> > I never used any of these.
>> > Are they docummented anywhere?
>>
>> Many compilers/linkers support such environment variabl
Jan Stary writes:
> It seems ./configure is confused about which compiler it found.
>
> When run without arguments, ./configure will look for (and find) gcc,
> without ever bothering to look for cc.
>
> With CC specified, using either of
>
> ./configure CC=cc
> env CC=cc ./configure
>
