2009/9/18 Tobias Gasser <l...@ebp-gasser.ch>: [ snip good explanations ]
> what about the kernel modules. they will be 64 bit, don't they have to > be in /lib64/modules? Tried it in clfs. Not worth the aggro. You have to change the top-level kernel Makefile every time. > perl: most will be in /lib/perl as they are architecture independent > (.pm, .pod, .pl). but some libraries (.a, .so) must be moved over to > /lib64/bin. > Perl is a real aggravation to build multilib - primarily because its build system pre-dates everything we are now used to. What is in clfs for perl works (no cross-compilation, both 32 and 64 bit. I suspect a full multilib system only needs one size of perl, but since I don't built these systems any more I don't have any interest in investigating this. Certainly, cblfs systems need perl modules (e.g. XML::Parser) to be built in the size of the program that will use them, but that is becasue of the USE_ARCH variable. ĸen -- After tragedy, and farce, "OMG poneys!" -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
