Re: Fail to compile trunk

On 14 April 2015 at 17:19, Harald Servat wrote: > Should we file a PR to request to integrate this patch? Or should I > better follow Peter's suggestion to build gcc from a separate build > directory? You should always build in a separate directory, that's what all the installation docs and the FA

Re: Fail to compile trunk

This is already filed as PR65763. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."

Re: Fail to compile trunk

That patch solved the problem Andreas, thank you very much! Should we file a PR to request to integrate this patch? Or should I better follow Peter's suggestion to build gcc from a separate build directory? Best regards. 2015-04-14 18:14 GMT+02:00 Andreas Schwab : > Please try this patch: > > di

Re: Fail to compile trunk

Ah, sorry for the misundersanding, I'll send the questions to gcc-help from now on! Still, thank you very much for the answer! 2015-04-14 18:14 GMT+02:00 Peter Bergner : > On Tue, 2015-04-14 at 17:37 +0200, Harald Servat wrote: >> I'm trying to compile the GCC's trunk but I find out the followi

Re: Fail to compile trunk

Please try this patch: diff --git a/libcc1/Makefile.am b/libcc1/Makefile.am index ecab22c..7a274b3 100644 --- a/libcc1/Makefile.am +++ b/libcc1/Makefile.am @@ -17,7 +17,7 @@ ## . ACLOCAL_AMFLAGS = -I .. -I ../config -gcc_build_dir = ../$(host_subdir)/gcc +gcc_buil

Re: Fail to compile trunk

On Tue, 2015-04-14 at 17:37 +0200, Harald Servat wrote: > I'm trying to compile the GCC's trunk but I find out the following > error while compiling it. I've configured it such as This question is not appropriate for this mailing list, as this list is only for questions about gcc development. Y