Date: Fri, 17 Feb 2017 00:14:02 -0700 From: Gordon Zaft <gordonzaft@gmail.com> To: Joe Nosay <superbisquit@gmail.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: compiler issues Message-ID: <CAGuhNT2Z1fxoo_izH18A6MatUKwk-f8shW5Kk=Jadp_m%2Bre_uQ@mail.gmail.com> In-Reply-To: <CA%2BWntOukeSCwUjHyL5DaVn3-HHMwou5xG_LAAwh9sU9vqHAbAA@mail.gmail.com> References: <CAGuhNT0EikeN0jrn0Fa7bCtc=JoN6wdd4DpF-jnKe9_ub-%2Btrg@mail.gmail.com> <CAGuhNT1uzkZaDLzbnwxyWLTU65eM9X5srmgGw0KoFj0Pc55=nQ@mail.gmail.com> <CA%2BWntOt11fP0ivpLwCoD896kULxRAJPwaE5eTL3OXtYAFig-Kg@mail.gmail.com> <CAGuhNT18TCAZwFM2OXn2Om%2B9vdbZ=0UHvPkdXPZF68GKuZGNRw@mail.gmail.com> <CA%2BWntOukeSCwUjHyL5DaVn3-HHMwou5xG_LAAwh9sU9vqHAbAA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I wanted to follow up on this post. I've discovered that if I build manually (i.e. "make install") instead of using portmaster, I can successfully build large packages. When I get the segmentation fault I simply restart (make install again) and as one would hope it picks up where it left off. I was able to build and install gcc 4.9.4 this way (it took a long time!). Note that portmaster won't work because it does a make clean when it fails, so you are starting from scratch every time. It's a feature, but one that's not helpful in this particular case. G On Wed, Nov 30, 2016 at 11:04 AM, Joe Nosay <superbisquit@gmail.com> wrote: > Give it a try and report your progress to the community. > > > On Wed, Nov 30, 2016 at 12:54 PM, Gordon Zaft <gordonzaft@gmail.com> wrote: >> >> Hmm. So you are saying you think this stuff would build with clang >> and doesn't with gcc? I thought others were able to build this >> stuff... >> >> G >> >> On Wed, Nov 30, 2016 at 9:59 AM, Joe Nosay <superbisquit@gmail.com> wrote: >> > This may bounce. There are not enough developers available to port clang >> > and >> > llvm to SPARC64 at the moment. >> > >> > On Tue, Nov 29, 2016 at 5:04 PM, Gordon Zaft <gordonzaft@gmail.com> >> > wrote: >> >> >> >> I am still experiencing this building a variety of ports, most >> >> recently binutils. >> >> >> >> internal compiler error: Segmentation fault >> >> >> >> I'm wondering if there is something deeper going on? Still don't have >> >> a way out of this at this point. >> >> >> >> G >> >> >> >> On Mon, Oct 31, 2016 at 2:17 PM, Gordon Zaft <gordonzaft@gmail.com> >> >> wrote: >> >> > Sun U5 running 11.0, 512MB memory >> >> > >> >> > I'm trying to do some updates and I keep getting segmentation faults >> >> > while >> >> > compiling. I got this for llvm37, spidermonkey170 and ... something >> >> > else. >> >> > >> >> > I looked at my install and realized the gcc I installed with 10.x was >> >> > 4.2.1 >> >> > which is pretty old, so I decided to update to 4.91 in hopes that >> >> > would >> >> > solve some of these issues. >> >> > >> >> > Alas, I get: >> >> > >> >> > In file included from >> >> > /usr/ports/lang/gcc49/work/gcc-4.9.4/gcc/c-family/c-common.c:11936: >> >> > >> >> > ./gt-c-family-c-common.h:254: internal compiler error: Segmentation >> >> > fault >> >> > >> >> > Please submit a full bug report, with preprocessed source if >> >> > appropriate. >> >> > >> >> > I'm going to try updating to something not so recent but i'm >> >> > wondering >> >> > if >> >> > others have seen this issue. >> >> > >> >> > -- >> >> > Gordon Zaft >> >> > Province 35 Governor >> >> > Phi Mu Alpha Sinfonia Fraternity >> >> > gordonzaft@gmail.com >> >> >> >> >> >> >> >> -- >> >> Gordon Zaft >> >> Province 35 Governor >> >> Phi Mu Alpha Sinfonia Fraternity >> >> gordonzaft@gmail.com >> >> _______________________________________________ >> >> freebsd-sparc64@freebsd.org mailing list >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 >> >> To unsubscribe, send any mail to >> >> "freebsd-sparc64-unsubscribe@freebsd.org" >> > >> > >> >> >> >> -- >> Gordon Zaft >> Province 35 Governor >> Phi Mu Alpha Sinfonia Fraternity >> gordonzaft@gmail.com > > -- Gordon Zaft Province 35 Governor Phi Mu Alpha Sinfonia Fraternity gordonzaft@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGuhNT2Z1fxoo_izH18A6MatUKwk-f8shW5Kk=Jadp_m%2Bre_uQ>