From: Bartlomiej Celary <bartlomiej.celary@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] MINGW: Unable to link multiboot.img + strnlen missing
Date: Fri, 10 Jul 2009 17:36:55 +0200 [thread overview]
Message-ID: <97c31bd80907100836sb6c32d2kb9da6b0832a4223b@mail.gmail.com> (raw)
In-Reply-To: <0A41868E-F505-4397-A957-EF875AB28F08@suse.de>
Hi,
Just tried latest pull from git and noticed the "cannot perform PE
operations on non PE output file 'multiboot.img'." error.
Is there any agreement on how to fix the linker issue under mingw?
Thanks,
Bartek Celary
2009/7/1 Alexander Graf <agraf@suse.de>:
>
> On 01.07.2009, at 17:52, Anthony Liguori wrote:
>
>> Alexander Graf wrote:
>>>
>>> Why can't we just exclude mingw from building option roms? Let's just
>>> treat it like any non-x86 platform, so it takes the binary blobs.
>>
>> The signrom problem is independent on mingw32. This makefile is doing
>> something that the rest of the build system is careful not to do: compile a
>> binary and run it as part of the build process.
>>
>> That's why hxtool is not written in C.
>
> Well, the optionrom directory is a first of its kind: Full source to a
> binary blob.
> So would you prefer to have signrom be in sh? :-)
>
> Maybe I could come up with a version in brainfuck though ... hum
>
> Alex
>
>
next prev parent reply other threads:[~2009-07-10 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 13:04 [Qemu-devel] MINGW: Unable to link multiboot.img + strnlen missing Bartlomiej Celary
2009-07-01 13:24 ` Anthony Liguori
2009-07-01 14:35 ` Alexander Graf
2009-07-01 15:52 ` Anthony Liguori
2009-07-01 15:55 ` Alexander Graf
2009-07-10 15:36 ` Bartlomiej Celary [this message]
2009-07-10 16:03 ` Anthony Liguori
2009-07-01 18:01 ` [Qemu-devel] [PATCH] Win32: Fix build (no strnlen) Stefan Weil
2009-07-01 18:44 ` [Qemu-devel] " Consul
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=97c31bd80907100836sb6c32d2kb9da6b0832a4223b@mail.gmail.com \
--to=bartlomiej.celary@gmail.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).