From owner-freebsd-questions@freebsd.org Wed Jan 18 19:37:51 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3893BCB6E61; Wed, 18 Jan 2017 19:37:51 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B6B41A52; Wed, 18 Jan 2017 19:37:49 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.71.34]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M39zL-1cjP463K6R-00sui8; Wed, 18 Jan 2017 20:37:33 +0100 Date: Wed, 18 Jan 2017 20:37:26 +0100 From: "O. Hartmann" To: Matthias Apitz Cc: Slawa Olhovchenkov , freebsd-current , freebsd-questions , "O. Hartmann" , Daniel Kalchev Subject: Re: ISO image: where is the CLANG compiler? Message-ID: <20170118203726.7dea0515@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170118153832.GA6905@c720-r292778-amd64> References: <20170118084502.617bfc94@freyja.zeit4.iv.bundesimmobilien.de> <20170118101915.523d7d7b@freyja.zeit4.iv.bundesimmobilien.de> <20170118123515.GE58505@zxy.spb.ru> <20170118160801.229b4134@freyja.zeit4.iv.bundesimmobilien.de> <20170118153832.GA6905@c720-r292778-amd64> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/ZD/NMegrg9aZZLiL7RLdYPV"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:ogEPj5cHzh9XD4ndr/v/Dpr8i92XT36YGlSOqnvxV2AfwzbxINK 738pJonFyXgTTNdQg7kRM51q6IUaWq8X73y93zthAEpfcZaAD2ttUoATm0Kno5gcLarzHe/ yz5o2tTxZJzlZr9gpOGpdg9OPUW91CDkArN0RwcarSIvS1eXjX5nq2Y6qNs8hQiyW1wlo5p yYUubpeyXLQRW+5FkMiFg== X-UI-Out-Filterresults: notjunk:1;V01:K0:Sf/4xiEfHFY=:IZUVgRwQjE6WgyDfvkJY0j HKIKkTpAb0WqJEXqN7i7FoIuG1EHuypazJEHhMP3T4z6eI26m2GT8uuvTd/pva/7nmI4geWaF VMihtx9nZ6AIDYBgqJ9NIZTBNIQMg0sTx1tsM52fm9rDgmVwCPkC/VPUVJlla7uFb0bCNE5/r EsTurzlkeIjHci2tLZU765djiuZiwtBPNm9ZAEKRf+9RqK/kwzI5sncEi7DxCoEizBR67PF+M c1ycKj9dmfwdHyPHgKofIMCbPJnV1kzAISG2/BB96KGkg6+YbV8SoB4DkY8txJc/ovfBLSTQP wtYqd2kLyqktArTZtMRLmti594KHJmp4UgyMUHAu1i/+KLBczGk19wslYhAkRQqrmyYcKqe7I kWR9bvHtAd1DcoFFdd3q0bXUvqhbJtBQKWqqUzUvj0ZUQo9MuNGUUWg0THAFHAUsrpX7wpj3Y CH5kxyafrzK15HCWzJzSedEkMnU4+Mh2cRRw1QnMny7nTEL8fwxtxjNuLaSE7xBIaO66ek5cx Q5xSq6FePb6qhwwDbrqsQcyVNRrtWpaxB75mSCav07moV4PLuEUjfpJDpAyzF50gB2iWHm0Qm eOtGvLjjEWlObnpsYdMlV0u0YKl7TfBUj7DsKhUL+JkycokTFS15wfoeB+uLt8Zh7bc+rVzdc Gt5WeN9exNJV2HduCQen/ggJpHNfTkp4ppN9pURzUz95wLA1+l3DxuK0nBTtsbwNT1rTACEf+ hIbzvaMxyY9CXQ9qopH23N+2CkTJPQk2Ak7ALQvWbG2dXsbXRmQNbiwyQmk= X-Mailman-Approved-At: Wed, 18 Jan 2017 20:16:17 +0000 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 19:37:51 -0000 --Sig_/ZD/NMegrg9aZZLiL7RLdYPV Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Wed, 18 Jan 2017 16:38:32 +0100 Matthias Apitz schrieb: > Why you do not just boot from USB some mem stick image, mount some disk > space to /mnt, svn checkout CURRENT to /mnt and build a booteable system > (world and kernel) and install to DESTDIR=3D/mnt ? >=20 > I do not understand all this hassle? >=20 > matthias >=20 Wow! As I initially stated, that is EXACTLY what I was inclined to do except the= fact that I had already an intact /usr/obj and usr/src with a complete compiled system. I booted from mem stick and I was lost due to no cc! Even for "make installworld" it seems I have to rely on the compiler. And t= he images (ISO, memstick et cetera) provided these days do not contain any clang. So, I tried /usr/src/release ... for the first time. The image does also no= t contain the necessary tools for a full "make installworld installkernel" - not to speak= of "compiling" world. I dodn't work (at least for me).=20 I try to figure out how to avoid this crazy and useless shrinking of the IS= O images - somehow when building NanoBSD, there are knobs with which we can prevent th= e build and/or installation of subsets like compiler, toolchain et cetera. The way such th= ing is provided via src.conf and make.conf is fine and sophisticated. But "RELEASE= " seems to handle things different, and the standard is useless for a rescue mission. So far. It might be that I have overlooked something ... Regards, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/ZD/NMegrg9aZZLiL7RLdYPV Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWH/D9gAKCRDS528fyFhY lPS5AgCDarnV2KaijxQtA1exsIafTmlKmiaan5Itcyr3CVm97TihY6PxZmmt4La8 eBuxnqK5XJvumZ/Mz19Vo7cRxTAFAf4uyqrNBzpFt9IZMTkxemO1afQ6gEXOc4eJ U/sebBiTyu2nAPHczL3k2m9lURQj9Qde2Qs+WUKNkQZdMrBDI3c3 =tpSS -----END PGP SIGNATURE----- --Sig_/ZD/NMegrg9aZZLiL7RLdYPV--