public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] binutils: update to 2.25.1
Date: Tue, 05 Apr 2016 12:10:08 +0100	[thread overview]
Message-ID: <1459854608.30749.325.camel@ipfire.org> (raw)
In-Reply-To: <e3f3761d5c8ae11ae12b6098964211cf@mail01.ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

On Tue, 2016-04-05 at 07:21 +0200, Marcel Lorenz wrote:
> Hi,
> 
> sorry, can't test ARM. Have no Hardware. Can you correct the rootfile 
> for me?
> On i586, i have no problems with 2.25.1

There must still be issues when you have to modify lfs/grub to insert PaX
headers into the ELF header. That should not be necessary at all.

-Michael

> 
> Marcel
> 
> Am 2016-04-04 13:51, schrieb Arne Fitzenreiter:
> > 
> > On 2016-04-04 07:24, Marcel Lorenz wrote:
> > > 
> > > Signed-off-by: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
> > > 
> > The arm rootfiles contain intel files now! This patch is broken.
> > 
> > Toolchain parts are really critical and should intensive tested on
> > all arches before changing.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-04-05 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04  5:24 Marcel Lorenz
2016-04-04  5:24 ` [PATCH 2/2] grub: fix build fail Marcel Lorenz
2016-04-04 11:51 ` [PATCH 1/2] binutils: update to 2.25.1 Arne Fitzenreiter
2016-04-05  5:21   ` Marcel Lorenz
2016-04-05 11:10     ` Michael Tremer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-27  8:34 Marcel Lorenz
2016-03-27 13:53 ` Michael Tremer

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=1459854608.30749.325.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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