Date: Sun, 17 Jun 2012 20:52:11 -0400 From: Eric McCorkle <eric@shadowsun.net> To: freebsd-hackers@freebsd.org Subject: Re: EFI development tools Message-ID: <4FDE7BBB.7040704@shadowsun.net> In-Reply-To: <2d9e0a80-658b-438f-90f0-1f510fb1cdd8@email.android.com> References: <4FDBBACF.9040809@shadowsun.net> <4FDE5E19.5050705@shadowsun.net> <2d9e0a80-658b-438f-90f0-1f510fb1cdd8@email.android.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/17/12 8:43 PM, Mike Meyer wrote: > Eric McCorkle <eric@shadowsun.net> wrote: > >> The -m32 flag seems to be the culprit; removing it fixes the problem. >> >> This is why I was having problems, as the offsets in EFI_SYSTEM_TABLE >> were wrong. >> >> In any case, this is a pretty serious error, and someone should try to >> reproduce it and take a look at it. > > This is a known issue, and had been around for a long time. You can't reliably build 32 bit binaries (what the -m32 flag specifies) on a 64 bit system. The header files (and possibly other things) are wrong. > > Doesn't look like anyone has opened a PR for it. > I just did. I'll keep that in mind, as I'm working on the 32-bit EFI implementation on a 64-bit machine. In the short term, I'll edit efibind.h (or wherever UINT64 is defined in the efi hierarchy) in my checkout and add a workaround. That should, in theory, hold.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FDE7BBB.7040704>