On 06/03/2010 11:33 AM, Neal Murphy wrote: > On Thursday 03 June 2010 04:08:33 Simon Geard wrote: >> >> Curious... like Chris, I routinely build LFS from a host with gdbm >> installed (i.e LFS itself), and never observed any problems relating to >> perl. Indeed, even on completed LFS install, /usr/bin/perl isn't linked >> against gdbm, and runs fine if I remove the libgdbm libraries. >> >> Can you be more specific about the problems you're seeing? Does the perl >> executable fail to run at all, unable to link to libgdbm.so? Or is it >> something less obvious? >> >> Simon. > > I built on Debian Lenny. Perl's configure examines the host system looking for > useful features. In my case, libgdbm was installed on Lenny; perl found it > and configured support for it. Later in the the build, perl failed to run > because it couldn't find libgdbm.so. This was obvious. What wasn't obvious > was, "Why?"
Still not enough info. At what point did Perl try to run, and how exactly? Is it just when running "perl" at all? With certain specific options and/or using certain Perl modules? > If I may be so crass, that you haven't stumbled on this may be due purely to > dumb luck. There are probably subtle differences between LFS' build steps and > the steps I follow in my project. And this may very well be the issue, since nobody has reported this problem when building LFS before. I'd say that for this report to have any validity, you'd need share exactly what these differences are, in particular how Perl is built in Chapter 5 (of course giving more than just "adding those 4 options to Configure"). Typically when some package tries to pull something from the host, it's because of a goof-up in Chapter 5. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
