Ken Moffat wrote: > On Tue, Sep 27, 2011 at 05:15:25PM -0500, Bruce Dubbs wrote: >> Since the only thing in LFS that requires pkg-config is E2fsprogs, the >> easiest thing would be to patch the E2fsprogs build mechanism to remove >> the dependency on pkg-config and then remove PCRE, Glib, and Pkg-config >> and defer them to BLFS. >> > That would also mean that e2fsprogs would have an inadequate > install - if anything *after LFS* requires e2fsprogs pc files, it > won't find them.
I would think the pc files would be installed anyway in /usr/lib/pkgconfig. I haven't checked though. > I've got quite attached to having pkgconfig in my core system, but > I can easilt reinstate 0.0.22 at the beginning of my own post-LFS > scripts. I'm just trying to say that we shouldn't throw the baby > out with the bathwater! You can always build any package from BLFS first (but following dependencies of course). Personally, I always build ssl, ssh, which, and sudo very early, but there would be nothing to prevent adding pkg-config to that list. I realize that would mean building pkg-config and dependencies without the convenience of jhalfs. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
