Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
3 birthdays and X-mas, bummer Taz. Actually, that reminds me... I have to make a phone call, cool, thanks man.
Er, yeah I think Dbopen refers to having the Berkeley DB from Sleepcat.com configured for 1.85 compatability mode (whatever that means).
This DB, by the way, is a raging pain in the arse. No normal README, instead a howto.html it wants you to load in a web browser. Hello jokers! If I could read this thing in a web browser, I wouldn't need to build this component as part of my GUI. I'm just glad I collect spare machines like most people collect belly button lint.
I think I've got it configured right, but I still can't get gnome-libs past that one spot in configure. Yeah, I've erased the cache, heck I've rm'd and re-untared the packages a number of times. There are as far as I can tell, 8 main libs and 4 core necesarry components to Gnome, then there are 6 other necessary packages to get any of that to compile right, plus all of the grphics libs for tiff, png, jpeg... blah blah blah, and this wonky db that looks like a commercial product. Heck, I've got some uber-geek friends I could pester about this, but I just wanted to give the forum a shot.
I'm beginning to doubt that I like Gnome much myself. Good luck with T-Bird when you get back to it... If I ever get this figured out, I'm putting together an LFS+Gnome How-to. There are just too many uncommon pitfalls.
Finegan, who is wondering why he is hacking to Brit-pop
No, I did 4.0.2, but honestly it was nearly a month ago now and I didn't keep very good track of what I was doing or the state of mind I was in... I remember I didn't get very far with 4.1.0 which is why I swapped down...
Originally posted by finegan Has anyone else had issues with gtk on LFS? I've compiled and installed GTK a couple of times now, but no matter what I fiddle with, imlib complains that it can't find gtk, but compiles anyway, and gtk-engines refuses to config as it can't find gtk.
I've run ldconfig and seen the library links to gtk.
i've run across this problem so many times when compiling gtk-progs that i've almost become one with the configure script. honestly... i don't know why the script can't always find gtk - it runs a small script called gtk-config to try to find it. when you install gtk, it should put the script in /usr/local/bin or in /usr/bin - the only solution i ever found was to copy the script to both directories. and that still doesn't work sometimes. exporting paths or passing command-line options has NEVER once worked... but i've spent entire cans of coffee grinds trying.
the only surefire method i've ever found of getting gtk included is to edit the configure scripts by hand... which is possible when you know what you're looking for, but it's a HOW-TO in itself, which i don't think has been written.
...if you want, i think i could write out how to fix the configure scripts for the progs... but i'd be typing for about an hour or so... i'll do this one by request only
ok... i got bored. this is for the configure script for gtk-engines-0.12 - hopefully that's the one you're using, or the line # will probably be different.
ok... here's the critical part in the script... i added line 1771 on mine
if test -n "$GTK_CONFIG"; then
echo "$ac_t""$GTK_CONFIG" 1>&6
echo "$ac_t""no" 1>&6
echo $ac_n "checking for GTK - version >= $min_gtk_version""... $ac_c" 1>&6
echo "configure:1775: checking for GTK - version >= $min_gtk_version" >&5
the line i put in there is the
which is the location of the gtk-config file on my system. yours might be different.
the trick is to set the GTK_CONFIG to the path at the right spot - if you do it at the beginning of the script, it will probably get changed before it gets to where it uses it. it needs to be set just before it's testing the version numbers that the gtk-config script returns. it's a pain-in-the-ass to find - esp. if you're not very familiar with shell scripts.
there are supposed to be options for configure to do it correctly using some options, but i've never gotten it to work. if you want to play around with it - type
"./configure --help", and slowly let it beat you into submission, and then just go and change the script manually .
Actually, one or two posts down... and this thread has turned into an anchor chain for an oil tanker, so I may be off. I solved my own idiocy with an addition to ld.so.conf. This is my first time juggling around libraries, so a lot of it is kind of counter-intuitive. My new problem lies in getting gnome-libs to config right. It coughs out on not finding dbopen, in 1.85 compatability mode, which I think refers to the monstrosity from sleepycat.com, but I swear I've built that right. I'm about to have a pair of CS degree friends start LFS as well, so maybe I'll go fiddle with Samba until they catch up, or possibly just go back and start over with a little more than the middle-school-gym-shorts-restrictiveness of my 1 Gb LFS partition. Today I pick up the printed copies of the LFS book; gotta love being staff at a university and having no print quota!
I actually went back to gtk and re-compiled everything from there with your modification, but it coughed and died in the same place on gnome-libs. Oh well...
And now that its the Gnu-year... why did I type that joke... even I think its silly, anyway, where is everyone else on their projects? TrickyKid? Taz? Recoil? Come on, our uber-thread has fallen to 8th.
Also, can anyone recomend a really good, close to cheap as can be, case/PS combo for a 1.2Ghz T-Bird? My PS is about to cough and die from dust and abuse. I've never been able to put the side of the case on as it'll run hot enough for me to use the HSF to cook hotdogs. I'm pretty poor at the moment, but I can pick up almost anything locally, yippee.
Howdy, well i've been halted on LFS lately. I set it aside for a little while as it was sstarting to make my head hurt. LOL I'm playing with the thought of starting over (again) and REALLY customizing it to my system, needs and wants. So for now, my printers brand new ink cartridge is already half used from printing out the 3.1 book in full. So i'll be spending another $30 on a new cartridge soon. Dang! So that's where I sit and am taking notes on this thread so that next time everything goes beyond flawless! If that's possible? =)
So happy LFSing all and a happy GNU year! hehehe, I liked it finegan....
Originally posted by finegan I actually went back to gtk and re-compiled everything from there with your modification, but it coughed and died in the same place on gnome-libs. Oh well...
yeah... i didn't think that had much of a chance of working right off... i don't remember offhand what other changes i made. i think sisyphys would have been condemned to mucking around with configure scripts instead of that boulder thing if zeus had known about computers...
This seems to be THE place to ask questions about LFS. So I guess this would be the right place. The rest of this thread has helped me a lot not to make the same mistakes others made. Anyways here is my problem. X is bothering me a bit. More specifically version 4.1.0. I got through the compile with nothing more then a few warnings which shouldn't be any problem. I followed the following hint:
All seemed well even when I let it automatically detect my hardware with the 'XFree86 -configure' command. It found everything right expect the mouse protocol but that wasn't a real disaster. I need the i740 driver to get my card working and that's exactly what was causing the problem. When I started X it goes through the whole process without any warnings or errors. But then it crashes with a signal 11 after loading the vgahw module. At that point it already did load the i740 module. Everything worked if I switched to the vga driver.
Anyways after trying all the things I could think of and a few compiles further without success, I finally copied the i740 module from my mandrake machine and it worked without any problems.
It works now so I actually shouldn't complain but I still wanna know why. I suspect that Mandrake either patched the drivers (I couldn't find any patches) or that they compiled it in a special way. Couldn't find anything obvious about the way I compiled it though. Just followed everything the standard way and didn't use optimizations.
Just wondering if anyone could explain why? Did anyone here get version 4.1.0 working and if so which modules do you use? I seem to read a lot of posts of people with problems with this version and after downgrading everything worked fine. Well if anyone did compile it in LFS and it's working maybe I could somehow get the i740 module from them just to see if it's the way I compiled it or just something buggy about the standard compile of that driver.
By the way I followed the 3.1 book to create my LFS.
I compiled the driver and it seems to work fine so far. I still haven't gotten my LFS as far as I want. But so far I've got it working with the http://xfce.org desktop environment. I've also got xine and xmms so I can watch movies and listen to music while I work on the rest.
I kinda like the LFS way of doing things it seems a lot easier to compile things. Well once in a while I run into a few troubles, but because I set it up from scratch I know where everything is which helps a lot. The only real problems I've had so far was compiling lynx which couldn't find the proper rand and srand instructions. And the i740 module problem. The rest was all stupid problems by disabling the wrong things in my kernel. Or forgetting to pass a parameter to the config script.
And linuxquestions has ofcourse been a great problem solver/preventer.
Originally posted by RecoilUK
How are you getting on with it btw? what new developments are you working on at the moment and what else is to come?
Keep up the good work
The short answer: http://bugs.linuxfromscratch.org will lead you to the 70 or so outstanding things. When they are all taken care (including new ones that may be added over the next while), LFS-4.0 will be released.
Most of the outstanding bugs are documentation type of things. Adding a lot more information, resources, explanations, alternative ways of doing things, etc, etc, etc (to really emphasis more on the learning aspect of LFS).
One of the big things we're working on is to re-structure chapters 5 and 6. Ideally chapters 5 and 6 should be fully seperated, as in: seperate preparing the LFS partition (chapter 5) and installing the software (chapter 6). Right now things done in chapter 6 should be moved to chapter 5.
Also, we don't quite like the idea of all the static software going into $LFS/usr/bin $LFS/bin and such directories. It doesn't provide a good clean guarantee that after you finish chapter 6, everything is overwritten properly, etc. So what we're going to do is this: In chapter 5, install everything to a prefix of $LFS/static and add $LFS/static/bin to $PATH inside chroot. Then when you're finished with chapter 6 run a "rm -r /static" and all temporary stuff from chapter 5 is gone. This guarantees a clean system.
Another thing is re-arranging the order of software installed in chapter 6. We want to re-compile GCC immediately after Glibc is installed (just feels better). this requires a static findutils to be added to chapter 5.
Another big change is to go through chapter 4 and 5 as non-root. This will greatly reduce the potential system damage (say you're using $LFS but forgot to set the $LFS variable - all software in chapter 5 will be installed onto your host distribution which isn't desirable). We'll have the users setup a user 'lfs' login as user 'lfs' and install chapter 5. Then su to root, enter chroot and mount the proc file system from inside chroot (instead of outside like currently). This means mount and umount need to be installed from the util-linux package in chapter 5 too.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
The last post by lfslinux is outstanding and exactly the reason that I think that having a distro rep is key to a distro having it's own forum. I hope no one minds, but I am moving this thread to the LFS forum.
If you're talking about expanding the disk to full capacity my question becomes why?
Identify the areas on the disk that require more space than the others (/usr vs /var for instance) and just create partitions and mount them in those directories.
This is actually another discussion entirely(disk management) but seeing as you've got a nice stable running LFS, it makes more sense to go ahead and be smart about disk management now, instead of using the entire beast as one partition.