Discussion:
Kernel 2.4.22 build under CygWin (for Jetway NF18GF)
(too old to reply)
Steve Mowbray
2003-11-11 16:24:58 UTC
Permalink
Hi

New to kernel building.

Trying to build kernel 2.4.22 using latest CygWin but cant get past the
'make dep' stage. I have followed the quick guide to the letter up until
this point (several times) therefore I would be grateful for any information
or source on the following:

- A working '.config' for Jetway NF18GF MB (all peripherals are integrated
so it should be pretty much a vanilla config for everybody with this board).
AND/OR
- A minimal x86 compatible PC target '.config' that will get a basic linux
kernal image running (this will at least give me confidence in the process)

Also I did not see any site specific modifications required for 'Makefile'
as a result of building under CygWin - am I mistaken.


Cheers
Steve
P.T. Breuer
2003-11-11 17:00:27 UTC
Permalink
Post by Steve Mowbray
Trying to build kernel 2.4.22 using latest CygWin but cant get past the
'make dep' stage. I have followed the quick guide to the letter up until
this point (several times) therefore I would be grateful for any information
- A working '.config' for Jetway NF18GF MB (all peripherals are integrated
so it should be pretty much a vanilla config for everybody with this board).
AND/OR
Every config works for compiling (bugs permitting). And the MB is
not really relevant, since by design it's as invisible as can get. Why
would having integrated peripherals be eitehr a help or a hindrance?
Often they're a horror story in themselves, but that's another tale.

Start with a distros *installed* (not *install*) kernel config.
Post by Steve Mowbray
- A minimal x86 compatible PC target '.config' that will get a basic linux
No such thing. It depends on your peripherals. For example, if you boot
of scsi or ide.
Post by Steve Mowbray
kernal image running (this will at least give me confidence in the process)
Also I did not see any site specific modifications required for 'Makefile'
as a result of building under CygWin - am I mistaken.
Eh? Surely you aren't compiling under windows? That will never fly.
Only a very few compilers can compile the kernel. Read the
instructions! At least the Changes file.

Peter
Steve Mowbray
2003-11-11 18:57:24 UTC
Permalink
Post by P.T. Breuer
Post by Steve Mowbray
Trying to build kernel 2.4.22 using latest CygWin but cant get past the
'make dep' stage. I have followed the quick guide to the letter up until
this point (several times) therefore I would be grateful for any information
- A working '.config' for Jetway NF18GF MB (all peripherals are integrated
so it should be pretty much a vanilla config for everybody with this board).
AND/OR
Every config works for compiling (bugs permitting). And the MB is
not really relevant, since by design it's as invisible as can get. Why
would having integrated peripherals be eitehr a help or a hindrance?
Since it is an all-in-one board - I thought maybe that there would be a
certain similarity between all kernel builds for this target.

Actually - I probably should have said NVidia nForce2 chipset as this would
have been much more meaningful.
Post by P.T. Breuer
Often they're a horror story in themselves, but that's another tale.
Yes - I have suffered much annoyance in the past - however the NVidia
chipset seems to behave reasonably well for Win32 and Linux installs (Not
Mandrake 9.2 as yet - but I put that down to my lack of experience).
Post by P.T. Breuer
Start with a distros *installed* (not *install*) kernel config.
Not starting from distro - have downloaded kernel 2.4.22 and along with web
searches, some books Ive bought and newsgroup support I am hoping to learn
Linux from the ground up. Something I should have done 10 years ago instead
of going down the Win32 path.

steps done so far

make clean
make mrproper
make clean (again? - it says so in a LinuxHQ man page I found)
make xconfig
make dep (stops half way)
...
...
Post by P.T. Breuer
Post by Steve Mowbray
- A minimal x86 compatible PC target '.config' that will get a basic linux
No such thing. It depends on your peripherals. For example, if you boot
of scsi or ide.
I was thinking along the lines of a DOS book disk equivelent (i.e no device
drivers).
Post by P.T. Breuer
Post by Steve Mowbray
kernal image running (this will at least give me confidence in the process)
Also I did not see any site specific modifications required for 'Makefile'
as a result of building under CygWin - am I mistaken.
Eh? Surely you aren't compiling under windows? That will never fly.
Only a very few compilers can compile the kernel. Read the
instructions! At least the Changes file.
I am using GCC 3.3.1 (cygming special) on CyGwin 1.5.5-1 (instructions state
GCC 2.95.3) will read the changes file.
Post by P.T. Breuer
Peter
P.T. Breuer
2003-11-11 21:10:16 UTC
Permalink
Post by Steve Mowbray
Post by P.T. Breuer
Start with a distros *installed* (not *install*) kernel config.
Not starting from distro - have downloaded kernel 2.4.22 and along with web
The advice stands. Start with a distros installed kernel config.
Slackwares springs to mind.
Post by Steve Mowbray
make clean
Don't.
Post by Steve Mowbray
make mrproper
No. Don't!!!!!!
Post by Steve Mowbray
make clean (again? - it says so in a LinuxHQ man page I found)
Don't.
Post by Steve Mowbray
make xconfig
OK. But menuconfig is easier and more convenient. Personally I edit the
.config and then run make oldconfig.
Post by Steve Mowbray
make dep (stops half way)
Fix the problem. But having a problem indicates that your toolchain is
b0rken.
Post by Steve Mowbray
Post by P.T. Breuer
No such thing. It depends on your peripherals. For example, if you boot
off scsi or ide.
I was thinking along the lines of a DOS book disk equivelent (i.e no device
drivers).
It depends on your peripherals. You need support for the boot medium.
If it's scsi, ide, floppy, ...
Post by Steve Mowbray
Post by P.T. Breuer
Eh? Surely you aren't compiling under windows? That will never fly.
Only a very few compilers can compile the kernel. Read the
instructions! At least the Changes file.
I am using GCC 3.3.1 (cygming special) on CyGwin 1.5.5-1 (instructions state
DON'T!!! Nothing much except 2.95 is guaranteed to work. Some other
compilers might work. 3.anything is practically guarranteed not to
work, in general.
Post by Steve Mowbray
GCC 2.95.3) will read the changes file.
Boot a knoppix or whatever and compile your kernel using standard
toolchains. You can't mess around here!

Peter
Steve Mowbray
2003-11-11 22:19:08 UTC
Permalink
Post by P.T. Breuer
Post by Steve Mowbray
Post by P.T. Breuer
Start with a distros *installed* (not *install*) kernel config.
Not starting from distro - have downloaded kernel 2.4.22 and along with web
The advice stands. Start with a distros installed kernel config.
Slackwares springs to mind.
Okay will try to extract my Mandrake distro kernel config.
Post by P.T. Breuer
Post by Steve Mowbray
make clean
Don't.
Post by Steve Mowbray
make mrproper
No. Don't!!!!!!
Post by Steve Mowbray
make clean (again? - it says so in a LinuxHQ man page I found)
Don't.
Now I am confused - the Linux kernel source README and the LinuxHQ kernel
compile howto list these as necessary steps.
Post by P.T. Breuer
Post by Steve Mowbray
make xconfig
OK. But menuconfig is easier and more convenient. Personally I edit the
.config and then run make oldconfig.
Yep - I am trying to work towards that level of kernel config.
Post by P.T. Breuer
Post by Steve Mowbray
make dep (stops half way)
Fix the problem. But having a problem indicates that your toolchain is
b0rken.
Not completely broke - just for Linux kernel - other software builds work.
Post by P.T. Breuer
Post by Steve Mowbray
Post by P.T. Breuer
No such thing. It depends on your peripherals. For example, if you boot
off scsi or ide.
I was thinking along the lines of a DOS book disk equivelent (i.e no device
drivers).
It depends on your peripherals. You need support for the boot medium.
If it's scsi, ide, floppy, ...
I would like to start out with FDD then incrementally add IDE, network,
protocols and services - hopefully learning loads along the way.

I am trying a two pronged attack at this - top down with Mandrake distro
(learn admin) and bottom up with the kernel (learn internals).
Post by P.T. Breuer
Post by Steve Mowbray
Post by P.T. Breuer
Eh? Surely you aren't compiling under windows? That will never fly.
Only a very few compilers can compile the kernel. Read the
instructions! At least the Changes file.
I am using GCC 3.3.1 (cygming special) on CyGwin 1.5.5-1 (instructions state
DON'T!!! Nothing much except 2.95 is guaranteed to work. Some other
compilers might work. 3.anything is practically guarranteed not to
work, in general.
Eek - exact compiler version required - learning linux from the ground up is
going to be a problem I think.
Post by P.T. Breuer
Post by Steve Mowbray
GCC 2.95.3) will read the changes file.
Boot a knoppix or whatever and compile your kernel using standard
toolchains. You can't mess around here!
Will do - thanks.
Post by P.T. Breuer
Peter
Fredderic
2003-11-14 02:19:05 UTC
Permalink
Post by P.T. Breuer
Post by Steve Mowbray
I am using GCC 3.3.1 (cygming special) on CyGwin 1.5.5-1 (instructions state
DON'T!!! Nothing much except 2.95 is guaranteed to work. Some other
compilers might work. 3.anything is practically guarranteed not to
work, in general.
Just wondering... Is that a CygWin special feature, or a gcc general fact?

Linux version 2.6.0-test7 (***@magentus) (gcc version 3.3.2 20031005
(Debian prerelease)) #1 Mon Oct 27 09:46:23 EST 2003


Fredderic
Lew Pitcher
2003-11-16 04:59:01 UTC
Permalink
Steve Mowbray wrote:
[snip]
Post by Steve Mowbray
steps done so far
make clean
which deletes the results of previous kernel compiles (object, assembly
language, executables, etc).
Post by Steve Mowbray
make mrproper
which deletes your existing config, and gives you a clean slate to build a new
config
Post by Steve Mowbray
make clean (again? - it says so in a LinuxHQ man page I found)
shouldn't be needed if you did it at the beginning. Perhaps a documentation bug?
Post by Steve Mowbray
make xconfig
lets you manipulate your config file (the new one built by mrproper)
Post by Steve Mowbray
make dep (stops half way)
builds compile dependancy lists. You don't need to do this with every kernel
compile, just with the first compile under a new tree (say, after applying a
kernel patch, or moving your kernel source to a new directory).


[snip]
--
Lew Pitcher

Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
Steve Mowbray
2003-11-16 10:08:30 UTC
Permalink
Post by Lew Pitcher
[snip]
Post by Steve Mowbray
steps done so far
make clean
which deletes the results of previous kernel compiles (object, assembly
language, executables, etc).
Post by Steve Mowbray
make mrproper
which deletes your existing config, and gives you a clean slate to build a new
config
Post by Steve Mowbray
make clean (again? - it says so in a LinuxHQ man page I found)
shouldn't be needed if you did it at the beginning. Perhaps a
documentation bug?

yep - but benign I hope
Post by Lew Pitcher
Post by Steve Mowbray
make xconfig
lets you manipulate your config file (the new one built by mrproper)
Post by Steve Mowbray
make dep (stops half way)
builds compile dependancy lists. You don't need to do this with every kernel
compile, just with the first compile under a new tree (say, after applying a
kernel patch, or moving your kernel source to a new directory).
Still trying to get kernel building using CygWin going but no luck yet.
Post by Lew Pitcher
[snip]
--
Lew Pitcher
Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
Gerard Oberle
2003-11-14 22:53:50 UTC
Permalink
Post by P.T. Breuer
Eh? Surely you aren't compiling under windows? That will never fly.
Only a very few compilers can compile the kernel.
I have been thinking of trying exactly the same thing. In case you
are unfamiliar with CygWin, it is a wonderful emulation of Unix under
Win/32. It contains many of the packages available with a typical
Linux install, including gcc and the various libraries, and gnu
config. In theory, therefore, it should be able to compile almost
anything, for a Linux target.

So could you explain why "that will never fly." After all, Linus
compiled the first kernel on something other than Linux, didn't he?
The only other choice was to have poked bits onto a floppy, and I
don't think anyone has done that since the first 1404 was booted.

Thanks in advance.

Cheers!
Jerry Oberle
perl -e 'printf "%silto%c%sberle%cearthlink%cnet%c", "ma", 58, "go",
64, 46, 10;'
P.T. Breuer
2003-11-15 02:10:16 UTC
Permalink
Post by Gerard Oberle
Post by P.T. Breuer
Eh? Surely you aren't compiling under windows? That will never fly.
Only a very few compilers can compile the kernel.
So could you explain why "that will never fly." After all, Linus
Because nobody has tried it. Ordinary variations from compiler to
compiler will result in different compilations, different bugs, and
different failures to compile something. It's already the case that
on x86 only a very few compilers are known to compile the kernel.
The rest won't do it, or do it wrong.

So you get to do a lot of debugging! At assembler level.

Peter
Loading...