| 1 |
On 20/04/16 03:41 PM, Anthony G. Basile wrote: |
| 2 |
> On 4/20/16 3:30 PM, Ian Stakenvicius wrote: |
| 3 |
>> On 20/04/16 03:01 PM, Anthony G. Basile wrote: |
| 4 |
>> |
| 5 |
>>> The way I think of it is |
| 6 |
>> |
| 7 |
>>> the operating system (ie kernel) = kernel_Winnt the system |
| 8 |
>>> libraries (=~libc) = elibc_Winnt the executable binary format |
| 9 |
>>> = win32 |
| 10 |
>> |
| 11 |
>>> I don't know that we need an executable binary format flag, but |
| 12 |
>>> we might because they're working on windows 10 so it can natively |
| 13 |
>>> run ELF. |
| 14 |
>> |
| 15 |
>> |
| 16 |
>> |
| 17 |
>> According to 'file' the binary format is actually "PE32 executable |
| 18 |
>> (console) Intel 80386, for MS Windows" for a random *.exe file in my |
| 19 |
>> /usr/i686-w64-mingw32/usr/bin |
| 20 |
>> |
| 21 |
>> I assume PE32 would be the label one would use if comparing to ELF ? |
| 22 |
>> |
| 23 |
> |
| 24 |
> yes and while it is reported by `file` as PE32, it is sometimes referred |
| 25 |
> to as just win32. its proper name, if i recall correctly is "Win32 |
| 26 |
> Portable Executable File Format". it is the equivalent of ELF, COFF and |
| 27 |
> a.out in the Linux world and Mach-O in the Mac world. basically its the |
| 28 |
> format the linker/loader is looking for. |
| 29 |
> |
| 30 |
> if i've understood the plans for windows 10, its kernel will be able to |
| 31 |
> link/load native ELF and execute Linux system calls, at least for amd64 |
| 32 |
> arch/abi. I saw a demonstration with ubuntu userland, but i'm sure it |
| 33 |
> will be able to handle gentoo. with gentoo portage in there, i think |
| 34 |
> we'll expand in to a whole new market. |
| 35 |
> |
| 36 |
> not meaning to steal your thread, but i think keeping the namespace |
| 37 |
> precise here will help us avoid collisions in the future. |
| 38 |
> |
| 39 |
> |
| 40 |
|
| 41 |
Right, so a +1 for USE="winapi" then? |
Archives