From: Keir Fraser <keir@xen.org>
To: "Roger Pau Monné" <roger.pau@entel.upc.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] ipxe: fix compilation issues with some gcc versions
Date: Fri, 16 Dec 2011 13:21:41 +0000 [thread overview]
Message-ID: <CB10F665.361A4%keir@xen.org> (raw)
In-Reply-To: <CAPLaKK7J312vgixP-SpH6VkrUF_WvdFpB7X72viNpiJXyU5UJg@mail.gmail.com>
On 16/12/2011 13:04, "Roger Pau Monné" <roger.pau@entel.upc.edu> wrote:
> 2011/12/16 Keir Fraser <keir.xen@gmail.com>:
>> On 16/12/2011 12:50, "Roger Pau Monne" <roger.pau@entel.upc.edu> wrote:
>>
>>> # HG changeset patch
>>> # User Roger Pau Monne <roger.pau@entel.upc.edu>
>>> # Date 1324039730 -3600
>>> # Node ID 8c0ce135cda382630adc72d64757ec64854ba696
>>> # Parent b60667a56ae085ee2bcea896887d0907fb86af41
>>> ipxe: fix compilation issues with some gcc versions
>>>
>>> Backported some changes from current ipxe, to fix a issue with some
>>> new versions of gcc that add -fPIC by default, and compilation fails
>>> with the following error:
>>
>> Is there a newer release tag on the ipxe repo that we could build instead,
>> that would automatically get us these fixes?
>
> No, latest tag (almost two years ago) is 1.0.0, which is the one we
> are currently using.
Perhaps we should pick a recent commit hash to clone, then? There's plenty
going on in there development-wise, which would surely have warranted a
release or two; it just looks like they couldn't be arsed to tag releases.
Hanging on to a two-year-old version and building up a backport queue
doesn't make sense. At the very least we should do this in xen-unstable, and
get some testing done of recent ipxe upstream.
-- Keir
next prev parent reply other threads:[~2011-12-16 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 12:50 [PATCH] ipxe: fix compilation issues with some gcc versions Roger Pau Monne
2011-12-16 12:59 ` Keir Fraser
2011-12-16 13:04 ` Roger Pau Monné
2011-12-16 13:21 ` Keir Fraser [this message]
2011-12-18 13:26 ` Roger Pau Monné
2011-12-18 14:56 ` Keir Fraser
2011-12-20 12:57 ` Roger Pau Monné
2011-12-20 13:02 ` Keir Fraser
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=CB10F665.361A4%keir@xen.org \
--to=keir@xen.org \
--cc=roger.pau@entel.upc.edu \
--cc=xen-devel@lists.xensource.com \
/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.