Date: Fri, 12 Sep 2014 17:06:53 +0400 From: Andrey Chernov <ache@freebsd.org> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: ports@FreeBSD.org Subject: Re: Can't build lang/gcc port on i386: segmentation fault Message-ID: <5412EFED.9000100@freebsd.org> In-Reply-To: <alpine.LSU.2.11.1409121436401.2669@tuna.site> References: <5412D743.70005@freebsd.org> <alpine.LSU.2.11.1409121400460.2669@tuna.site> <5412E4A1.7040101@freebsd.org> <5412E64E.7050701@freebsd.org> <alpine.LSU.2.11.1409121436401.2669@tuna.site>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12.09.2014 16:42, Gerald Pfeifer wrote: > On Fri, 12 Sep 2014, Andrey Chernov wrote: >>> As I just found, it builds with BOOTSTRAP nice, so apparently clang >>> makes some damage. You can see CFLAGS in the log. Swap is 4GB I think it >>> is large enough. Nothing special otherwise. >> BTW, previous 4.7* as lang/gcc build fine even without BOOTSTRAP. > > I am curious, what happens when you try lang/gcc48? > > My expectation would be both lang/gcc and lang/gcc48 to behave > the same, since it's a very similar codebase, gcc48 just a bit > newer on the same branch. > > We could make BOOTSTRAP the default for lang/gcc, though not > doing that and thus building a lot faster has been one of the > features of lang/gcc. -- Since it does not reproduce for me, > do others see the same failure? Segfault is exact the same but comes from strange place - in the middle of configure check. I will try with MAKE_JOBS_UNSAFE=yes -- http://ache.vniz.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5412EFED.9000100>