on 15/12/2008 16:27 Eygene Ryabinkin said the following:
> Andriy, good day.
>
> Mon, Dec 15, 2008 at 02:08:15PM +0200, Andriy Gapon wrote:
>> on 12/12/2008 13:17 Andriy Gapon said the following:
>>> Just in case anybody still remembers this issue.
>>> It seams that the main culprit here was the following line in the linker
>>> script:
>>>
>>> OUTPUT_FORMAT("elf32-i386");
>>>
>>> I was tipped just today that it should have read:
>>> OUTPUT_FORMAT("elf32-i386-freebsd", "elf32-i386-freebsd",
>>> "elf32-i386-freebsd");
>> In fact it was Stephan Eisvogel who provided me with this hint.
>
> Yes, it is a somewhat known culprit. A number of packages that are
> messing with assembly code have troubles due to this directive. The
> better way to overcome this issue is not to patch linker scripts, but to
> override object format via '--oformat elf32-i386-freebsd' command-line
> switch to ld(1). With this your proposed patch could be made even
> smaller, providing that you can override linker command-line switches,
> and it will be more robust in respect to the patching troubles when
> linker scripts will be changed.
Eygene,
thanks a lot! this option is indeed sufficient.
--
Andriy Gapon
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
