[gPXE-devel] Fwd: Re: [Xen-devel] tools: gpxe link error

[Keir Fraser]

On 19/07/2010 16:59, "Stefan Hajnoczi" <stefanha at gmail.com> wrote:

> You can get around this for now by *undoing* the following change:
> diff --git a/src/Makefile b/src/Makefile
> index 059c558..ffa046f 100644
> --- a/src/Makefile
> +++ b/src/Makefile
> @@ -95,7 +95,8 @@ INCDIRS               += include .
>  # Default build target: build the most common targets and print out a
>  # helpfully suggestive message
>  #
> -all : bin/blib.a bin/gpxe.dsk bin/gpxe.iso bin/gpxe.usb bin/undionly.kpxe
> +all : bin/blib.a bin/gpxe.dsk bin/gpxe.iso bin/gpxe.usb bin/undionly.kpxe \
> +      bin/rtl8139.rom
>         @$(ECHO) '==========================================================='
>         @$(ECHO)
>         @$(ECHO) 'To create a bootable floppy, type'
> 
> ROMs need to have explicit PCI vendor and device IDs, which are put in
> the ROM header so the BIOS can load them for appropriate PCI devices.
> 
> Hope this helps.  We need to fix this in gpxe.git.

Christoph: Please test this and, if it works for you, submit it as a patch
against our gpxe tarball, as you did for your previous patch.

> Keir: Are you tracking gpxe.git/master for Xen?  Thanks for letting
> gpxe-devel know about this issue.

No we have a tarball snapshot of the git repository, originally taken in
September 2008 and never updated since. The issue here is that afaik you
don't do releases out of your repository, so it's not like we could pull
your repo and check out a tagged release. I could clone your repo in our
build system, and check out a known changeset which I update across stable
releases of Xen, I suppose. The original thinking is that I want our builds
to be reasonably deterministic, and taking a snapshot tarball is easy.

Is there any structure in your git repo in terms of stable versus
development branches? That is, are we guaranteed to get a pretty good set of
bits generated from any pull of the main branch of your public repository?

 Thanks,
 Keir