Re: [Mingw-w64-public] Building gcc-10 against mingw-w64-8.0.0: error: unknown conversion type character 'l' in format

On 19.01.21 16:06, Biswapriyo Nath wrote: Would you like to test if the following patch works? * File name: 0020-libgomp-Don-t-hard-code-MS-printf-attributes.patch * Link: https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-gcc/0020-libgomp-Don-t-hard-code-MS-printf-attributes.patch

Re: [Mingw-w64-public] Building gcc-10 against mingw-w64-8.0.0: error: unknown conversion type character 'l' in format

在 2021-01-19 22:16, Sandro Mani 写道: Hi Tryting to build gcc-10 against mingw-w64-8.0.0, when compiling libgomp it errors out with [1] (...) -Werror is passed when compiling libgomp (as it generally is in gcc throughout), so this causes the build to fail. I'm unsure which is the correct

Re: [Mingw-w64-public] Building gcc-10 against mingw-w64-8.0.0: error: unknown conversion type character 'l' in format

Would you like to test if the following patch works? * File name: 0020-libgomp-Don-t-hard-code-MS-printf-attributes.patch * Link: https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-gcc/0020-libgomp-Don-t-hard-code-MS-printf-attributes.patch ArchLinux also uses that patch file. Link

Re: [Mingw-w64-public] Building GCC linked against libucrt fails

On Mon, 1 Apr 2019, Kacvinsky, Tom wrote: Hi, I think the important distinction here is to make between building the compiler itself (which is a binary which you build using your existing toolchain, using the CRT that is default/usable there), and building the runtimes (libgcc, libstdc++,

Re: [Mingw-w64-public] Building GCC linked against libucrt fails

> -Original Message- > From: Kacvinsky, Tom > Sent: Monday, April 1, 2019 10:54 AM > To: mingw-w64-public@lists.sourceforge.net > Subject: [Mingw-w64-public] Building GCC linked against libucrt fails > > > In my own setup for bootstrapping a mingw cross compiler on linux, I > > do the

Re: [Mingw-w64-public] Building GCC on mingw-w64

On Sat, Oct 3, 2015 at 6:46 PM, FX wrote: >> MSYS2 distributes the gcc fortran package based on mingw-w64 (see the >> output of pacman -Ss fortran). You can inspect how it is built by >> consulting its PKGBUILD recipe. It is here, along with the necessary >> patches:

Re: [Mingw-w64-public] Building GCC on mingw-w64

FX 2015-10-04 00:57: > Hi everyone, Hi, > Am I missing something? Please read: https://github.com/niXman/mingw-builds -- Regards, niXman ___ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:

Re: [Mingw-w64-public] Building GCC on mingw-w64

> MSYS2 distributes the gcc fortran package based on mingw-w64 (see the > output of pacman -Ss fortran). You can inspect how it is built by > consulting its PKGBUILD recipe. It is here, along with the necessary > patches: https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-gcc Thanks

Re: [Mingw-w64-public] Building GCC on mingw-w64

On Sat, Oct 3, 2015 at 11:46 PM, FX wrote: >> MSYS2 distributes the gcc fortran package based on mingw-w64 (see the >> output of pacman -Ss fortran). You can inspect how it is built by >> consulting its PKGBUILD recipe. It is here, along with the necessary >> patches:

Re: [Mingw-w64-public] Building GCC with --enable-libstdcxx-debug

Hello. I've finished a build with --enable-libstdcxx-debug, and this time I've checked both the build tree and the install tree. This is what I found on the build tree. $ find . -name libstdc*.dll -exec ls -l {} \; 15,102,643 Sep 17 08:49

Re: [Mingw-w64-public] Building GCC with --enable-libstdcxx-debug

Hello. First of all, sorry for the late reply. I ran into a bit of a problem last week, and learned the hard way that having backups is not enough, you need to test them every now and then. Anyway, I've just checked the build tree for the last build I performed (with --enable-libstdcxx-debug),

Re: [Mingw-w64-public] Building GCC with --enable-libstdcxx-debug

Le 07/09/2015 23:23, Paulo Caetano a écrit : > Hello. > > I've been experimenting building GCC with --enable-libstdcxx-debug, > both on Linux and MSYS2, and there's one thing I'm not sure of and I > wonder if you could help me understand it. > > GCC docs say that configuring GCC with

Re: [Mingw-w64-public] Building GCC 5.1 with --enable-host-shared --enable-languages=jit --disable-bootstrap

Hi, I have not tried to build jit option for windows right now. Nevertheless you shouldn't remove the c-languages from bootstrap as modern gcc requires at least c++ for doing a full bootstrap. Additionally I would recomment to specify explicit --disable-multilib option, as this could otherwise

Re: [Mingw-w64-public] Building GCC with crazy host-build-target

On 1/10/2014 17:21, Ruben Van Boxem wrote: Hi, I'm attempting to build GCC with the following triplets: checking build system type... x86_64-unknown-linux-gnu checking host system type... i686-unknown-linux-gnu checking target system type... i686-w64-mingw32 Above is OK. I configured

Re: [Mingw-w64-public] Building GCC with crazy host-build-target

2014/1/10 JonY jo...@users.sourceforge.net On 1/10/2014 17:21, Ruben Van Boxem wrote: Hi, I'm attempting to build GCC with the following triplets: checking build system type... x86_64-unknown-linux-gnu checking host system type... i686-unknown-linux-gnu checking target system type...

Re: [Mingw-w64-public] Building GCC with crazy host-build-target

On 1/10/2014 18:46, Ruben Van Boxem wrote: 2014/1/10 JonY jo...@users.sourceforge.net On 1/10/2014 17:21, Ruben Van Boxem wrote: Hi, I'm attempting to build GCC with the following triplets: checking build system type... x86_64-unknown-linux-gnu checking host system type...

Re: [Mingw-w64-public] Building GCC with my scripts under MSYS

于 2011/7/10 20:52, Earnie 写道: I didn't think it was possible to build in the source directory for the GCC package, when did it change? It is also advised to build in a separate build directory instead of the source directory so if this is reproducibly true then a bug report needs to be open

Re: [Mingw-w64-public] Building GCC with my scripts under MSYS

2011/7/10 PcX xunxun1...@gmail.com 于 2011/7/10 20:52, Earnie 写道: I didn't think it was possible to build in the source directory for the GCC package, when did it change? It is also advised to build in a separate build directory instead of the source directory so if this is reproducibly

Re: [Mingw-w64-public] Building GCC with my scripts under MSYS

Ruben Van Boxem wrote: 2011/7/10 Earnie ear...@users.sourceforge.net PcX wrote: 于 2011/7/10 1:55, Ruben Van Boxem 写道: Which is very odd, because the file that does not exist, exists. Sometimes, on msys, if your source directory and build directory is different, the some file does not exit

Re: [Mingw-w64-public] Building GCC with my scripts under MSYS

JonY wrote: On 7/10/2011 01:55, Ruben Van Boxem wrote: In an attempt to help all these people trying to build GCC toolchains (for reasons still very mysterious to me), I attempted modifying them to build a 32-bit to 64-bit cross-compiler and tried running it on MSYS with my 32-bit toolchain.

Re: [Mingw-w64-public] Building GCC with my scripts under MSYS

于 2011/7/10 1:55, Ruben Van Boxem 写道: Which is very odd, because the file that does not exist, exists. Sometimes, on msys, if your source directory and build directory is different, the some file does not exit error will appear. I don't know this reason. So if I build gcc on msys, I will build

Re: [Mingw-w64-public] building gcc

On Sun, Jul 3, 2011 at 6:06 AM, JonY jo...@users.sourceforge.net wrote: On 7/3/2011 12:10, Bj Raz wrote: I've been working on cross compiler for building w64 binaries. I just wanted to see if I could do it :P I'm following the directions from Linux From Scratch (modifying them as needed).

Re: [Mingw-w64-public] building gcc

2011/7/3 Bj Raz whitequill...@gmail.com: On Sun, Jul 3, 2011 at 6:06 AM, JonY jo...@users.sourceforge.net wrote: On 7/3/2011 12:10, Bj Raz wrote: I've been working on cross compiler for building w64 binaries. I just wanted to see if I could do it :P I'm following the directions from Linux

Re: [Mingw-w64-public] building gcc

On Sun, Jul 3, 2011 at 4:22 PM, Ruben Van Boxem vanboxem.ru...@gmail.comwrote: 2011/7/3 Bj Raz whitequill...@gmail.com: On Sun, Jul 3, 2011 at 6:06 AM, JonY jo...@users.sourceforge.net wrote: On 7/3/2011 12:10, Bj Raz wrote: I've been working on cross compiler for building w64

Re: [Mingw-w64-public] building gcc

On Sun, Jul 3, 2011 at 5:45 PM, Ruben Van Boxem vanboxem.ru...@gmail.comwrote: 2011/7/3 Bj Raz whitequill...@gmail.com: On Sun, Jul 3, 2011 at 4:22 PM, Ruben Van Boxem vanboxem.ru...@gmail.com wrote: 2011/7/3 Bj Raz whitequill...@gmail.com: On Sun, Jul 3, 2011 at 6:06 AM, JonY

Re: [Mingw-w64-public] building gcc

On Sun, Jul 3, 2011 at 6:06 AM, JonY jo...@users.sourceforge.net wrote: On 7/3/2011 12:10, Bj Raz wrote: I've been working on cross compiler for building w64 binaries. I just wanted to see if I could do it :P I'm following the directions from Linux From Scratch (modifying them as needed).

Re: [Mingw-w64-public] building gcc

On 7/4/2011 08:49, Bj Raz wrote: /tools/x86_64-w64-mingw32/bin/ld cannot find dllcrt2.o: No such file or directory /tools/x86_64-w64-mingw32/bin/ld cannot find crtbegin.o: No such file or directory /tools/x86_64-w64-mingw32/bin/ld cannot find crtend.o: No such file or directory collect2:

Re: [Mingw-w64-public] building GCC myself from MSYS

I am now trying to rebuild the same GCC version (4.6-20100904) with my fresh compiler, but getting stuck at either the stage2-stage3 comparison or if I don't bootstrap, this: xgcc.exe: error: C:UsersRubenAppDataLocalTempcccemHMa.lto.o: No such file or directory Some MSYS path problem: same

Re: [Mingw-w64-public] building GCC myself from MSYS

2010/9/14 John E. / TDM tdra...@tdragon.net This is correct. TDM64 GCC 4.5.1 is patched to remove a leading underscore from the names of the _alloca and __chkstk symbols, in order for them to be exported from both the 64-bit and 32-bit versions of libgcc with the same export rule (there is

Re: [Mingw-w64-public] building GCC myself from MSYS

On 9/13/2010 11:34 AM, Ruben Van Boxem wrote: M:/Development/msys/gcc-libs/lib/libmpfr.a(div.o):div.c:(.text+0xe75): more undefined references to `__chkstk' follow collect2: ld returned 1 exit status How do i fix this? I'm doing a make profiledbootstrap in gcc, it has used mpfr

Re: [Mingw-w64-public] building GCC myself from MSYS

2010/9/11 John E. / TDM tdra...@tdragon.net On 9/11/2010 12:19 PM, Kai Tietz wrote: , but nevertheless libelf (which isn't an elf OS specific library btw) is required so that LTO works as it should. Trust me, it isn't! I have never installed libelf on my build machine, but LTO is

Re: [Mingw-w64-public] building GCC myself from MSYS

2010/9/11 Ruben Van Boxem vanboxem.ru...@gmail.com Hi, Recently I started messing around with GCC and attempted to build it many times. I first had lots of trouble with the 4.5 snapshots, but have now moved to 4.6 and all seems well. I put all the instructions in a single file (not quite a

Re: [Mingw-w64-public] building GCC myself from MSYS

2010/9/11 Ruben Van Boxem vanboxem.ru...@gmail.com: 2010/9/11 Ruben Van Boxem vanboxem.ru...@gmail.com Hi, Recently I started messing around with GCC and attempted to build it many times. I first had lots of trouble with the 4.5 snapshots, but have now moved to 4.6 and all seems well. I put

Re: [Mingw-w64-public] building GCC myself from MSYS

Hmm, I don't get this failure on cygwin as host. Have you installed lto on msys for native compiler before proper? Kai I'm using TDM64 GCC 4.5.1 with lto enabled, and it works for eg building Qt without error. I have also built and installed libelf for TDM64 GCC (it's installed in the MSYS

Re: [Mingw-w64-public] building GCC myself from MSYS

2010/9/11 Ruben Van Boxem vanboxem.ru...@gmail.com: Hmm, I don't get this failure on cygwin as host. Have you installed lto on msys for native compiler before proper? Kai I'm using TDM64 GCC 4.5.1 with lto enabled, and it works for eg building Qt without error. I have also built and

Re: [Mingw-w64-public] building GCC myself from MSYS

2010/9/11 John E. / TDM tdra...@tdragon.net:  On 9/11/2010 11:50 AM, Kai Tietz wrote: Well, lto normally needs not to be explicit enabled. You just need to have the libelf library installed on you host environment. Actually, libelf is not required to enable LTO for PE-COFF targets (i.e.

Re: [Mingw-w64-public] building GCC myself from MSYS

On 9/11/2010 12:19 PM, Kai Tietz wrote: , but nevertheless libelf (which isn't an elf OS specific library btw) is required so that LTO works as it should. Trust me, it isn't! I have never installed libelf on my build machine, but LTO is enabled and I see dramatic improvements when I use it.