Date: Wed, 10 Apr 2013 01:00:00 GMT From: Mark Andrews <marka@isc.org> To: gecko@FreeBSD.org Subject: Re: ports/177728: firefox-20.0,1 requires a GCC 4.7 or later Message-ID: <201304100100.r3A100Fr096450@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/177728; it has been noted by GNATS. From: Mark Andrews <marka@isc.org> To: Jan Beich <jbeich@tormail.org> Cc: bug-followup@freebsd.org Subject: Re: ports/177728: firefox-20.0,1 requires a GCC 4.7 or later Date: Wed, 10 Apr 2013 10:50:13 +1000 In message <1UPiY5-000Dhi-4D@internal.tormail.org>, Jan Beich writes: > Mark Andrews <marka@isc.org> writes: > > > In message <1UPZxS-0009eJ-2K@internal.tormail.org>, Jan Beich writes: > > > >> Mark Andrews <marka@isc.org> writes: > >> > >> >>Environment: > >> > System: FreeBSD sex.dv.isc.org 8.4-PRERELEASE FreeBSD 8.4-PRERELEASE > >> > #28 r249035M: Wed Apr 3 14:24:08 EST 2013 > >> > marka@sex.dv.isc.org:/usr/obj/usr/src/sys/DEBUG i386 > >> >>Description: > >> > Firefox tries to include <new> which is not available until > >> > GCC 4.7. > >> >>How-To-Repeat: > >> > Attempt to build firefox on FreeBSD 8.4. > >> > >> It builds fine on pointyhat with default options and using poudriere > >> with GIO and LOGGING unset. Provide more details. > >> > >> http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.8.20130404090506.p > oin > >> tyhat/firefox-20.0,1.log > >> http://ompldr.org/vaTFnMg/firefox-20.0,1.log.gz > > > > See http://users.isc.org/~marka/177728 for failing build. > [...] > > checking compiler version... gcc46 (FreeBSD Ports Collection) 4.6.4 2012083 > 1 (prerelease) > > That corresponds to lang/gcc46 snapshot from September. While firefox > should build fine with any (maintained) gcc version selectively > upgrading ports is not really supported. > > > /usr/ports/www/firefox/work/mozilla-release/memory/mozalloc/mozalloc.cpp:9: > 54: fatal error: new: No such file or directory > > compilation terminated. > > gmake[3]: *** [mozalloc.o] Error 1 > > base-gcc and clang (without -stdlib=libc++) use /usr/include/c++/4.2/new. > gccXY from ports use /usr/local/lib/gccXY/include/c++/new which can > be confirmed by looking at pointyhat packages e.g., > > # same version as you're using > $ tar tf gcc-4.6.4.20120831.tbz | fgrep c++/new > lib/gcc46/include/c++/new > > # latest snapshot > $ tar tf gcc-4.6.4.20130215.tbz | fgrep c++/new > lib/gcc46/include/c++/new > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/lang/gcc-4.6.4 > .20120831.tbz > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.4-release/lang/gcc-4. > 6.4.20130215.tbz Somehow gcc46 got disconnected from the ports managements databases. Re-installing gcc46 fixed this issue. Whenever I upgrade one thing I upgrade everything else than needs upgrading and rebuild everything that depends on the ports being upgraded. Been doing that for the last decade or so. It avoids lots of problems but does mean you are living on the bleeding edge at times. e.g. portupgrade -an > junk extract list of ports portupgrade -cF <list of ports> portupgrade -rf <list of ports> OS upgrades are followed by 'portupgrade -af' -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304100100.r3A100Fr096450>