Re: lang/gcc on freebsd 10
On Mon, 19 Dec 2011, Andriy Gapon wrote: > The patch worked for me too, thank you. Thanks, Andriy. I'll commit the patch momentarily, with two updates: removing patches for ChangeLogs, and fixing an issue with a library getting named .0.0.so (by pulling in another upstream patch). > The only small trouble with it was that the resulting > files/patch-freebsd10 had the dos line endings. Hmm, I think that must have happened when I mailed it (though no Windows machine was involved)? The patch as I applied it should not have those. Gerald ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc on freebsd 10
on 19/12/2011 08:06 Gerald Pfeifer said the following: > On Thu, 15 Dec 2011, Gerald Pfeifer wrote: >>> lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22 >>> installed during its configure step with the errors like the following in >>> config.log: >> >> Yes, I am aware of it. lang/gcc is the slowly moving, conservative >> option, lang/gcc46 being the fast, aggressive one. In consequence, >> lang/gcc46 has already been fixed with regard to FreeBSD 10, whereas >> this likely will take another month or so for lang/gcc when the next >> upstream release hapens. >> >> (Had I better network connectivity right now, I might try the backport, > > I managed to get a somewhat decent connection now (and until Thursday). > > Want to give the attached patch against lang/gcc a try? It passes my > tests, but I'd prefer to get confirmation from someone directly affected > before committing it. The patch worked for me too, thank you. The only small trouble with it was that the resulting files/patch-freebsd10 had the dos line endings. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc on freebsd 10
On Thu, 15 Dec 2011, Gerald Pfeifer wrote: >> lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22 >> installed during its configure step with the errors like the following in >> config.log: > > Yes, I am aware of it. lang/gcc is the slowly moving, conservative > option, lang/gcc46 being the fast, aggressive one. In consequence, > lang/gcc46 has already been fixed with regard to FreeBSD 10, whereas > this likely will take another month or so for lang/gcc when the next > upstream release hapens. > > (Had I better network connectivity right now, I might try the backport, I managed to get a somewhat decent connection now (and until Thursday). Want to give the attached patch against lang/gcc a try? It passes my tests, but I'd prefer to get confirmation from someone directly affected before committing it. GeraldIndex: files/patch-freebsd10 === RCS file: files/patch-freebsd10 diff -N files/patch-freebsd10 0a1,873 > Upstream SVN commit 181536. > > Index: libtool.m4 > === > --- libtool.m4(revision 181535) > +++ libtool.m4(revision 181536) > @@ -2273,7 +2273,7 @@ > objformat=`/usr/bin/objformat` >else > case $host_os in > -freebsd[[123]]*) objformat=aout ;; > +freebsd[[23]].*) objformat=aout ;; > *) objformat=elf ;; > esac >fi > @@ -2291,7 +2291,7 @@ >esac >shlibpath_var=LD_LIBRARY_PATH >case $host_os in > - freebsd2*) > + freebsd2.*) > shlibpath_overrides_runpath=yes > ;; >freebsd3.[[01]]* | freebsdelf3.[[01]]*) > @@ -4804,7 +4804,7 @@ >;; > > # Unfortunately, older versions of FreeBSD 2 do not have this feature. > -freebsd2*) > +freebsd2.*) >_LT_TAGVAR(archive_cmds, $1)='$LD -Bshareable -o $lib $libobjs > $deplibs $linker_flags' >_LT_TAGVAR(hardcode_direct, $1)=yes >_LT_TAGVAR(hardcode_minus_L, $1)=yes > @@ -5751,7 +5751,7 @@ > esac > ;; > > - freebsd[[12]]*) > + freebsd2.*) > # C++ shared libraries reported to be fairly broken before > # switch to ELF > _LT_TAGVAR(ld_shlibs, $1)=no > Index: libgomp/configure > === > --- libgomp/configure (revision 181535) > +++ libgomp/configure (revision 181536) > @@ -9317,7 +9317,7 @@ >;; > > # Unfortunately, older versions of FreeBSD 2 do not have this feature. > -freebsd2*) > +freebsd2.*) >archive_cmds='$LD -Bshareable -o $lib $libobjs $deplibs $linker_flags' >hardcode_direct=yes >hardcode_minus_L=yes > @@ -10230,7 +10230,7 @@ > objformat=`/usr/bin/objformat` >else > case $host_os in > -freebsd[123]*) objformat=aout ;; > +freebsd[23].*) objformat=aout ;; > *) objformat=elf ;; > esac >fi > @@ -10248,7 +10248,7 @@ >esac >shlibpath_var=LD_LIBRARY_PATH >case $host_os in > - freebsd2*) > + freebsd2.*) > shlibpath_overrides_runpath=yes > ;; >freebsd3.[01]* | freebsdelf3.[01]*) > @@ -13164,7 +13164,7 @@ >;; > > # Unfortunately, older versions of FreeBSD 2 do not have this feature. > -freebsd2*) > +freebsd2.*) >archive_cmds_FC='$LD -Bshareable -o $lib $libobjs $deplibs > $linker_flags' >hardcode_direct_FC=yes >hardcode_minus_L_FC=yes > @@ -13869,7 +13869,7 @@ > objformat=`/usr/bin/objformat` >else > case $host_os in > -freebsd[123]*) objformat=aout ;; > +freebsd[23].*) objformat=aout ;; > *) objformat=elf ;; > esac >fi > @@ -13887,7 +13887,7 @@ >esac >shlibpath_var=LD_LIBRARY_PATH >case $host_os in > - freebsd2*) > + freebsd2.*) > shlibpath_overrides_runpath=yes > ;; >freebsd3.[01]* | freebsdelf3.[01]*) > Index: libgomp/ChangeLog > === > --- libgomp/ChangeLog (revision 181535) > +++ libgomp/ChangeLog (revision 181536) > @@ -1,3 +1,7 @@ > +2011-11-20 Andreas Tobler > + > + * configure: Regenerate. > + > 2011-10-26 Release Manager > > * GCC 4.6.2 released. > Index: libquadmath/configure > === > --- libquadmath/configure (revision 181535) > +++ libquadmath/configure (revision 181536) > @@ -8727,7 +8727,7 @@ >;; > > # Unfortunately, older versions of FreeBSD 2 do not have this feature. > -freebsd2*) > +freebsd2.*) >archive_cmds='$LD -Bshareable -o $lib $libobjs $deplibs $linker_flags' >hardcode_direct=yes >hardcode_minus_L=yes > @@ -9643,7 +9643,7 @@ > objformat=`/usr/bin/objformat` >else > case $host_os in > -freebsd[123]*) objformat=aout ;; > +freebsd[23].*) objformat=aout ;; > *) objformat=elf ;; > esac >fi > @@ -9661,7 +9661,7 @@ >e
Re: lang/gcc on freebsd 10
on 15/12/2011 16:42 Gerald Pfeifer said the following: > On Thu, 15 Dec 2011, Andriy Gapon wrote: >> lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22 >> installed during its configure step with the errors like the following in >> config.log: > > Yes, I am aware of it. lang/gcc is the slowly moving, conservative > option, lang/gcc46 being the fast, aggressive one. In consequence, > lang/gcc46 has already been fixed with regard to FreeBSD 10, whereas > this likely will take another month or so for lang/gcc when the next > upstream release hapens. > > (Had I better network connectivity right now, I might try the backport, > but really the use case for lang/gcc at this point is not users of > FreeBSD 10. That's going to change with the changes to Mk/bsd.gcc.mk > that we discussed on this list the last couple of days, and that will > not happen before it builds on FreeBSD 10.) Thank you for the information. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc on freebsd 10
On Thu, 15 Dec 2011, Andriy Gapon wrote: > lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22 > installed during its configure step with the errors like the following in > config.log: Yes, I am aware of it. lang/gcc is the slowly moving, conservative option, lang/gcc46 being the fast, aggressive one. In consequence, lang/gcc46 has already been fixed with regard to FreeBSD 10, whereas this likely will take another month or so for lang/gcc when the next upstream release hapens. (Had I better network connectivity right now, I might try the backport, but really the use case for lang/gcc at this point is not users of FreeBSD 10. That's going to change with the changes to Mk/bsd.gcc.mk that we discussed on this list the last couple of days, and that will not happen before it builds on FreeBSD 10.) Gerald ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc on freebsd 10
On Thu, Dec 15, 2011 at 12:59:02PM +0200, Andriy Gapon wrote: > > lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22 > installed during its configure step with the errors like the following in > config.log: > > configure:2978: checking for C compiler default output file name > configure:3000: /usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/xgcc > -B/usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/ > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem > /usr/local/x86_64-portbld-freebsd10.0/include -isystem > /usr/local/x86_64-portbld-freebsd10.0/sys-include-g -O2 -gtoggle > -static-libstdc++ -static-libgcc conftest.c >&5 > xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found > > It seems that the error occurs because the preceding steps create > liblto_plugin.so.0.0 file, but no liblto_plugin.so link to it. Not sure why > is > that though. Maybe something about platform misdetection. .0.0 is almost sure indication of another case of FreeBSD-10 bug, i.e. freebsd1* glob that used to detect a.out shared libraries. pgpBSdrvbx6tS.pgp Description: PGP signature
Re: lang/gcc on freebsd 10
on 15/12/2011 12:59 Andriy Gapon said the following: > > lang/gcc build would fail for me on FreeBSD 10 (head) with binutils-2.22 > installed during its configure step with the errors like the following in > config.log: > > configure:2978: checking for C compiler default output file name > configure:3000: /usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/xgcc > -B/usr/obj/usr/ports/lang/gcc/work/build/./prev-gcc/ > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/bin/ > -B/usr/local/x86_64-portbld-freebsd10.0/lib/ -isystem > /usr/local/x86_64-portbld-freebsd10.0/include -isystem > /usr/local/x86_64-portbld-freebsd10.0/sys-include-g -O2 -gtoggle > -static-libstdc++ -static-libgcc conftest.c >&5 > xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found > > It seems that the error occurs because the preceding steps create > liblto_plugin.so.0.0 file, but no liblto_plugin.so link to it. Not sure why > is > that though. Maybe something about platform misdetection. > Yeah, lto-plugin/configure: freebsd* | dragonfly*) # DragonFly does not have aout. When/if they implement a new # versioning mechanism, adjust this. if test -x /usr/bin/objformat; then objformat=`/usr/bin/objformat` else case $host_os in freebsd[123]*) objformat=aout ;; *) objformat=elf ;; esac fi freebsd[123]* is it. Other configure scripts have this thing too. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
