Cc: to BLFS-Dev Alexander E. Patrakov wrote these words on 03/31/08 10:44 CST: > Bruce Dubbs wrote: >> >> The implication of going to DESTDIR for LFS would imply doing the same >> for BLFS. Some of the BLFS packages are not DESTDIR friendly. I can't >> remember which ones off the top of my head, but I do recall some that >> ignore DESTDIR, at least partially. > > All perl modules. See > http://linuxfromscratch.org/pipermail/lfs-dev/2007-December/060640.html
This message is after-the-fact and not really relevant to the previous discussion. It is however, interesting. I just installed a Perl Module and not only was it native DESTDIR friendly and multilib friendly, it installed files depending on the native arch of the machine. The module is XML-Parser, version 2.36. The BLFS book is still at 2.34 and I did not do testing with that. Simply using the USE_ARCH var passed to the configuration (perl Makefile.PL), makes multilib just right (maybe, depending on what you are expecting). Destdir works as it is supposed to, passed on the 'make install' line. But what was interesting is that the man pages were only installed in the 64bit installation. They were not put in DESTDIR during the 32bit build, only 64bit. Now, this could be a hassle for cross-builders, but for someone like me that does multilib building with 64bit being the native arch, this works *really good*. I don't have to deal with files being overwritten that are consistent between arches. This is a package manager issue. Nice for me. If it is the way of the future for other Perl Modules, I'm all for it and I can only think it is a good thing. -- Randy rmlscsi: [bogomips 1003.22] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 18:20:00 up 70 days, 9:08, 1 user, load average: 0.52, 0.20, 0.10 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
