On Aug 24 13:19:46, [email protected] wrote:
> On Aug 24 12:04:11, [email protected] wrote:
> > Jan Stary <[email protected]> writes:
> >
> > > We both know what it is: passing C_INCLUDE_PATH and LIBRARY_PATH
> > > into ./configure's environment produces a working link command;
> > > passing CPPFLAGS and LDFLAGS to ./configure also used to produce
> > > a working command, but now produces a failing link line;
> > > the position of -L seems to be the difference.
> >
> > Both ways work fine on my OpenBSD system (clean install + lame etc).
> > There is no difference in behaviour between the master and new-build
> > branches.
>
> Can you please post the complete script(1) for each of
>
> env CC=cc C_INCLUDE_PATH=/usr/local/include LIBRARY_PATH=/usr/local/lib \
> ./configure
> make V=1
>
> and
>
> ./configure CC=cc CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib
> make V=1
>
> on both master and new-build? Because the difference between the two calls
> (which is, eventually, the difference between the ultimate link command)
> seems to be exactly the problem on my system.
Can you please post these scripts so that were are sure?
I beliave it is what we think (namely, a libtool bug),
but so far, we have only seen it fail on my system.
Jan
_______________________________________________
SoX-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sox-devel
