qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>, Avi Kivity <avi@redhat.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] write option roms in pc-bios/
Date: Fri, 8 Jan 2010 17:54:57 +0000	[thread overview]
Message-ID: <f43fc5581001080954p73875e29iedc12580d12f8e86@mail.gmail.com> (raw)
In-Reply-To: <128398603.432201262946418786.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>

On Fri, Jan 8, 2010 at 10:26 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>>>> This will wreak havoc on the tree since these are built by default and
>>>>>> they are replacing files in revision control.
>>>>> ... the next question is why are they (linuxboot.bin and multiboot.bin)
>>>>> in revision control since they do not require any strange tool to be built.
>>>> They require an i386 cross compiler, which is not available on all
>>>> installations.
>>>
>>> They are being built always anyway now, since their target
>>> pc-bios/optionrom/linuxboot.bin does not exist on a checked out tree or
>>> even a release tree.  But no one has complained.
>>
>> They are only built on i386 and x86_64 hosts, look at the configure
>> script. We should continue providing all the ROM binaries, even the x86
>> ones.
>
> Oops, my bad. :-(  The only reason I see against my patch is that the option
> ROMS do not change that often; maybe I felt that it should be done different
> only because I screwed up and I'm blaming the code instead of myself.
> There is also the problem that they are not built on Darwin and Solaris,
> which is possibly even worse.
>
> What about adding to version control a stamp file and using it to avoid
> useless changes to pc-bios/*.bin?  Such as overwriting the .bin files only
> when the .S file changes.  Something like the attached patch.

configure could also detect that we are building inside the source
tree (not in an object tree outside of the source directory) and not
compile the roms in that case. Or we could make object tree use
mandatory, it's a good practice anyway.

  reply	other threads:[~2010-01-08 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <668989114.432161262946223474.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-01-08 10:26 ` [Qemu-devel] Re: [PATCH] write option roms in pc-bios/ Paolo Bonzini
2010-01-08 17:54   ` Blue Swirl [this message]
     [not found] <4B337318.6080901@redhat.com>
     [not found] ` <1261664861-15493-1-git-send-email-pbonzini@redhat.com>
2010-01-07 20:03   ` [Qemu-devel] " Anthony Liguori
2010-01-08  7:31     ` [Qemu-devel] " Paolo Bonzini
2010-01-08  7:57       ` Aurelien Jarno
2010-01-08  8:19         ` Paolo Bonzini
2010-01-08  9:12           ` Aurelien Jarno
2010-01-08 12:29       ` Anthony Liguori

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=f43fc5581001080954p73875e29iedc12580d12f8e86@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=aurelien@aurel32.net \
    --cc=avi@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).