atark atark at
Wed Aug 23 19:27:28 PDT 2000

I'm starting to look at this a bit lately also.  I'm building Slackware type
packages of each part of lfs (shared only).  Then I'm going to find the least
amount of stuff I need to install to have a bootable system to start installing
packages.  So I'm finding some dependancies by accident.  

My main purpose behind this is to be able to install LFS consistently across
several computers, slower ones that would take forever for certain packages to
compile.  Once ALFS get here this idea may change but hey, isn't it all a
learning experience anyway?


Gerard Beekmans wrote:
> > And here's the kicker:  The bison compile fails, with an error "ld: cannot
> > open -lc: no such file or directory"
> -lc is your C library and expands into
> what does redhat 4.2 use? libc-5.x I guess. Are there files like
> /lib/ ?
> perhaps there are /lib/ - if so, make symlink from to
> > By the way, is there a fairly complete package dependency list out there
> > already, or should I build one as I go?
> I'm working on it. A proper list is obtained by installing one package,
> satisfy dependencies and then remove all installed package and start
> from scratch. If you say "ok bison needs flex so install flex" and let
> flex be, you might not notice a second package that needs flex too, so
> after flex is installed to satisfy bison, remove flex and bison and go
> on the next package. That's a time consuming process. But I'm getting
> there slowly but steadily.
> --
> Gerard Beekmans
> -*- If Linux doesn't have the solution, you have the wrong problem -*-

More information about the lfs-dev mailing list