On 2011-01-11 20:40 +0100, Sven Joachim wrote:
> On 2011-01-10 23:52 +0100, Colin Watson wrote:
>
>> Package: ncurses
>> Version: 5.7+20101128-1
>> Severity: wishlist
>>
>> Apparently ncurses has an --enable-pc-files option to generate
>> pkg-config files. pkg-config is quite common nowadays; perhaps it would
>> be worth enabling that option and installing those files in -dev?
>
> Sounds reasonable to me. Do you know if the lib{32,64}ncurses*-dev
> packages need special treatment or if they can use the .pc files from
> their normal counterparts? I see that the .pc files set
> libdir=/usr/lib, but (fortunately) do not use -L${libdir} in Libs, so
> they might work for the lib{32,64}*-dev packages as well, but I'm not a
> pkg-config expert.
Reading the pkg-config documentation, it removes /usr/lib from Libs
anyway to not interfere with the linker search path.
> If the lib{32,64}*-dev packages needed their own .pc files, where would
> those be installed?
Seems there is no place for them, because pkg-config does not know
whether you want to build 32-bit or 64-bit binaries. Only gcc knows
that and sets up the linker path accordingly.
It seems that the mere "libdir=/usr/lib" setting cannot lead to stray
"-L/usr/lib" in gcc commandlines, so that it should be safe to install
the .pc files and use them in conjunction with "CC=gcc -m{32,64}".
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
