First, the previous post indicated some libraries which are owned by Linux-PAM, and they should not have been on the list. Linux-PAM was installed when I did the search.
I've since learned a little bit more about libtool, and that it can create problems during cross compiles. What I thought was a problem with path references to later to be nonexistent installation directory paths, is not an issue. The reason I no longer think the references are a problem, are that after implementing the solution outlined below, there the references are still there. It does not appear to be a requirement for libtools to be present on the host system, as if it is removed, the applications will still install. If gcc is reinstalled after the base system installation, then the errors related to libstc++.la go way. To err on the side of caution, I reinstalled binutils, gcc, libtool, file, gettext, and shadow (in that order) after base system installation. This appears to be an acceptable workaround to the libtools issue at the moment. I'm not sure that a cross-compiled native installation of libtool is necessary. My instincts tell me that some sort of additional magic is required when performing the installations of the applications mentioned above during the base system install to eliminate any problems with the .la files. That's purely conjecture at the moment. I am currently burning through BLFS, and have not experienced the problem again. For those that bump into this post first, I posted separately in clfs-support 'libusb fails to install.' That post gives a little more detail on the actual error message. Best regards, Harvey _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
