Twas brillig at 08:24:37 03.12.2009 UTC+01 when [email protected] did gyre and gimble:
>> During cross-compilation brain-damaged stuff like libxtrans just >> will not be picked up by compiler unless various pereversions are >> applied. Given this, xtrans.pc need to be installed to /usr/share, >> and hence there is no problem to install rest of arch-independent >> stuff to /usr/share. MK> Sorry, I must be missing something. Since when do compilers look in MK> /usr/share? Ugh. I meant pkg-config. >> Include list for cross-compilation does not include /usr/lib, it >> instead includes /usr/$arch/lib. All libraries need to be installed >> to /usr/$arch/lib anyway to be usable for cross-compilation, but >> headers and stuff like macros and source code do not. MK> Isn't /usr/$arch just another $PREFIX? So currently .pc files MK> would end up in /usr/$arch/lib where they would be picked up just MK> fine if you set the proper environment variables. Well, it's kind of special, as there should be no /usr/$arch/share (so there is no logical place for xtrans.m4). MK> Corss-compilation is the special case here. It's perfectly MK> acceptable to ask people to do a bit of more work in that case. MK> Much more acceptable than imposing the same burden on the majority MK> of people doing native builds. "Native builds" of all kinds are FOOBARed if they don't look at /usr/share/pkgconfig. E.g.: udev: /usr/share/pkgconfig/udev.pc xcb-proto: /usr/share/pkgconfig/xcb-proto.pc libpthread-stubs0-dev: /usr/share/pkgconfig/pthread-stubs.pc Asking to "do a bit of more work" just to compensate for upstream failing to grasp pkg-config is rude. I could live with various hacks: hey, it's bloody one-line patch. Should I, or it's better to make it work properly? -- http://fossarchy.blogspot.com/
pgpsBePSDBxJg.pgp
Description: PGP signature
_______________________________________________ xorg-devel mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-devel
