Date: Sat, 8 Feb 2014 00:24:34 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: lev@FreeBSD.org Cc: ports@freebsd.org Subject: Re: USE_GCC politic -- why so many ports has it as runtime dependency? Message-ID: <A136680D-BD8A-4819-9600-6B640AB16ADE@FreeBSD.org> In-Reply-To: <1133138786.20140207202949@serebryakov.spb.ru> References: <1133138786.20140207202949@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_84D02891-7A1B-46D4-9E7C-5B49874A2092 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 07 Feb 2014, at 17:29, Lev Serebryakov <lev@freebsd.org> wrote: > I was very surprised, when virtualbox-ose-additions-4.3.6, installed as > binary package on 10.0/amd64, pulled gcc "lang/gcc" (567MiB) and > "devel/binutils" (50MiB), and I don't mention mpc/mprf/gmp. > > I understand, that this package could not build with clang, Ok. But why > does it need all these developer tools AT RUNTIME?! > > It even doesn't have "libjcc.so" or "libsdc++.so" in "Shared Libs > required"! > > And it seems, that most of USE_GCC-equipped ports pull all this development > toolkit for nothing! Well, some ports can be more or less difficult to get building with clang. So depending on whether the maintainer(s) wish to choose the way of least resistance, they will sometimes decide to set USE_GCC. Since a lot (maybe even most?) of modern software requires something way newer than our old gcc in base, and 10.0 and later ship without gcc by default, it is logical to use lang/gcc in such cases too. > Maybe, it is time to make USE_GCC work as if ":build" is specified by > default? And, yes, add additional port with gcc RUNTIME? As far as I know, this is a feature still in the works for pkgng. E.g. using one port work directory for multiple packages, for example -libs, -devel and so on. Although some people tend to hate such modularization with great passion. Paint for more bikesheds... :-) -Dimitry --Apple-Mail=_84D02891-7A1B-46D4-9E7C-5B49874A2092 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlL1azYACgkQsF6jCi4glqPPbQCgs721Fx470m60FyjtlkOWBC4w 7cgAoKgRjukdZZSxMSywXmEnbRnUkv8U =sMe4 -----END PGP SIGNATURE----- --Apple-Mail=_84D02891-7A1B-46D4-9E7C-5B49874A2092--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A136680D-BD8A-4819-9600-6B640AB16ADE>