Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants
Hi, On Mon, Jun 1, 2015 at 12:25 PM, Jacek Caban wrote: > On 06/01/15 10:53, İsmail Dönmez wrote: >> On Thu, May 28, 2015 at 8:58 PM, İsmail Dönmez wrote: >>> On Thu, May 28, 2015 at 6:51 PM, Jacek Caban wrote: >>>> >>>> I committed the change, but I noticed that you modified winnt.h from >>>> widl directory. I removed that part because that's just an internal side >>>> effect of importing it from Wine. The one we care about is in >>>> mingw-w64-headers/include. >>> Btw, without winnt.h change, I still cannot compile the example >>> program from >>> http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx >>> so I think, it also should be applied. >> Would you mind applying the winnt.h part too? I guess it wouldn't hurt >> to keep those definitions in sync. > > As I said, winnt.h from widl directory is not meant to be used to build > anything with mingw-w64 except internal widl usage. Please prepare and > test a patch for mingw-w64-header/include/winnt.h. Now I get it, please see the attached patch. diff --git a/mingw-w64-headers/include/winnt.h b/mingw-w64-headers/include/winnt.h index bfecb7b..8d8bd0d 100644 --- a/mingw-w64-headers/include/winnt.h +++ b/mingw-w64-headers/include/winnt.h @@ -5878,6 +5878,7 @@ __buildmemorybarrier() #define IMAGE_SUBSYSTEM_XBOX 14 #define IMAGE_SUBSYSTEM_WINDOWS_BOOT_APPLICATION 16 +#define IMAGE_DLLCHARACTERISTICS_HIGH_ENTROPY_VA 0x0020 #define IMAGE_DLLCHARACTERISTICS_DYNAMIC_BASE 0x0040 #define IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY 0x0080 #define IMAGE_DLLCHARACTERISTICS_NX_COMPAT 0x0100 @@ -5886,6 +5887,7 @@ __buildmemorybarrier() #define IMAGE_DLLCHARACTERISTICS_NO_BIND 0x0800 #define IMAGE_DLLCHARACTERISTICS_APPCONTAINER 0x1000 #define IMAGE_DLLCHARACTERISTICS_WDM_DRIVER 0x2000 +#define IMAGE_DLLCHARACTERISTICS_GUARD_CF 0x4000 #define IMAGE_DLLCHARACTERISTICS_TERMINAL_SERVER_AWARE 0x8000 #define IMAGE_DIRECTORY_ENTRY_EXPORT 0 -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants
On Thu, May 28, 2015 at 8:58 PM, İsmail Dönmez wrote: > On Thu, May 28, 2015 at 6:51 PM, Jacek Caban wrote: >> On 05/28/15 17:29, İsmail Dönmez wrote: >>> On Thu, May 28, 2015 at 4:49 PM, Jacek Caban wrote: >>>> On 05/28/15 11:06, İsmail Dönmez wrote: >>>>> On Mon, May 25, 2015 at 7:47 PM, İsmail Dönmez wrote: >>>>>> Hi, >>>>>> . >>>>>> Noticed while trying to compile the application from >>>>>> http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx . >>>>>> >>>>>> Patch attached. >>>>> ping? >>>>> >>>> Looks good to me. >>> Could you please apply it? Thanks! >> >> I committed the change, but I noticed that you modified winnt.h from >> widl directory. I removed that part because that's just an internal side >> effect of importing it from Wine. The one we care about is in >> mingw-w64-headers/include. > > Btw, without winnt.h change, I still cannot compile the example > program from > http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx > so I think, it also should be applied. Would you mind applying the winnt.h part too? I guess it wouldn't hurt to keep those definitions in sync. ismail -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants
On Thu, May 28, 2015 at 6:51 PM, Jacek Caban wrote: > On 05/28/15 17:29, İsmail Dönmez wrote: >> On Thu, May 28, 2015 at 4:49 PM, Jacek Caban wrote: >>> On 05/28/15 11:06, İsmail Dönmez wrote: >>>> On Mon, May 25, 2015 at 7:47 PM, İsmail Dönmez wrote: >>>>> Hi, >>>>> . >>>>> Noticed while trying to compile the application from >>>>> http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx . >>>>> >>>>> Patch attached. >>>> ping? >>>> >>> Looks good to me. >> Could you please apply it? Thanks! > > I committed the change, but I noticed that you modified winnt.h from > widl directory. I removed that part because that's just an internal side > effect of importing it from Wine. The one we care about is in > mingw-w64-headers/include. Btw, without winnt.h change, I still cannot compile the example program from http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx so I think, it also should be applied. Regards, ismail -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants
On Thu, May 28, 2015 at 6:51 PM, Jacek Caban wrote: > On 05/28/15 17:29, İsmail Dönmez wrote: >> On Thu, May 28, 2015 at 4:49 PM, Jacek Caban wrote: >>> On 05/28/15 11:06, İsmail Dönmez wrote: >>>> On Mon, May 25, 2015 at 7:47 PM, İsmail Dönmez wrote: >>>>> Hi, >>>>> . >>>>> Noticed while trying to compile the application from >>>>> http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx . >>>>> >>>>> Patch attached. >>>> ping? >>>> >>> Looks good to me. >> Could you please apply it? Thanks! > > I committed the change, but I noticed that you modified winnt.h from > widl directory. I removed that part because that's just an internal side > effect of importing it from Wine. The one we care about is in > mingw-w64-headers/include. Thanks! > Also, I can see that we already forked ddk fro ReactOS, but it would be > nice to contribute the change to them. I'll send a patch to them too. ismail -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants
On Thu, May 28, 2015 at 4:49 PM, Jacek Caban wrote: > On 05/28/15 11:06, İsmail Dönmez wrote: >> On Mon, May 25, 2015 at 7:47 PM, İsmail Dönmez wrote: >>> Hi, >>> . >>> Noticed while trying to compile the application from >>> http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx . >>> >>> Patch attached. >> ping? >> > > Looks good to me. Could you please apply it? Thanks! -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants
On Mon, May 25, 2015 at 7:47 PM, İsmail Dönmez wrote: > Hi, > . > Noticed while trying to compile the application from > http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx . > > Patch attached. ping? -- ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] [PATCH] Add some missing IMAGE_DLLCHARACTERISTICS_* constants
Hi, . Noticed while trying to compile the application from http://blogs.msdn.com/b/oldnewthing/archive/2015/05/18/10615339.aspx . Patch attached. Thanks, ismail dll_character.patch Description: Binary data -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] LLVM and CLang 2.8 with mingw-w64
Hi; On Sat, Oct 9, 2010 at 10:35 AM, Ozkan Sezer wrote: > On Sat, Oct 9, 2010 at 8:41 AM, Dongsheng Song > wrote: > > On Sat, Oct 9, 2010 at 11:28, Jon <10wa...@gmail.com> wrote: > >> On 10/7/10, Dongsheng Song wrote: > >>> > c:\gcc-4.5-w32\bin\../lib/gcc/i686-w64-mingw32/4.5.2/../../../../i686-w64-mingw32/include/_mingw.h:235:0: > >>> note: this is the location of the previous definition > >>> In file included from > >>> C:\var\tmp\llvm-2.8\lib\System\DynamicLibrary.cpp:49:0: > >>> C:\var\tmp\llvm-2.8\lib\System\/Win32/DynamicLibrary.inc: In static > >>> member function 'static bool > >>> llvm::sys::DynamicLibrary::LoadLibraryPermanently(const char*, > >>> std::string*)': > >>> C:\var\tmp\llvm-2.8\lib\System\/Win32/DynamicLibrary.inc:103:64: > >>> error: invalid conversion from 'BOOL (*)(CHAR*, llvm::ModuleBaseType, > >>> ULONG, void*)' to 'WINBOOL (*)(const CHAR*, ULONG, ULONG, void*)' > >>> C:\var\tmp\llvm-2.8\lib\System\/Win32/DynamicLibrary.inc: In static > >>> member function 'static void* > >>> llvm::sys::DynamicLibrary::SearchForAddressOfSymbol(const char*)': > >>> C:\var\tmp\llvm-2.8\lib\System\/Win32/DynamicLibrary.inc:158:23: > >>> warning: ISO C++ forbids casting between pointer-to-function and > >>> pointer-to-object > >>> gmake[2]: *** > [lib/System/CMakeFiles/LLVMSystem.dir/DynamicLibrary.cpp.obj] > >>> Error 1 > >>> gmake[1]: *** [lib/System/CMakeFiles/LLVMSystem.dir/all] Error 2 > >>> gmake: *** [all] Error 2 > >>> > >> You should ask the llvm and clang developers for help. > >> > > > > No, this is a mingw-w64 issue, because I can compile LLVM and CLang > > 2.8 by mingw32 > > compiler smoothly. > > > > No, this is not a mingw-w64 problem, because LLVM assumes that for > non-MSVC compilers EnumerateLoadedModules() has a non-const first > argument which is not correct for us: It should check against the > value of the API_VERSION_NUMBER macro from imagehlp.h or dbghelp.h > which is 11 which indicates the new api with many functions have > constified arguments. (PS: They also assume that mingw does not > have a dbghelp.h header: mingw.org does not, but mingw-w64 has it.) > If you can cook up a simple testcase I'll report an LLVM bug. Regards, ismail -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi there; FWIW gcc 4.6 fails much later with some undefined symbols. I gave up on my quest to create a mingw-w64 canadian cross, for now. Regards, ismail -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi; On Mon, Sep 6, 2010 at 1:02 PM, Pete Batard wrote: > For those interested, I recently blogged about how one can get a working > multilib MinGW-w64 on Linux, which includes how to work around the > "skipping incompatible" errors [1]. > > I'm pretty sure there's a much better way than what I did (for one > thing, I didn't use --with-sysroot), and it's likely newer versions of > the tools have changed the deal yet again, but maybe that can be of some > help. > Tried this and ended up with lots of unresolved symbol errors. For now I think canadian-cross multilib is not an option for mingw-w64. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi; On Mon, Sep 6, 2010 at 11:47 AM, JonY wrote: > Did you link lib to lib64? And do you have lib32? Native cross-back works > fine for me. > > I do link lib64 to lib and I have lib32. > Are you talking about a triple cross? I tried > i686-linux->sparc-linux-mingw64 before, it works fine too. > x86_664-apple-darwin10 -> x86_64-w64-mingw32 > You might have better chance with makebuildroot-test.mk for canadian > cross, I've used it for the sparc triple cross. > I will test this. It would be nice if the usual methods worked though. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
On Mon, Sep 6, 2010 at 11:45 AM, İsmail Dönmez wrote: > Hi; > > On Mon, Sep 6, 2010 at 11:41 AM, Kai Tietz wrote > >> just for getting you right. Does initial cross-compiler fails, or then >> the build of the canadian cross based on this cross-compiler? >> >> > Initial gcc is fine, it fails in the "Finishing GCC [ > FNSHGC]" part mentioned in the gcc. > > mentioned in the wiki* ismail. -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi; On Mon, Sep 6, 2010 at 11:41 AM, Kai Tietz wrote > > just for getting you right. Does initial cross-compiler fails, or then > the build of the canadian cross based on this cross-compiler? > > Initial gcc is fine, it fails in the "Finishing GCC [ FNSHGC]" part mentioned in the gcc. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
On Mon, Sep 6, 2010 at 11:20 AM, JonY wrote: > > No, not path. By link, I meant using symlinks on Linux and junction points > in Windows. > > The compiler looks in /usr/local/mingw64/mingw instead of > /usr/local/mingw64/x86_64-w64-mingw32, so you'll need to link them. > Sorry I misunderstood but its already linked: [~]> ls -al /usr/local/mingw64/mingw lrwxr-xr-x 1 root wheel 18 Sep 6 08:19 /usr/local/mingw64/mingw -> x86_64-w64-mingw32 Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi; On Mon, Sep 6, 2010 at 4:03 AM, JonY wrote: > On 9/6/2010 05:27, İsmail Dönmez wrote: >> >> Hi; >> >> On Mon, Sep 6, 2010 at 12:12 AM, Kai Tietz >> wrote: >>> >>> Well, could you please try '../configure --host=x86_64-w64-mingw32 >>> --enable-lib32 --enable-lib64 --prefix=/usr/local/mingw64'. Does this >>> change the behavior? At least for me it worked that way. >> >> Sadly that didn't help either. I'll do more tinkering tomorrow. Thanks >> for your help, its appreciated. >> >> Regards, >> ismail > > Hi, > > Did you remember to link /usr/local/mingw64/mingw/ to > /usr/local/mingw64/x86_64-w64-mingw32? > Yes it was in my PATH. I just re-tried from scratch and same error. ld seems to be misbehaving somehow. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi; On Mon, Sep 6, 2010 at 12:12 AM, Kai Tietz wrote: > Well, could you please try '../configure --host=x86_64-w64-mingw32 > --enable-lib32 --enable-lib64 --prefix=/usr/local/mingw64'. Does this > change the behavior? At least for me it worked that way. Sadly that didn't help either. I'll do more tinkering tomorrow. Thanks for your help, its appreciated. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi; On Mon, Sep 6, 2010 at 12:08 AM, Kai Tietz wrote: > Could you please show me your configure line you used for crt. ../configure --host=x86_64-w64-mingw32 --enable-lib32 --prefix=/usr/local/mingw64 Thanks, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi; On Sun, Sep 5, 2010 at 11:56 PM, Kai Tietz wrote: > Well, have you build and installed headers and crt after initial gcc > bootstrap? Have you added new sys-root/bin folder to you path before > building crt? Yes, I did actually. The gcc fails in the second time which I do after installing crt. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi there; On Sun, Sep 5, 2010 at 11:45 PM, Kai Tietz wrote: > 2010/9/5 İsmail Dönmez : >> Hi, >> >> On Sun, Sep 5, 2010 at 11:26 PM, Kai Tietz wrote: >>> Well, as you see in your dump of ld "i386pep" which means that ld >>> supports x86_64 output. In ld (and some other tools of binutils) the >>> naming of target is different. >>> >>> So you should have a binutils version which is capable to build 32-bit >>> and 64-bit code. >> >> Ok, then it shouldn't fail right? >> >>> See >>> http://sourceforge.net/apps/trac/mingw-w64/wiki/Answer%20Multilib%20Toolchain >>> for some FAQ about this subject. >> >> Do I need --enable-multilib --enable-version-specific-runtime-libs, >> because >> http://sourceforge.net/apps/trac/mingw-w64/wiki/Cross%20Win32%20and%20Win64%20compiler >> does not mention it. Also --sysroot is mandatory for multilib? > > Well, for multilib you get two different sets of runtime-libraries > installed (by gcc and by our crt). Therefore to avoid conflicts > between those two sets we recomment to use > --enable-version-specific-runtime-libs. The --enable-multilib isn't > absolutely necessary as it is on by default for gcc (at least for > 4.5.1 and higher), but for completeness I would always specify it on > configure line. > It has some advantages to use sysroot (and this option we describe in > single targeted cross-compiler howto, too), as it leads in combination > with --prefix to a relocatable toolchain. This means, you can copy the > sysroot-folder (the past folder specified - eg > --with-sysroot=/opt/mingww64, then mingww64 is the sysroot-folder) to > any location without the need of rebuilding it. I tried --enable-multilib too; but here is the same error : /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/x86_64-w64-mingw32/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/x86_64-w64-mingw32/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/mingw/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/mingw/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/x86_64-w64-mingw32/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/x86_64-w64-mingw32/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/x86_64-w64-mingw32/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/mingw/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: skipping incompatible /usr/local/mingw64/x86_64-w64-mingw32/lib/libmingw32.a when searching for -lmingw32 /usr/local/mingw64/x86_64-w64-mingw32/bin/ld: cannot find -lmingw32 So ld does not find; /usr/local/mingw64/x86_64-w64-mingw32/lib32/libmingw32.a which is supposed to be the 32bit one. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi, On Sun, Sep 5, 2010 at 11:26 PM, Kai Tietz wrote: > Well, as you see in your dump of ld "i386pep" which means that ld > supports x86_64 output. In ld (and some other tools of binutils) the > naming of target is different. > > So you should have a binutils version which is capable to build 32-bit > and 64-bit code. Ok, then it shouldn't fail right? > See > http://sourceforge.net/apps/trac/mingw-w64/wiki/Answer%20Multilib%20Toolchain > for some FAQ about this subject. Do I need --enable-multilib --enable-version-specific-runtime-libs, because http://sourceforge.net/apps/trac/mingw-w64/wiki/Cross%20Win32%20and%20Win64%20compiler does not mention it. Also --sysroot is mandatory for multilib? Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Canadian cross still broken?
Hi there; On Sun, Sep 5, 2010 at 10:04 PM, Kai Tietz wrote: > Hmm, as I see in this report has binutils not being configure to > support pe-i386 targets (see here our Wiki page about multilib - it > needs additional arguments for doing this). > By fixing this, you should be able to build a multilib cross-compiler. ld do have i386 targets but interestingly missing x86_64 ones: [~/Sources/gcc/build-w64]> x86_64-w64-mingw32-ld -V GNU ld (GNU Binutils) 2.20.1.20100905 Supported emulations: i386pep i386pe I have configured binutils with: ../configure --target=x86_64-w64-mingw32 --enable-targets=x86_64-w64-mingw32,i686-w64-mingw32 --prefix=/usr/local/mingw64 --disable-werror Any help is appreciated. Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Canadian cross still broken?
Hi all; Today I was trying to do a canadian cross build of mingw-w64 on Snow Leopard. I am using the instructions in the wiki but the gcc failed to compiled with an error, that was already reported here [0]. I didn't try a non-multilib build (yet) but I wonder if multilib is broken or canadian cross is still broken in the trunk. Used gcc 4.5 from the stable branch and mingw-w64 from trunk. [0] http://www.mail-archive.com/mingw-w64-public@lists.sourceforge.net/msg00839.html Regards, ismail -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
