|
From: Heiko Z. <he...@zu...> - 2003-03-12 00:45:30
|
Manu ESCAR wrote: > No, i didn't make unpack before menuconfig ! that's why it worked for my > second compilation as sources where in tmp dir ! A "mrproper" is necessary to ensure a clean build environment. The next step would be a "really-really-clean" which means deleting everything and unpacking the lfssystem. This is the way I use before I release any new version. >>> so i opened another shell to see it was grsec patches ! Amazing as >>> the option was disabled for a while in my selection! So i edit >>> .config file to see that there is no ligne with CONFIG_GRSECURITY=n !!! >> >> >> >> It's important that there is no CONFIG_GRSECURITY=y . >> I checked the script again, I can't find any problems. >> Do you know if CONFIG_XFS and CONFIG_GRSECURITY were set to "y" ? > > > CONFIG_XFS=y and nothing about CONFIG_GRSECURITY, not even > CONFIG_GRSECURITY=n Strange, I'll start a compile with xfs and no grsec >> A symlink to $DL_DIR/build/tmp/linux-2.4.20/include/linux is created >> in /usr/include during the early build process. >> That's our way to ensure the usage of the correct include files for >> the current Kernel. > > > so why renaming it to linux2 ? and when in the build process ? The documentation says nothing about linux2.... ;-) It's in 001prepare. >> Always try to avoid modifying tarballs, use patches. If it is really >> necessary, then we include modified tarballs, but only when we really >> have to do it. This makes later software updates much easier. >> >> About the depmod stuff, you can use it when it doesn't run into an >> error, which should not happen that late in the build stage (I mean >> after 159linux). We don't use the generated data and create our own >> when the system boots up. > > > Thanks a lot, my only purpous is to make good clean job others can use > and integrate in this wonderful distro! Sounds good to me. ;-) -- Regards Heiko We are Penguin, resistance is futile! http://www.devil-linux.org |