RE: binutils-cvs built for x86_64 PE Interix 6 - now then?

["Duft Markus" <Markus dot Duft at salomon dot at>]

Hi!

A while ago i experimented with Interix (3.5, x86, not x86_64) and binutils/gcc too and my result was that GCC (4.2) works ok, but only when using the native (some very old GNU binutils) ld and as.

I used 2.17 binutils, which i managed to compile without too much trouble, but ld and as didn't work correctly. While as seems to work, but gets some input from gcc it doesn't like (i don't remember exactly), ld wasn't able to link any basic executable.

Maybe this helps!

Cheers, Markus

Jerker Bäck <> wrote:
> Hello all,
> 
> I just built binutils from CVS for x86_64 PE (Interix Vista x64 SUA).
> However, I'm not quite sure what I got - need a test-suite to run. To
> be frank, I didn't expect it to go so smoothly. Doing a "make check"
> didn't turn into any tests.
> 
> Any advise would be most helpful.
> 
> Environment and tools used:
> Interix SDK for Vista x64 SUA
> GNU make
> Compiler and linker: cc script (targeting MS x64 compiler
> 14.00.50727.762). 
> 
> What I did:
> Adding target "x86_64-*-interix*" to source, basically copying
> "x86_64-*-mingw*" settings.
> $ ../configure --prefix=/opt/gcc-4.2.0
> $ make
> Compiled just out of the box except for two minor corrections:
> 
> bfd/doc/Makefile.in(612) - moved $(srcdir)/chew.c to end of line.
> 
> bfd macro STRING_COMMA_LEN gives "error C2099: initializer is not a
> constant" so I changed it to:
> bfd/bfd-in2.h(58)
> #define STRING_COMMA_LEN(STR) (STR), (sizeof (STR) - 1)
> 
> By the way:
> Anyone knows anything about x86_64 PE GCC? I can't find any
> "x86_64-*-mingw*" in the gcc source.
> 
> Regards Jerker


-- 


Salomon Automation GmbH - Friesachstrasse 15 - A-8114 Friesach bei Graz
Sitz der Gesellschaft: Friesach bei Graz
UID-NR:ATU28654300 - Firmenbuchnummer: 49324 K
Firmenbuchgericht: Landesgericht für Zivilrechtssachen Graz