Lemon Lime wrote: > Seeing that some packages in LFS require pkg-config to build,
Nothing *requires* pkg-config. It can always be worked around with the appropriate environment variables. After all, that's what it does: set appropriate environment variables. The reason we dropped pkg-config in LFS is that it requires glib. Unfortunately, glib requires libffi and python and can use pcre, attr, d-bus, and gtk-doc. Additionally *glib* wants to use pkg-config too. python uses pkg-config (a circular dependency), openssl, tk (another circular dependency), openssl, berkeley-db, and sqlite. There are other dependencies when looking at these packages. This is too much for LFS just to avoid setting a few environment variables, so it is addressed in BLFS. > I wrote a > bash script that implements most of pkg-config's functionality, in order > to avoid setting the flags manually for each package that needs it. I > put it in /tools/bin and did a full build of LFS, with a few packages > from BLFS, without any problems. I also verified that it returns the > same results as the standard implementation for all calls to pkg-config > made during the build, except for differences in error messages and the > order of flags of independent libraries. That looks like a nice bit of scripting, but I don't see it being used in LFS where we have already identified the variables needed. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
