Re: 2.4.18 kernel compile
On Fri, 10 May 2002, Richard Fillion wrote:
> This isnt the first time it happens to me, it seems i'm very limited to
> what i can build as far as kernels go. What happens is the following.
> I use the same config (or VERY similar) configs every time i go to
> compile, so there's really is no chance that its "my" fault. I then do
> make dep as usual, and then make vmlinux (anyone know why make vmlinuz
> or bzimage dont work on alphas?).
Those targets are not properly defined in the Makefiles in the alpha parts
of the kernel source, so they won't work properly. The 'bzimage' target
especially shouldn't work since IIRC, there's no "unbzipping" support in
the bootloaders. Making the vmlinuz target work should be trivial,
> fs/fs.o: In function `generic_cont_expand':
> fs/fs.o(.text+0x7074): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7078): undefined reference to `page_cache_release'
> fs/fs.o: In function `cont_prepare_write':
> fs/fs.o(.text+0x7190): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7194): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7250): undefined reference to `page_cache_release'
> fs/fs.o(.text+0x7254): more undefined references to `page_cache_release'
> make: *** [vmlinux] Error 1
> Sometimes its a whole lot more of these errors, other times its less.
> Every time i mention this in #debian i get "thats a gcc problem." and
> when i ask whats wrong with gcc, i get "thats a binutils problem." and
> when i ask whats wrong with binutils i get "thats a kernel problem." As
> you can see, i get nowheres.
If this is the same problem as most of the unresolved references that I've
seen on i386, then this is most definitely a kernel problem. What
happened is that the kernel was placing the code for some symbols in a
section that is discarded by the kernel's linker script, so the symbols
that are in that discarded section cannot be referenced. To see if this
is the same problem, try removing the " *(.text.exit)" entry from the
/DISCARD/ line at the end of arch/alpha/vmlinux.lds.in. If this allows
the kernel to link, then it's definitely the same problem that many of the
drivers exhibit. If this is the case, I can probably provide a patch that
you could submit upstream to fix this (I don't have the available time to
follow-up on a kernel patch personally right now).
> Do any of you know whats going on? I've just be told that 2.4.19 is
> out, and possibly something newer than that, so im going to try those.
Give those a shot and, if they show the same problem, try the above. FYI,
you should've seen a debconf warning when installing the binutils package
that talked about this very problem...(at least for woody and unstable,
which should be the only two dists affected).
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org