From: Jean Delvare <khali@linux-fr.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Anders Kaseorg <andersk@MIT.EDU>,
Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] modpost: more complete endianness fixing
Date: Mon, 4 May 2009 10:00:45 +0200 [thread overview]
Message-ID: <20090504100045.4bfe5591@hyperion.delvare> (raw)
In-Reply-To: <20090503194848.GA32400@uranus.ravnborg.org>
On Sun, 3 May 2009 21:48:48 +0200, Sam Ravnborg wrote:
> On Sun, May 03, 2009 at 02:07:35PM -0400, Anders Kaseorg wrote:
> > Fix endianness of all the fields in the ELF header and section headers,
> > not just some of them.
> >
> > The missing TO_NATIVE(sechdrs[i].sh_flags) was causing many “unexpected
> > non-allocatable section” warnings when cross-compiling for an architecture
> > with a different endianness.
>
> Thanks Anders.
> Makes sense for the powerpc case.
> But I cannot see it fixing the warnings Jean sees.
>
> Jean?
It indeed didn't help me (but your other fix did.)
--
Jean Delvare
next prev parent reply other threads:[~2009-05-04 8:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 9:05 Lots of unexpected non-allocatable section warnings Jean Delvare
2009-05-03 10:30 ` Sam Ravnborg
2009-05-03 10:42 ` Stephen Rothwell
2009-05-03 18:07 ` [PATCH] modpost: more complete endianness fixing Anders Kaseorg
2009-05-03 19:48 ` Sam Ravnborg
2009-05-04 8:00 ` Jean Delvare [this message]
2009-05-03 10:48 ` Lots of unexpected non-allocatable section warnings Jean Delvare
2009-05-03 18:03 ` Sam Ravnborg
2009-05-03 20:29 ` Sam Ravnborg
2009-05-04 7:58 ` Jean Delvare
2009-05-04 9:51 ` Sam Ravnborg
2009-05-04 8:28 ` Manuel Lauss
2009-05-04 9:49 ` Sam Ravnborg
2009-05-04 9:49 ` Sam Ravnborg
2009-05-04 10:05 ` Manuel Lauss
2009-05-04 15:24 ` David Daney
2009-05-04 15:26 ` David Daney
2009-05-03 18:18 ` Andreas Schwab
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=20090504100045.4bfe5591@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=andersk@MIT.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.