[PATCH] biarch support for i386-mingw32
Robert Millan
rmh@aybabtu.com
Mon Jun 8 15:32:00 GMT 2009
More information about the Binutils mailing list
Mon Jun 8 15:32:00 GMT 2009
- Previous message (by thread): [PATCH] biarch support for i386-mingw32
- Next message (by thread): [PATCH] biarch support for i386-mingw32
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Kai, On Mon, Jun 08, 2009 at 09:27:23AM +0200, Kai Tietz wrote: > > This approach seems to be wrong. It makes no sense to change emulation > for i386 pr-coff targets. This would break i386 default. I tested i386-mingw32 and it continues to work. Can you be more specific? > Instead of your patch you should configure options to enable biarch > for binutils here. > At typical multilib version based on i386-*-mingw* can be configured as: > "../configure --prefix=<prefix-dir> --with-sysroot=<prefix-dir> > --target=i686-w64-mingw32 > --enable-targets=i686-w64-mingw32,x86_64-w64-mingw32 " > > For me this works pretty well and testsuite run works, too. This works for ld, but then "as --64" won't work. My goal is to setup a biarch toolchain, which will later need some adjustments in gcc so that "i586-mingw32msvc-gcc -m64" works. Is there a better way to archieve that? -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all."
- Previous message (by thread): [PATCH] biarch support for i386-mingw32
- Next message (by thread): [PATCH] biarch support for i386-mingw32
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list