Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 3 Nov 2013 16:00:12 +0200
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Peter Jeremy <peter@rulingia.com>
Cc:        vbox@FreeBSD.org
Subject:   Re: ports/182468: [patch] lang/gcc builds unrunnable emulators/virtualbox-ose
Message-ID:  <20131103140012.GF59496@kib.kiev.ua>
In-Reply-To: <201311031010.rA3AA1UI094428@freefall.freebsd.org>
References:  <201311031010.rA3AA1UI094428@freefall.freebsd.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On Sun, Nov 03, 2013 at 10:10:01AM +0000, Peter Jeremy wrote:
> The following reply was made to PR ports/182468; it has been noted by GNATS.
> 
> From: Peter Jeremy <peter@rulingia.com>
> To: Volodymyr Kostyrko <c.kworr@gmail.com>
> Cc: bug-followup@FreeBSD.org
> Subject: Re: ports/182468: [patch] lang/gcc builds unrunnable
>  emulators/virtualbox-ose
> Date: Sun, 3 Nov 2013 21:09:07 +1100
> 
>  --jI8keyz6grp/JLjh
>  Content-Type: text/plain; charset=us-ascii
>  Content-Disposition: inline
>  Content-Transfer-Encoding: quoted-printable
>  
>  On 2013-Nov-01 15:19:32 +0200, Volodymyr Kostyrko <c.kworr@gmail.com> wrote:
>  >Isn't it easier to map libstdc++.so.6 to gcc46/libstdc++.so.6 in=20
>  >/etc/libmap.conf?
>  
The libstdc++.so ABI is supposed to be backward-compatible, so, in theory,
libstdc++ from gcc 4.6 should be a drop-in replacement for the libstdc++
from our base.

>  As a general solution, definitely not - that would break programs (eg
>  those compiled with the base C++) that expect libstdc++.so.6 to be the
>  one in /usr/lib.
It should not.

>  
>  As a specific solution for VBox-ose, not really.  That would require
>  hand-crafting a libmap.conf entry that is only valid for one version
>  of gcc and is unknown to the ports/pkg system.  It would look like it
>  works up until VBox gets copied onto another system or lang/gcc changed
>  to a different version.
>  
>  Any fix has to fit into the ports/pkg system so it gets handled automatical=
>  ly
>  and doesn't get lost.  Ideally, lang/gcc (etc) would be fixed so they were
>  usable without having to rely on hacks in Mk/bsd.gcc.mk.
>  
>  --=20
>  Peter Jeremy
>  
>  --jI8keyz6grp/JLjh
>  Content-Type: application/pgp-signature
>  
>  -----BEGIN PGP SIGNATURE-----
>  Version: GnuPG v2.0.21 (FreeBSD)
>  
>  iKYEARECAGYFAlJ2IMNfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl
>  bnBncC5maWZ0aGhvcnNlbWFuLm5ldDBCRjc3QTcyNTg5NEVCRTY0RjREN0VFRUZF
>  OEE0N0JGRjAwRkI4ODcACgkQ/opHv/APuIdMgACZAUlD2snT239g/tUE8DAuLRiX
>  vTAAnihkGEfsczkKjGd+dR+XS/ZDGO52
>  =2rRy
>  -----END PGP SIGNATURE-----
>  
>  --jI8keyz6grp/JLjh--
> _______________________________________________
> freebsd-emulation@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org"

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBAgAGBQJSdlbrAAoJEJDCuSvBvK1BlOkP/39kky6U9eZTV/kPCb7UeJxx
SsNb/ZPj1lVYpxCSVGkLO+d9ObFQ6aMEpTaf465dEFbbP69+hG5xG1KgootuXRKP
aBFdnG6DVBifkEMqRIRmCyKp+WO5gjmtJ0xZ9e9lDo1+q8k333VAAmjIa6d95Fum
6PH5Ctg2fkT9CvUqVoXi6MdnGZkOcuW+FKyKdvCgV1AGfchfIVQzlpPUfC/uSPeD
dlkh0cYN53Lb+hA4w8yKSZobLtaz0JTSB5VQZ1urZbo//ygHLYfBsxrDrQXBbAEt
QqMTT1QT8hbFWbU4WOW+KEKxXAnuydSk7hCziZ71KhRcT0lJLKkaKV2W+rm5e4UK
B7j2WjsNDR8GGx5f07OoFd06mi3V01bwgr88o8RJ0lbPrF6CaJxjqIQ3GFYRWMJj
kZkxwF4G561EEbRHMWG1xIx6zQsi6iv1aCrx+AqBIOXxvMpt5gjqCIafxjzMa//a
Wd2m1PnydgnO+bN5uMLiSORsPgTYtt2dpEGbEopuaPC5TOOTq+rCZJeJ6JJD9eZ9
Js1zc/f/MRaGGKwi3PjpwpXjxpBunpq5dTmB2LjEpzSMGq0HOlvT2WR+DxMPGNqz
d4O3HiU13Vedv0p2uS800XGVvKFKxLfOAlaYE448Nta9lkcPX8Zlhjg70W0p90r+
JQQYxcTbOdKOfMqrvq54
=XyBO
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131103140012.GF59496>