Reinhard Tartler schrieb:
As for FHS compliance, well, since even libc6 is doing this, I'd think this is okay.
Fine, I am not too literate in linker science. ;)
I'd say we install all variants in a single package and let the dynamic linker choose the right library.
If the aforementioned is true, then that's fine by me.
# Don't disable altivec, at least for now. Disabling altivec causes a # FTBFS in libswscale, as it will fallback to a "plain c version" of # some functions, which only compile with altivec enabled. #nooptflags += --disable-altivec Unfortunately, I forgot to add references (bugno or buildlog) to this problem. Damn.
Hehe, I know about this comment, but obviously we are going to provide a non-altivec PPC version of the library. That's why I was asking.
Sebastian, could you please investigate this issue? I'll be working on building the flavors in paralell.
Now would be the right moment to offer my help, but I'll be on the Rock-am-Ring festival from Wednesday to next week's monday... :D
-- Dipl.-Phys. Fabian Greffrath Ruhr-Universität Bochum Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT) Universitätsstr. 150, IB 3/134 D-44780 Bochum Telefon: +49 (0)234 / 32-26334 Fax: +49 (0)234 / 32-14227 E-Mail: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
