rebranding a i386 binary to be a amd64 binary
jrisom at gmail.com
Wed Oct 10 23:38:47 PDT 2007
On Oct 11, 2007, at 1:34 AM, Aryeh Friedman wrote:
> On 10/11/07, Kris Kennaway <kris at freebsd.org> wrote:
>> Aryeh Friedman wrote:
>>> Even though I know this is asking for it I want to test the new
>>> driver on amd64 and the only issue with a hand compile (from nVidia's
>>> tar not the ports one) is src/nv-kernel.o is branded elf-i386-32 and
>>> amd64 wants it branded elf-amd64-64. This file comes from them as a
>>> precompiled object so rebranding seems to be my only option.
>>> freebsd-questions at freebsd.org mailing list
>>> To unsubscribe, send any mail to
>>> "freebsd-questions-unsubscribe at freebsd.org"
>> Uh it really is an i386 binary, "rebranding" won't magically change
>> the code.
> All I want to do is make it compile so I can test it (like I said I
> know it is inherently dangerous)
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
It's not inherently dangerous, it's not possible. What you need to do
is disassemble the code(probably illegal), port it to amd64, and
reassemble it. It would require intimate knowledge of i386 asm and
amd64 asm. The architectures are more different than you might expect.
More information about the freebsd-questions