From: Andrew Morton <akpm@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH -mm HOT-FIX] fix build on ia64 (modpost.c)
Date: Mon, 20 Feb 2006 21:37:36 +0000 [thread overview]
Message-ID: <20060220133736.2df448c8.akpm@osdl.org> (raw)
In-Reply-To: <20060220192500.GA17003@mars.ravnborg.org>
Sam Ravnborg <sam@ravnborg.org> wrote:
>
> >
> > - This kernel won't compile on ia64 (and possibly other architectures)
> > because the kbuild tree is using Elf_Rela in scripts/mod/modpost.c. Is OK
> > on x86, x86_64 and powerpc. Sam might send a hotfix?
>
> Attached is a real hot-fix. It disables the new check entirely.
Well that bit compiles.
> I like to learn:
> 1) Why IA64 is missing Elf64_Rela. Can someone drop me a copy of elf.h -
> and include gcc + binutils version in the mail - thanks.
This thing's running RHAS2.1 which I think dates from before the invention
of the transistor. Running home-made gcc-3.3.2 and binutils-2.14.90.0.6-1.
I'll send along the three elf.h's under /usr/include.
> 2) I also like to know if other architectures broke - so I can figure
> out how to fix this.
Dunno yet - I didn't do the normal batch of cross-compiles due to spending
six hours chasing down new bugs.
> I have tested this on X86_64/amd64 (gentoo based) only.
That fixes the modpost.c compile, but the new futex stuff fails because
ia64 doesn't implement ptr_to_compat(). In fact only three architectures
appear to do so.
prev parent reply other threads:[~2006-02-20 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060220042615.5af1bddc.akpm@osdl.org>
2006-02-20 19:25 ` [PATCH -mm HOT-FIX] fix build on ia64 (modpost.c) Sam Ravnborg
2006-02-20 21:37 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060220133736.2df448c8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox