On 9/19/05, bob self <bobself_at_charter.net> wrote: > > > Why might this be happening???? I updated all the ports from source > yesterday. That worked fine. Now I'm trying to go to beta 5 but after a > long time > compiling I get this message. I'm now running 6.0 beta 4 and as far as I > know there are no problems except this. > > Bob > > > > > c++ -O2 -fno-strict-aliasing -pipe -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H > -I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc++/../ > ../../contrib/libstdc++/libsupc++ > -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc > -I/usr/src/gnu/lib/libstdc++/../../../contri > b/libstdc++/include -frandom-seed=RepeatabilityConsideredGood > -fno-implicit-templates -ffunction-sections -fdata-sections -Wno- > deprecated -c > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/io-inst.cc > In file included from /usr/obj/usr/src/tmp/usr/include/c++/3.4/string:57, > from > > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/bits/locale_classes.h:47, > from > > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/bits/ios_base.h:47, > from /usr/obj/usr/src/tmp/usr/include/c++/3.4/ios:49, > from > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/io-inst.cc:35: > > /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include/bits/basic_string.tcc:236: > internal compiler error: Segmentation f > ault: 11 > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://gcc.gnu.org/bugs.html> for instructions. > *** Error code 1 > > Stop in /usr/src/gnu/lib/libstdc++. > *** Error code 1 > > Stop in /usr/src/gnu/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" I have heard many times on this list that such "internal compiler errors" are usually caused by bad hardware -- have you checked your memory? Ben KadukReceived on Mon Sep 19 2005 - 17:30:14 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:43 UTC