From: Jeshua Lacock <jeshua@OpenOSX.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu on Intel Macs
Date: Tue, 31 Jan 2006 22:02:46 -0700 [thread overview]
Message-ID: <ce63c7d800465d1fb47dc6f31afa0f08@OpenOSX.com> (raw)
Greetings,
I am trying to build Qemu on a Intel Mac and after a little bit of work
I got it building. It is having trouble with the "mach-o/ppc/reloc.h"
file. Someone from Apple says:
"Mac OS X's ABI for Intel uses 'generic' relocation entry types, which
are defined in <mach-o/reloc.h>. You can see this by running
'otool -arch i386 -rv /path/to/binary', where the binary is
universal or
Intel-only."
The generic entry types are:
enum reloc_type_generic
{
GENERIC_RELOC_VANILLA, /* generic relocation as discribed above */
GENERIC_RELOC_PAIR, /* Only follows a GENRIC_RELOC_SECTDIFF */
GENERIC_RELOC_SECTDIFF,
GENERIC_RELOC_PB_LA_PTR, /* prebound lazy pointer */
GENERIC_RELOC_LOCAL_SECTDIFF
};
I don't see anything similar to "PPC_RELOC_BR24" . I realize that those
are specific to the PPC and "GENERIC_RELOC_VANILLA" will have to be
used, although I have no idea how to implement them. The scheme should
be pretty similar to the PPC Mach-O port.
The other (most likely related) error is:
struct relocation_info' has no member named 'r_offset'
This is above my understaning, I would be very grateful to pay you for
your help. If you are interested I can create an account for you to log
into. Any help is appreciated. I would be happy to provide the changes
to the Qemu project.
Anyone out there feel qualified to help me get this going? Its a bit
beyond my ability at this time and I would be happy to compensate for
time.
Thanks,
Jeshua Lacock ___________________________
Programmer/Owner Phone: 877.240.1364
http://OpenOSX.com Fax: 415.462.6211
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
next reply other threads:[~2006-02-01 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 5:02 Jeshua Lacock [this message]
2006-02-01 6:48 ` [Qemu-devel] Qemu on Intel Macs Gwenole Beauchesne
2006-02-01 9:14 ` Mike Kronenberg
2006-02-01 20:00 ` Paul Brook
2006-02-01 15:01 ` Paul Brook
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=ce63c7d800465d1fb47dc6f31afa0f08@OpenOSX.com \
--to=jeshua@openosx.com \
--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).