Date: Mon, 15 Dec 2008 16:37:18 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: rea-fbsd@codelabs.ru Cc: freebsd-hackers@freebsd.org Subject: Re: memtest86+ on freebsd Message-ID: <49466B9E.1090900@icyb.net.ua> In-Reply-To: <UtxGBGuVuemk8OcS1gDPEw78Aok@VULTLOHGNlPnB6yOjbBvjMB9mrA> References: <4909DC03.1080901@icyb.net.ua> <20081030184625.GA99398@server.vk2pj.dyndns.org> <490B05BA.9090306@icyb.net.ua> <4942483D.8000003@icyb.net.ua> <494648AF.6010009@icyb.net.ua> <UtxGBGuVuemk8OcS1gDPEw78Aok@VULTLOHGNlPnB6yOjbBvjMB9mrA>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49466B9E.1090900>