[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in gstep-make
From: |
Nicola Pero |
Subject: |
Re: Bug in gstep-make |
Date: |
Wed, 2 Apr 2003 12:50:27 +0100 (BST) |
> Hello list,
>
> I think there is a little bug in the makefile package. I have
> libffcall installed in a non-standard place (say '/perso/lib').
>
> when I configure the makefile package I do
> CPPFLAGS="-I/perso/include" LDFLAGS="-L/perso/lib" ./configure ...
>
> and this put these two lines
>
> CPPFLAGS = -I/perso/include
> LDFLAGS = -L/perso/lib
>
> into config.make (inside System/Makefile).
> This is nice.
>
> After that, I configure the base package with almost the same line as
> above. When I build the base package, the link failed because it
> can not find libffcall (but the compilation goes well).
> It occurs that the linker is called without -L/perso/lib which is bad.
More precisely - the linker is called with -L/perso/lib when building
(say) a tool, but not when building (say) a library.
I think you can get what you want (having the -L always used) by simply
adding
AUXILIARY_LIB_DIRS += -L/perso/lib
to your config.make.
Else, if you're just hacking things around, another suggestion would be to
edit the base config makefiles so that wherever there is -lcallback
-lavcall, you add -L/perso/lib too. That way you are sure that whenever
ffcall is linked in (and only in that case), -L/perso/lib is used.
Btw, you might need to add /perso/lib to ld.so.conf in order for the
library to be found at runtime.
- Bug in gstep-make, Frederic De Jaeger, 2003/04/02
- Re: Bug in gstep-make,
Nicola Pero <=