|
From: Heiko Z. <he...@zu...> - 2008-06-23 18:00:42
|
Hey, it sounds like you're doing everything right. Did you try to compile on different physical hosts or was it always the same machine? With a compile this big you sometimes find hardware problems you would never stumbled over otherwise. When you test, work with the default config for now. I'm going to kick off a fresh compile on my build machine, to make sure I didn't introduce a bug with the last update (when I added 2.4.36.6). cu Heiko Quoting KyleJHarper <ky...@ca...>: > > I have been experiencing a great deal of trouble getting devil-linux to build > properly. I am able to get the LFS system going, get the sources and unpack > them, get the config set up, run prepare just fine, but I receive many build > errors. I have tried several configurations, thinking I messed something > up. As follows: > > --Attempt #1-- > Host OS: Ubuntu 8.0.4 (fresh install) on a Virtual Machine (VMWare) > LFS: LFSSystem for DL 1.0 and up > Building Version: 1.2.x > Install location: All default and according to documentation > (/usr/src/lfssystem) > Modifications: Deselected most in config and added sudosh. > Problems: Reached linux-2.4.36.6 build and it failed. Upon reading the log > in tmp/LOGS/build/linux it was having some trouble finding the > /etc/lilo/install file/folder. > > --Attempt #2-- > Same as Attempt #1 except I didn't change anything in the config (I did > enter config though, to create the config file with defaults). Also I did > not add sudosh. I just followed the instructions verbatim. > Problems: Reached linux-2.4.36.6 build and it failed. Reading log again > showed an error with /etc/lilo/install file/folder. > > --Attempt #3-- > Same thing as Attempt #2 except I used a REAL system, not a VM. Followed > the steps verbatim. > Problems: Reached postgresql build and it failed (error log showed "No rule > to make target utf8_and_euc_jis_2004.0, needed by > 'libutf8_and_euc_jis_2004.so.0.0"). Manually ran the configure and make > (inside the chroot environment) and it build successfully. I added the > .done_build_postgresql and continued on. Then I reached linux-2.4.36.6 and > received a plethora of errors about being unable to find a function (if I > remember correctly) called __guard and __stack_smasher. > > --Attemp #4-- > Thinking the problem could be with Ubuntu I switched to Mandriva (fresh > install). Followed all steps verbatim again. > Problems: Reached postgresql build with errors again (same error message as > in attempt #3). > > Please note that on attempt #1 and #2 I tried wiping out the LFS system, > running mrproper, and getting sources and preparing again. No luck. Also, > I checked for things like Pax and GRSecurity and couldn't find any > indication of them (since your site said you can't compile devil with those > on the host OS). > > I've ready several forums where the problem has been user-side and after a > quick change everything runs great. From looking at the system for many > many hours I believe it is very user friendly. So I might just be a tool > here, but any advice on what to try would be greatly appreciated! > > If you need any more information just let me know. I've tried to include as > much as I can recall. If you need me to use another host OS or whatever I > have both virtual (VMWare) and physical (good ole fashioned HD) systems > available. > > Sincerely, > Kyle Harper > -- > View this message in context: > http://www.nabble.com/Continous-build-errors-tp18066864p18066864.html > Sent from the devil-linux-discuss mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |