Date: Fri, 27 Apr 2012 11:58:59 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Ruslan Ermilov <ru@freebsd.org> Cc: toolchain@freebsd.org, current@freebsd.org Subject: Re: [RFC] Un-staticise the toolchain Message-ID: <20120427085859.GY2358@deviant.kiev.zoral.com.ua> In-Reply-To: <20120426134140.GF14350@lo0.su> References: <20120426093548.GR2358@deviant.kiev.zoral.com.ua> <20120426134140.GF14350@lo0.su>
next in thread | previous in thread | raw e-mail | index | archive | help
--DSqUood0rpsROwaK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 26, 2012 at 05:41:40PM +0400, Ruslan Ermilov wrote: > On Thu, Apr 26, 2012 at 12:35:48PM +0300, Konstantin Belousov wrote: > > I think it is time to stop building the toolchain static. I was told th= at > > original reasoning for static linking was the fear of loosing the abili= ty > > to recompile if some problem appears with rtld and any required dynamic > > library. Apparently, current dependencies are much more spread, e.g. /b= in/sh > > is dynamically linked, and statically linked make does not solve anythi= ng. >=20 > ------------------------------------------------------------------------ > r76801 | sobomax | 2001-05-18 13:05:56 +0400 (Fri, 18 May 2001) | 6 lines >=20 > By default build make(1) as a static binary. It costs only 100k of additi= onal > disk space, buf provides measureable speed increase for make-intensive > operations, such as pkg_version(1), `make world' and so on. >=20 > MFC after: 1 week >=20 > ------------------------------------------------------------------------ >=20 > Have things changed enough that the above is not true anymore? >=20 > > Patch below makes the dynamically linked toolchain a default, adding an > > WITHOUT_SHARED_TOOLCHAIN build-time option for real conservators. > >=20 > > I did not looked in details why including bsd.own.mk makes NO_MAN > > non-functional. Please see the diffs for gnu/usr.bin/cc1*/Makefile. >=20 > Because you include bsd.own.mk before NO_MAN is defined, and the way > how .if works in make(1). What is the 'right' thing to do then ? Postpone the inclusion of bsd.own.mk after NO_MAN definition ? This makes the .if $MK_SHARED_TOOLCHAIN to not work. Or, continue to do what I have done, using 'MAN=3D' instead ? N.B. I will commit the change, with defaults kept to build toolchain static, just to avoid bikeshed. --DSqUood0rpsROwaK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk+aX9IACgkQC3+MBN1Mb4iq8wCghjt4unEw5lKeL7OvHxdh8QWf K3MAoIStz60XmlAapjxLB7skamxQjyxJ =Ygvx -----END PGP SIGNATURE----- --DSqUood0rpsROwaK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120427085859.GY2358>