Menu
▾
▴
devil-linux-discuss
|
From: KyleJHarper <ky...@ca...> - 2009-09-25 21:51:37
|
Hello, I'm building devil with a default config and using the cvs checkout steps listed in the docs for 1.2. The LFS system I'm using is "For DL-1.0 and up". When I run make prepare I get the following: ..... scripts/basic/fixdep.c:306: warning: unused variable `s' make[2]: *** [scripts/basic/fixdep] Error 1 make[1]: *** [scripts_basic] Error 2 make[1]: Leaving directory `/build/tmp/linux-2.6.30' make: *** [prepare] Error 1 Any pointers on what I am doing incorrectly? If there are any logs I can provide let me know. Thanks, Kyle -- View this message in context: http://www.nabble.com/Prepare-getting-error-in-fixdep.c-tp25619820p25619820.html Sent from the devil-linux-discuss mailing list archive at Nabble.com. |
|
From: Heiko Z. <he...@zu...> - 2009-09-25 23:15:27
|
You must be building 1.4, since 1.2 doesn't use the 2.6.30 kernel. Stick with the 1.4, it's much better and very stable. You'll need to use lfssystem-for-DL-1.3.4_and_up for that one. Did you do a "make unpack" before the prepare? Heiko > -----Original Message----- > From: KyleJHarper [mailto:ky...@ca...] > Sent: Friday, September 25, 2009 4:51 PM > To: dev...@li... > Subject: [Devil-Linux-discuss] Prepare getting error in fixdep.c > > > Hello, > > I'm building devil with a default config and using the cvs checkout > steps > listed in the docs for 1.2. The LFS system I'm using is "For DL-1.0 > and > up". When I run make prepare I get the following: > > ..... > scripts/basic/fixdep.c:306: warning: unused variable `s' > make[2]: *** [scripts/basic/fixdep] Error 1 > make[1]: *** [scripts_basic] Error 2 > make[1]: Leaving directory `/build/tmp/linux-2.6.30' > make: *** [prepare] Error 1 > > Any pointers on what I am doing incorrectly? If there are any logs I > can > provide let me know. > > Thanks, > Kyle > -- > View this message in context: http://www.nabble.com/Prepare-getting- > error-in-fixdep.c-tp25619820p25619820.html > Sent from the devil-linux-discuss mailing list archive at Nabble.com. > > > ----------------------------------------------------------------------- > ------- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: KyleJHarper <ky...@ca...> - 2009-09-28 15:55:18
|
Yep, I did "make unpack" first. I found one problem, when following the documentation I forgot the "-r rel-x-y-patchs" option on my CVS checkout. When I've built devil in the past I specified 1-2-patches to get a stable build. I tried 1-4-patches and 1-3-patches but neither exist. I've updated my lfssystem to the "for DL 1.3.4 and up" version. Before I download all the sources with CVS I want to be sure of the proper "-r" switch during checkout. Can you let me know what that is? Thanks, Kyle Heiko Zuerker wrote: > > You must be building 1.4, since 1.2 doesn't use the 2.6.30 kernel. > Stick with the 1.4, it's much better and very stable. You'll need to use > lfssystem-for-DL-1.3.4_and_up for that one. > > Did you do a "make unpack" before the prepare? > > > Heiko > -- View this message in context: http://www.nabble.com/Prepare-getting-error-in-fixdep.c-tp25619820p25645417.html Sent from the devil-linux-discuss mailing list archive at Nabble.com. |
|
From: Heiko Z. <he...@zu...> - 2009-09-29 12:03:08
|
Quoting KyleJHarper <ky...@ca...>: > > Yep, I did "make unpack" first. > > I found one problem, when following the documentation I forgot the "-r > rel-x-y-patchs" option on my CVS checkout. When I've built devil in the > past I specified 1-2-patches to get a stable build. I tried 1-4-patches and > 1-3-patches but neither exist. > > I've updated my lfssystem to the "for DL 1.3.4 and up" version. Before I > download all the sources with CVS I want to be sure of the proper "-r" > switch during checkout. Can you let me know what that is? Don't specify a -r and you'll get the latest and greatest (that's what you want). -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: KyleJHarper <ky...@ca...> - 2009-09-29 21:29:26
|
Heiko Zuerker wrote: > > Don't specify a -r and you'll get the latest and greatest (that's what > you want). > > -- > > Regards > Heiko Zuerker > http://www.devil-linux.org > > That took care of the issue. Thanks. One more quick question... I have a dedicated server for building software, but it still takes quite some time to build devil. Do you have recommendations on speeding up the build process? I see options for using "Nice" and "parallel build jobs" in the config, but I avoid these because I'm unsure how to use them properly. Any recommendations for letting LFS/devil hammer the whole machine to build as fast as possible? Thanks, Kyle -- View this message in context: http://www.nabble.com/Prepare-getting-error-in-fixdep.c-tp25619820p25671285.html Sent from the devil-linux-discuss mailing list archive at Nabble.com. |
|
From: Heiko Z. <he...@zu...> - 2009-09-30 11:21:56
|
> That took care of the issue. Thanks. cool! > One more quick question... I have a dedicated server for building software, > but it still takes quite some time to build devil. Do you have > recommendations on speeding up the build process? I see options for using > "Nice" and "parallel build jobs" in the config, but I avoid these because > I'm unsure how to use them properly. Any recommendations for letting > LFS/devil hammer the whole machine to build as fast as possible? Leave the nice on, this will help your scheduling a bit better. Not sure of the top of my head which option you need to change, it's either "parallel build jobs" or something similar to that. One of them you can only choose 1-2, the other one has 1-10 or something like that (doing it out of memory). Change the one with the more options. As a rule of thumb, use a number +1 or +2 of the total number of CPU cores in the machine. (I really got to disable the other selection....) Lot's of RAM makes a big difference and if you got spare HDDs, use striping. When you compile the 1.4, use a "make makefile" after the "make mrproper unpack prepare", this will enable the parallel build. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: KyleJHarper <ky...@ca...> - 2009-09-30 21:28:37
|
Two things (let me know if I should break this into new posts since we've deviated from the fixdep.c error): 1) Your recommendations for building were spot on. Building was much faster (as least 2x as fast). We might want to update the documentation to include this performance tip since multi-core systems are becoming so prevalent. 2) The build process runs and then hangs on GRSecurity. In single-job mode it simply hung on it (no CPU use for 12 hours). In a parallel-job build it finished everything but not this... again just sitting there. I checked the log file "grsecurity" in build/tmp/LOGS/build. Here is is a 'tail -n 3 grsecurity': ... File POSIX Capabilities (SECURITY_FILE_CAPABILITIES) [Y/n/?] y Root Plug Support (SECURITY_ROOTPLUG) [N/y/?] n TOMOYO Linux Support (SECURITY_TOMOYO) [N/y/?] (NEW) Is this a new configuration flag that the devil/LFS build environment needs to have set? -Kyle -- View this message in context: http://www.nabble.com/Prepare-getting-error-in-fixdep.c-tp25619820p25689355.html Sent from the devil-linux-discuss mailing list archive at Nabble.com. |
|
From: KyleJHarper <ky...@ca...> - 2009-10-01 16:39:50
|
I did some poking around in the grsecurity script and found where the kernel config parameters were. I added a line like so: set_kernel_option CONFIG_SECURITY_TOMOYO n My build is now flying along nicely and looks to have made it passed GRSecurity in the build phase. Let me know if this was the appropriate change to make for Devil and when CVS is updated. -Kyle -- View this message in context: http://www.nabble.com/Prepare-getting-error-in-fixdep.c-tp25619820p25701377.html Sent from the devil-linux-discuss mailing list archive at Nabble.com. |
|
From: Heiko Z. <he...@zu...> - 2009-10-01 17:47:57
|
I added it to CVS. Heiko Quoting KyleJHarper <ky...@ca...>: > > I did some poking around in the grsecurity script and found where the kernel > config parameters were. I added a line like so: > set_kernel_option CONFIG_SECURITY_TOMOYO n > > My build is now flying along nicely and looks to have made it passed > GRSecurity in the build phase. Let me know if this was the appropriate > change to make for Devil and when CVS is updated. > > -Kyle > -- > View this message in context: > http://www.nabble.com/Prepare-getting-error-in-fixdep.c-tp25619820p25701377.html > Sent from the devil-linux-discuss mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > 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. |
|
From: Heiko Z. <he...@zu...> - 2009-10-01 17:40:22
|
Quoting KyleJHarper <ky...@ca...>: > > Two things (let me know if I should break this into new posts since we've > deviated from the fixdep.c error): > > 1) Your recommendations for building were spot on. Building was much > faster (as least 2x as fast). We might want to update the documentation to > include this performance tip since multi-core systems are becoming so > prevalent. Ah documentation.... Are you volunteering? :D > 2) The build process runs and then hangs on GRSecurity. In single-job mode > it simply hung on it (no CPU use for 12 hours). In a parallel-job build it > finished everything but not this... again just sitting there. I checked the > log file "grsecurity" in build/tmp/LOGS/build. Here is is a 'tail -n 3 > grsecurity': > ... > File POSIX Capabilities (SECURITY_FILE_CAPABILITIES) [Y/n/?] y > Root Plug Support (SECURITY_ROOTPLUG) [N/y/?] n > TOMOYO Linux Support (SECURITY_TOMOYO) [N/y/?] (NEW) > > Is this a new configuration flag that the devil/LFS build environment needs > to have set? I thought we fixed that already.... -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: KyleJHarper <ky...@ca...> - 2009-10-01 17:49:19
|
For as much help as you and the Devil project have been I'd be glad to help out with keeping documents updated. I've sent you a private message with my email address if you'd like a hand. As for the TOMOYO stuff, it wasn't fixed for me in the grsecurity file. I always run an update script I made that checks out the latest from CVS and runs update_src; a fixed grsecurity wasn't in there. If it IS in there perhaps I have my CVS checkout command wrong. In either case let me know :) Thanks, Kyle -- View this message in context: http://www.nabble.com/Prepare-getting-error-in-fixdep.c-tp25619820p25703606.html Sent from the devil-linux-discuss mailing list archive at Nabble.com. |
