Re: Can't compile an exact copy of kernel image.
On Fri, Oct 05, 2001 at 04:14:34PM -0300, Ricardo Gazoni wrote:
>
>
> Ricardo Gazoni gravada:
>
> > Osamu Aoki gravada:
> >
> > > On Thu, Oct 04, 2001 at 09:36:24PM -0300, Ricardo Gazoni wrote:
> > > > Yes, I did. In fact, step 1 loaded /boot/config-2.2.19pre17 and
> > > > saved it in /usr/src/kernel-source-2.2.19pre17/.config. To be
> > > > precise, doing this via make xconfig only adds comment lines to
> > > > the .config file. I checked it out carefully....
> > > >
> > > > > > Everything worked just fine until now. But the old kernel image
> > > > > > (vmlinuz-2.2.19pre17) is 1.001.473 bytes long, and the new one
> > > > > > (vmlinuz-2.2.19foo17) is 1.033.565 bytes long. But the worst thing
> > > > > > is that the new kernle doesn't boot. What am I doing wrong??
> > >
>
> OK: just compiled bypassing xconfig: worked fine!!! It seems that
> there were some configuration variables (marked NEW in make config)
> that were not set in the old kernel configuration file, and xconfig
> assumed as set to Y. Thats why the new kernel was 30k bigger...
>
"make oldconfig" maybe something you wanted to use to update .config.
But since you are configuring same version of kernel, it is strange.
Most likely, you may have sit some check box inadvently. :-)
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~
+ Osamu Aoki <debian@aokiconsulting.com>, GnuPG-key: 1024D/D5DE453D +
+ My debian quick-reference, http://www.aokiconsulting.com/quick/ +
Reply to: