Re: [Mingw-w64-public] [PATCH] ucrtbase: Make sure that compat symbols aren't autoexported

2017-11-23 Thread Martin Storsjö
On Thu, 23 Nov 2017, Sven Kretzschmar wrote: Currently I get a new strange error while compiling the Julia sources with the new toolchain: /CROSS64/lib/gcc/x86_64-w64-mingw32/6.4.0/../../../../x86_64-w64-mingw32/lib /../lib/libmsvcrt.a(lib64_libucrtbase_a-ucrt_sprintf.o):/home/sven/buildtmp/ bu

Re: [Mingw-w64-public] [PATCH] ucrtbase: Make sure that compat symbols aren't autoexported

2017-11-23 Thread Sven Kretzschmar
Hi Martin, Thanks a lot for your support in getting ucrtbase to work. I will try to add the 2 missing references in the way you hinted at in your post. Currently I get a new strange error while compiling the Julia sources with the new toolchain: /CROSS64/lib/gcc/x86_64-w64-mingw32/6.4.0/../../

Re: [Mingw-w64-public] [PATCH] ucrtbase: Make sure that compat symbols aren't autoexported

2017-11-23 Thread Martin Storsjö
On Thu, 23 Nov 2017, Martin Storsjö wrote: On Thu, 23 Nov 2017, Kai Tietz via Mingw-w64-public wrote: Martin, patch looks ok. Be careful about the static symbol in custom section that it is actually present in a finally linked version. Sometimes gcc thinks ... that it can optimize away such

Re: [Mingw-w64-public] [PATCH] ucrtbase: Make sure that compat symbols aren't autoexported

2017-11-23 Thread Martin Storsjö
On Thu, 23 Nov 2017, Kai Tietz via Mingw-w64-public wrote: Martin, patch looks ok. Be careful about the static symbol in custom section that it is actually present in a finally linked version. Sometimes gcc thinks ... that it can optimize away such static symbols. I had to introduce for that

Re: [Mingw-w64-public] [PATCH] ucrtbase: Make sure that compat symbols aren't autoexported

2017-11-23 Thread Kai Tietz via Mingw-w64-public
Martin, patch looks ok. Be careful about the static symbol in custom section that it is actually present in a finally linked version. Sometimes gcc thinks ... that it can optimize away such static symbols. I had to introduce for that dummy references to such symbols in the past. See crt/* folde

Re: [Mingw-w64-public] ucrtbase_compat.c:225:34: error: 'UCRTBASE_PRINTF_LEGACY_WIDE_SPECIFIERS' undeclared

2017-11-23 Thread Rainer Emrich
Hi Martin, Am 22.11.2017 um 20:03 schrieb Martin Storsjö: > On Wed, 22 Nov 2017, Rainer Emrich wrote: >> building master is broken atm. >> >> gcc-7.2.0 >> binutils 2.29 >> >> Configure: >> /opt/devel/gnu/src/gcc-mingw-w64/mingw-w64-runtime.git/configure >> --prefix=/home/rainer/software/install/x8

[Mingw-w64-public] [PATCH] ucrtbase: Make sure that compat symbols aren't autoexported

2017-11-23 Thread Martin Storsjö
When linking a DLL without using dllexport attributes or a def file, all global symbols are exported, unless they are excluded for one reason or another. GNU ld has got a list of libraries and object files to exclude, so any symbols from e.g. libmingwex or libmingw32 or dllcrt2.o won't get exported

Re: [Mingw-w64-public] Challenges with using ucrtbase option for cross compiling...

2017-11-23 Thread Martin Storsjö
On Thu, 23 Nov 2017, Sven Kretzschmar wrote: ERROR #1: -- libtool: link: rm -fr .libs/libgfortran.dll.a .libs/libgfortran.la.lnkscript libtool: link: /home/sven/buildtmp/build/gcc/./gcc/xgcc -B/home/sven/buildtmp/build/gcc/./gcc/ -L/CROSS64/x86_64-w64-mingw32/lib -L/CROSS64/mingw/li