From: Simon Horman <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 1/1] ia64: increase .data.patch offset
Date: Wed, 14 Nov 2007 20:39:03 +0000 [thread overview]
Message-ID: <20071114203850.GA2368@verge.net.au> (raw)
In-Reply-To: <200711130855.lAD8tBWd002649@imap1.linux-foundation.org>
On Tue, Nov 13, 2007 at 02:26:07PM -0800, Andrew Morton wrote:
> On Wed, 14 Nov 2007 09:07:45 +1100 Peter Chubb <peterc@gelato.unsw.edu.au> wrote:
>
> > >>>>> "akpm" = akpm <akpm@linux-foundation.org> writes:
> >
> > akpm> From: Andrew Morton <akpm@linux-foundation.org> I get this:
> >
> > akpm> /opt/crosstool/gcc-3.4.5-glibc-2.3.6/ia64-unknown-linux-gnu/lib/gcc/ia64-unknown-linux-gnu/3.4.5/../../../../ia64-unknown-linux-gnu/bin/ld:
> > akpm> section .data.patch [a000000000000500 -> a000000000000507]
> > akpm> overlaps section .dynamic [a0000000000003c8 -> a000000000000507]
> >
> > If you switch to gcc 4.1 the patch section shrinks again and this patch
> > isn't necessary.
>
> It took me two solid days work to generate my current cross-compile suite.
> Weep.
>
> I spose I can keep this patch locally if that's the direction which i64
> wants to take. But in that case ia64 should #error out early if __GNUC__
> is wrong.
Hi Peter,
can you be a little more specific about what toolchain you are using?
I'm using crosstool but the most recent thing that it seems to like is
gcc-3.4.5 + glibc 2.3.6. I don't mind working on crosstool a bit to get
a newer gcc working, but I'd be grateful of any advice on versions to
avoid too much stabbing in the dark.
--
Horms, California Edition
next prev parent reply other threads:[~2007-11-14 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 8:48 [patch 1/1] ia64: increase .data.patch offset akpm
2007-11-13 22:07 ` Peter Chubb
2007-11-13 22:26 ` Andrew Morton
2007-11-14 20:39 ` Simon Horman [this message]
2007-11-14 23:17 ` Peter Chubb
2007-11-14 23:39 ` Luck, Tony
2007-11-14 23:49 ` Peter Chubb
2007-11-20 2:58 ` Peter Chubb
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=20071114203850.GA2368@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-ia64@vger.kernel.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