Re: [IPCop-devel] Build howto

[E.Zierler <zo...@st...>]

> Selon "E.Zierler" <zo...@st...>:
>
>> > Selon "E.Zierler" <zo...@st...>:
>> >
>> [...]
>> >>
>> >> Now I have this situation again and I would find it VERY VERY usefu=
l
>> to
>> >> have a little more detailed information where one has to jump in an=
d
>> >> change things in order to compile in a few extra modules which are
>> >> required on certain machines.
>> >>
>> >> This can be a very short document, in fact a list of files where
>> things
>> >> need to be changed. Does something like this exist or does anyone
>> think
>> >> he/she could create such a document?
>> >>
>> > the simple way is
>> > - compile the entire distrib without changes
>> > - add a lfs/my_script (look at the others, configure VER,
>> THISAPP,DL_FILE,
>> > DL_FROM,DIR_APP,TARGET,$(DL_FILE)_md5 and the way to compile)
>> > - add a call to this script in make.sh : ipcopmake my_script
>> > - ./make.sh build until your script work
>> > - look at log/$(my_script_TARGET) for the list of file result of the
>> > compilation
>> > - copy the list of files in src/ROOTFILES.i386 and comment with # th=
e
>> > files you
>> > don't want to include in the ISO
>> > - ./make.sh build again and the supplementary files are include in
>> your
>> > ISO
>> >
>> > I may be more elaborate if you need to hack the installer for a
>> specific
>> > hardware.
>> >
>> > Gilles
>>
>> Hi once again, with help of this short tips from Gilles I have managed
>> to
>> successfully compile my hardware specific drivers and build a working
>> ISO file. However, I need to EXCLUDE for instance the promise_sata
>> module
>> and according to your advice I am supposed to comment out everything
>> that
>> I don't want in src/ROOTFILES.i386. When I check I see that this file
>> is already commented out.
>>
>> #lib/modules/2.4.29/kernel/drivers/scsi/sata_promise.o.gz
>> #lib/modules/2.4.29-smp/kernel/drivers/scsi/sata_promise.o.gz
>>
>> Hmm, so all I need to figure out is how to prevent certain modules to
>> be checked while booting. I'd be thankful for any hints!
>>
>> Regards,
>>  Erwin
>>
> Sometime a higher level of directory is include.
> This is the case of lib/modules/2.4.29/kernel
>
> The exact solution is when everything is compilated to :
> ./make.sh shell
> cd /usr/src/linux
> make menuconfig and remove compilation of SATA_PROMISE
> make oldconfig to remove some menuconfig comments
> track changes between /usr/src/linux/.config and kernel.config.i386
> report the changes in kernel.config.i386-smp and kernel.config.installe=
r
> remove the line in ROOTFILES.i386 (for documentation purpose only)
> recompile linux so remover
> log/{linux-ipcop,linux-ipcop-smp,linux-installer}
> (or recompile everything)
>
> This is a bit painfull. I play this game sometime during this WE.

It is ;-) But I guess I will get that working eventually.

> It may work a shorter way by directly removing the file you don't want =
in
> lfs/linux (and/or under build/lib/modules/2.4.29), so those files will =
not
> be include.

The art is to remove the modules thta you do not want at the right time!
I seem to have a talent getting them on the ISO file everytime anyway ;-)

> Why do you want to remove sata_promise?

Because the orignal driver from Promise supports my controller fully i.e.
it recognizes the 'real' configuration of the raid system. the sata_promi=
se
module shows me sda and sdb instead of a single disk (sda) - so no mirror=
!
And I have this controller/driver running on other Linuxes with success.

> I will commit changes for kernel 2.4.31 tonight.

I just did a fresh download of the cvs tree and now I get an error I neve=
r
have seen before:

cd /build/ipcop/build/usr/src/openswan-1.0.9 && patch -Np1 <
/build/ipcop/build/usr/src/src/patches/openswan-1.0.1-plutoctl.patch
cd /build/ipcop/build/usr/src/openswan-1.0.9 && patch -Np1 <
/build/ipcop/build/usr/src/src/patches/openswan-1.0.6-numif.patch

Seems those files are indeed missing. Any clue?

> Gilles
>

TIA,
 Erwin

PS.: sorry for being a pain in ... ...