From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Andrew Walrond <andrew@walrond.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binutils-2.16 & kernel-2.6.11.10
Date: Sun, 22 May 2005 16:21:42 +0100 [thread overview]
Message-ID: <200505221621.42931.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200505221151.46592.andrew@walrond.org>
On Sunday 22 May 2005 11:51, you wrote:
> On Saturday 21 May 2005 23:59, Herbert Rosmanith wrote:
> > > http://www.kernel.org/pub/linux/devel/binutils/linux-2.6-seg-5.patch
> > > http://www.kernel.org/pub/linux/devel/binutils/linux-2.4-seg-4.patch
> > >
> > > should probably fix that.
> >
> > interesting, that's the same patch (s/movl/movw/), but it is date
> > from *march* 2005.
> >
> > why is this not in the kernel source yet? It is definitely not
> > okay to "movl" a segreg.
>
> I'd also like to know the status of these patches; I've avoided the last
> couple binutils upgrades because of HJL's attached kernel patches and
> implied Linux build problems.
For what it's worth, I recently built an adapted LFS SVN for x86-64, using
HJL's binutils 2.16.90.0.2. A few weeks later, and still no problems.
Literally the only package I had difficulty building was Linux itself, and
the attached patches seem to work fine.
Let's hope they get into mainline shortly.
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/CSim Undergraduate
contact: 1F2 55 South Clerk Street,
Edinburgh. EH8 9PP.
next prev parent reply other threads:[~2005-05-22 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 21:25 Herbert Rosmanith
2005-05-21 21:30 ` Herbert Rosmanith
2005-05-21 22:38 ` Jan Dittmer
2005-05-21 22:59 ` Herbert Rosmanith
2005-05-22 10:51 ` Andrew Walrond
2005-05-22 15:21 ` Alistair John Strachan [this message]
[not found] <E1DZfPw-0001u4-HT@be1.7eggert.dyndns.org>
2005-05-22 7:13 ` Herbert Rosmanith
2005-05-22 7:21 ` Herbert Rosmanith
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=200505221621.42931.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=andrew@walrond.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®