[Peeweelinux] trouble compiling custom kernel
Jonathan Sturges
[email protected]
Mon, 22 Dec 2003 21:23:59 -0500
Hmmm. What's the significance of the RH62 compat-* packages?
thanks,
Jonathan
----- Original Message -----
From: "Troy Engel" <[email protected]>
To: <[email protected]>
Sent: Monday, December 22, 2003 7:13 PM
Subject: Re: [Peeweelinux] trouble compiling custom kernel
> Hi,
>
> I'm assuming you're following my instructions to make this kernel --
> check two things:
>
> 1) the RH62 compat-* packages are installed, and you are invoking the
> script /usr/i386-glibc21-linux/bin/i386-glibc21-linux-env.sh *prior* to
> running/configuring/building the kernel
>
> 2) that you've edited the kernel Makefile to use "kgcc" instead of "gcc"
> (/usr/bin/kgcc is installed as part of compat-egcs-<VER>.rpm)
>
> -te
>
> Jonathan Sturges wrote:
> > I was able to compile 2.2.25 in gcc 3.2, but the resulting kernel
"Oops"es
> > when initialized on my Advantech boards, which are using National
> > Semiconductor's Geode CPU. You might be right about gcc 3.2 with 2.2.17
> > though. If I cd into the $PWL_HOME/kernelbuild/usr/src/linux, after
trying
> > to make a custom kernel within PWL, and do a 'make bzImage' it does
choke
> > without producing an image.
> >
> > I will try a 2.4 kernel and see how it goes.
> >
> > thanks,
> > Jonathan
> >
> > ----- Original Message -----
> > From: "Ken Emmons, Jr." <[email protected]>
> > To: <[email protected]>
> > Sent: Monday, December 22, 2003 3:05 PM
> > Subject: RE: [Peeweelinux] trouble compiling custom kernel
> >
> >
> >
> >>I think the 2.2 kernel compile will die with GCC 3.2, but I am not sure.
> >
> > Compile a kernel version (2.4 something) that will work with your
compiler
> > (view the README docs in the kernel source for where to findd out what
> > version of GCC to use). If you can, compile everything static, so you
don't
> > have to deal with modules.
> >
> >>Now you need to Copy the bzImage file (your compiled kernel) into your
> >
> > peewee projects "custom" folder. This custom folder mimics the root
> > filesystem of your target, which allows you to overwrite or add files.
Make
> > a "boot" directory if it is not already there, and put your bzImage file
> > there. If you don't need modules, you are now done. Otherwise, copy all
of
> > your module files intot he appropriate directories, and hope it works.
> >
> >>
> >>~Ken
> >>
> >>
> >>
> >>
> >>
> >>>-----Original Message-----
> >>>From: Jonathan Sturges [mailto:[email protected]]
> >>>Sent: Monday, December 22, 2003 2:52 PM
> >>>To: [email protected]
> >>>Subject: [Peeweelinux] trouble compiling custom kernel
> >>>
> >>>
> >>>Hi,
> >>>I'm a PWL newbie. I've been playing with 0.61.1 for a week
> >>>or so now and
> >>>have made several successful test images with it... pretty
> >>>darn intuitive
> >>>and easy!
> >>>
> >>>However I cannot seem to compile a custom kernel from the
> >>>2.2.17 sources
> >>>that came with PWL. It never seems to produce a bzImage.
> >>>
> >>>I was able to follow some directions I found in the list
> >>>archive and build a
> >>>kernel outside of PWL and bring that in... that did work for
> >>>me though.
> >>>
> >>>FWIW, my host OS is RH 8.0 with gcc 3.2; is that likely a
> >>>problem area or is
> >>>the host platform pretty flexible with PWL?
> >>>
> >>>thanks,
> >>>Jonathan
> >>>
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>Peeweelinux mailing list
> >>>[email protected]
> >>>http://mail.adis.on.ca/lists/listinfo/peeweelinux
> >>>
> >>
> >>_______________________________________________
> >>Peeweelinux mailing list
> >>[email protected]
> >>http://mail.adis.on.ca/lists/listinfo/peeweelinux
> >>
> >
> >
> >
> > _______________________________________________
> > Peeweelinux mailing list
> > [email protected]
> > http://mail.adis.on.ca/lists/listinfo/peeweelinux
>
> --
> Troy Engel, Systems Engineer
> we code so you don't have to
>
> _______________________________________________
> Peeweelinux mailing list
> [email protected]
> http://mail.adis.on.ca/lists/listinfo/peeweelinux