qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] QEMU 0.11.0-rc1 broken on OpenBSD.


From: Brad
Subject: Re: [Qemu-devel] QEMU 0.11.0-rc1 broken on OpenBSD.
Date: Mon, 3 Aug 2009 18:41:38 -0400
User-agent: KMail/1.9.10

On Monday 03 August 2009 15:24:09 Anthony Liguori wrote:
> Brad wrote:
> > Trying to compile QEMU 0.11.0-rc1 on OpenBSD/i386 it is broken at the
> > moment..
> >
> > gmake[1]: Entering directory
> > `/stuff/ports/emulators/qemu.new/w-qemu-0.11.0-rc1/qemu-0.11.0-rc1/pc-bio
> >s/optionrom' cc -Wall -Wstrict-prototypes -Werror -fomit-frame-pointer
> > -fno-builtin
> > -I/stuff/ports/emulators/qemu.new/w-qemu-0.11.0-rc1/qemu-0.11.0-rc1
> > -fno-stack-protector -o
>
> Is cc not gcc?
>
> > multiboot.o -c multiboot.S
> > multiboot.S: Assembler messages:
> > multiboot.S:116: Error: `%es:-4(%edi)' is not a valid 16 bit base/index
>
> Yeah, that does look suspicious.  I think:
>
> movl %ecx, %es:-4(%di)
>
> Would be more correct.  Alex?
>
> Regards,
>
> Anthony Liguori

Gets a bit further along..

gmake[1]: Entering directory 
`/stuff/ports/emulators/qemu.new/w-qemu-0.11.0-rc1/qemu-0.11.0-rc1/pc-bios/optionrom'
cc -Wall -Wstrict-prototypes -Werror -fomit-frame-pointer -fno-builtin 
-I/stuff/ports/emulators/qemu.new/w-qemu-0.11.0-rc1/qemu-0.11.0-rc1 
-fno-stack-protector -o 
multiboot.o -c multiboot.S
ld -Ttext 0 -e _start -s -o multiboot.img multiboot.o
objcopy -O binary -j .text multiboot.img multiboot.raw
/stuff/ports/emulators/qemu.new/w-qemu-0.11.0-rc1/qemu-0.11.0-rc1/pc-bios/optionrom/signrom.sh
 
multiboot.raw multiboot.bin
od: unknown option -- A
od: od(1) has been deprecated for hexdump(1).
usage: od [-aBbcDdeFfHhIiLlOovXx] [-j offset] [-N length] [-t type_string]
        [[+]offset[.][Bb]] [file ...]
/stuff/ports/emulators/qemu.new/w-qemu-0.11.0-rc1/qemu-0.11.0-rc1/pc-bios/optionrom/signrom.sh[31]:
   
* 512 - 1 : unexpected `*'
gmake[1]: *** [multiboot.bin] Error 1

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]