Re: Two linkers - EFI one (mingw64) and normal GNU one [Fedora]

[Doug Goldstein <cardoe@cardoe.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1424 bytes --]

On 2/15/16 8:26 AM, Konrad Rzeszutek Wilk wrote:
> On Mon, Feb 15, 2016 at 02:32:45AM -0700, Jan Beulich wrote:
>>>>> On 12.02.16 at 18:19, <konrad.wilk@oracle.com> wrote:
>>> Fedora for the longest time seems to have two linkers - one normal for GNU
>>> applications and then another - mingw64 - for building EFI applications.
>>>
>>> Which means that to compile ELF binaries on Fedora requires this patch
>>> (taken from Fedora build):
>>
>> This seems completely backwards: Just like we (SUSE) did, they
>> should really configure their binutils package with
>> --enable-targets=<arch>-pep. I absolutely cannot see why a
>> MingW64 linker should be used to generate EFI binaries. Yes,
>> both use the same binary container format, but beyond that
>> there's nothing common here: EFI binaries are of no use in a
>> MingW64 environment (afaict at least), but are nowadays an
>> integral part of an OS installation (i.e. a Linux distro in this case).
>>
>>> +LD_EFI ?= $(LD)
>>
>> Why couldn't you just probe the binary location(s) you know about
>> here? But in any case this would perhaps need better integration
>> with the checking done in xen/arch/x86/efi/Makefile.
> 
> <nods>
> I can certainly do that.
> 
> Doug, does Gentoo have it in some other locations?
>>
>> Jan
>>

Gentoo does --enable-targets=<arch>-pep so our default ld can generate
EFI binaries.

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel