3 messages in net.sourceforge.lists.etherboot-developersRe: [Etherboot-developers] [PATCH] mo...
FromSent OnAttachments
Glauber CostaOct 14, 2008 9:17 am 
Michael BrownOct 15, 2008 9:13 am 
Eduardo HabkostOct 15, 2008 10:36 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [Etherboot-developers] [PATCH] move RM_FRAGMENT to the beginning of undi.cActions...
From:Eduardo Habkost (ehab@redhat.com)
Date:Oct 15, 2008 10:36:52 am
List:net.sourceforge.lists.etherboot-developers

On Wed, Oct 15, 2008 at 05:13:23PM +0100, Michael Brown wrote:

On Tuesday 14 October 2008 17:17:34 Glauber Costa wrote:

I'm currently facing a compile problem with gcc 4.3.0 at undi.c Looking at the generated code, it seems gcc is inlining _undi_call into _undi_call_silent, thus making rm_undi_call be defined twice.

Using gcc option -fno-inline also fixes this, but then the compiler won't do any kind of inlining, even "good" ones, so this fix seem to do the right thing.

Thank you for reporting this. Etherboot 5.4 is obsolete and no longer maintained. Would you consider upgrading to gPXE instead?

Yes, but right now most Qemu and KVM installs today are using Etherboot instead, as upstream Qemu and KVM carries Etherboot pxe images when installed.

The problem fixed by Glauber was found while we were doing the packaging of Etherboot for Fedora[1]. The problem is not critical, as probably there are not no users of the packaged Etherboot images on Fedora yet, except for the three or four PXE images used by Qemu and KVM.

We plan to first properly package the same Etherboot images that are used right now by Qemu and KVM, and then moving to gPXE (as moving to gPXE would need more testing work to make sure it works properly under Qemu and KVM).

[1] https://bugzilla.redhat.com/show_bug.cgi?id=464621