Re: [Mingw-w64-public] Strange linker error with gcc-5.1 32-bit involving 'virtual thunk'

On 7/30/2015 10:48 AM, Óscar Fuentes wrote: > Edward Diener > writes: > >>> Another thing is to get some hints from a .map-file. >>> Add "-Wl,--print-map,--sort-common,--cref > file.map" at the >>> of the link-cmd. >> >> I could not find any documentation regarding the linker options you >> specif

Re: [Mingw-w64-public] GCC 5.2 with JIT language frontend

Hi, I'm getting this error from make, and have no idea how to fix it? I got this previously as well, when I tried to build GCC without using your build scripts. Searching around it says that maybe it is related to not configuring the right directory, but I'm positive I've done it correctly and al

Re: [Mingw-w64-public] [PATCH] 2 Small Patches for ARM and Clang building

> > For consistency with the existing multilib dirs, IMHO LIBARM32SUFFIXDIR > should be lib only if hostcpu is arm*, it should be libarm32 otherwise. Yes this makes sense so I changed it to that with this updated patch. Also when the host is arm x86 libs should also not be lib and should be libx8

Re: [Mingw-w64-public] Strange linker error with gcc-5.1 32-bit involving 'virtual thunk'

On 7/30/2015 10:48 AM, Óscar Fuentes wrote: > Edward Diener > writes: > >>> Another thing is to get some hints from a .map-file. >>> Add "-Wl,--print-map,--sort-common,--cref > file.map" at the >>> of the link-cmd. >> >> I could not find any documentation regarding the linker options you >> specif

Re: [Mingw-w64-public] Strange linker error with gcc-5.1 32-bit involving 'virtual thunk'

Edward Diener writes: >> Another thing is to get some hints from a .map-file. >> Add "-Wl,--print-map,--sort-common,--cref > file.map" at the >> of the link-cmd. > > I could not find any documentation regarding the linker options you > specify in the gcc documentation. Are they mingw-64 specific

Re: [Mingw-w64-public] Strange linker error with gcc-5.1 32-bit involving 'virtual thunk'

On 7/30/2015 2:48 AM, Gisle Vanem wrote: > Edward Diener wrote: > >> If I remove the declaration and definition of ex_xml_exception::what(), >> since it is not needed, when linking I get: >> >> throw_exception_ex.o:throw_exception_ex.cpp:(.rdata$_ZTV16ex_xml_exception[__ZTV16ex_xml_exception]+0x20)

Re: [Mingw-w64-public] GCC 5.2 with JIT language frontend

Awesome, going to try that, btw I think it also needs --enable-host-shared, but I'll try with your suggestion only and see where I get. On Thu, Jul 30, 2015 at 3:28 AM, niXman wrote: > Hayden Livingston 2015-07-30 13:19: >> Hi, >> >> I couldn't see an option to enable jit, it's not on the repo or

Re: [Mingw-w64-public] GCC 5.2 with JIT language frontend

Hayden Livingston 2015-07-30 13:19: > Hi, > > I couldn't see an option to enable jit, it's not on the repo or are > you saying if I pass it your script will still work? Yes, you should to add the 'jit' here(for gcc-5.2): https://github.com/niXman/mingw-builds/blob/develop/scripts/gcc-5.2.0.sh#L82

Re: [Mingw-w64-public] GCC 5.2 with JIT language frontend

Hi, I couldn't see an option to enable jit, it's not on the repo or are you saying if I pass it your script will still work? On Thu, Jul 30, 2015 at 3:07 AM, niXman wrote: > Hayden Livingston 2015-07-30 05:56: > > Hi, > >> Are you saying that this is a way to get a windows 64-bit build? > Yes,

Re: [Mingw-w64-public] GCC 5.2 with JIT language frontend

Hayden Livingston 2015-07-30 05:56: Hi, > Are you saying that this is a way to get a windows 64-bit build? Yes, 32 and 64 bit. > Or are you saying you've got JIT frontend working? I was able to build the GCC with the '--enable-languages=jit' option.

Re: [Mingw-w64-public] Strange linker error with gcc-5.1 32-bit involving 'virtual thunk'

On 7/30/2015 2:48 AM, Gisle Vanem wrote: > Edward Diener wrote: > >> If I remove the declaration and definition of ex_xml_exception::what(), >> since it is not needed, when linking I get: >> >> throw_exception_ex.o:throw_exception_ex.cpp:(.rdata$_ZTV16ex_xml_exception[__ZTV16ex_xml_exception]+0x20)