Date: Thu, 19 Jan 2017 19:10:00 +0000 From: Glen Barber <gjb@FreeBSD.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: Matthias Apitz <guru@unixarea.de>, freebsd-current@freebsd.org Subject: Re: ISO image: where is the CLANG compiler? Message-ID: <20170119191000.GG1451@FreeBSD.org> In-Reply-To: <20170119101636.5537f4fd@freyja.zeit4.iv.bundesimmobilien.de> References: <20170118084502.617bfc94@freyja.zeit4.iv.bundesimmobilien.de> <A73ED94A-89CE-41C5-98D2-F1611476797B@digsys.bg> <20170118101915.523d7d7b@freyja.zeit4.iv.bundesimmobilien.de> <20170118123515.GE58505@zxy.spb.ru> <20170118160801.229b4134@freyja.zeit4.iv.bundesimmobilien.de> <20170118153832.GA6905@c720-r292778-amd64> <20170118203726.7dea0515@thor.intern.walstatt.dynvpn.de> <ce772c1c-7506-6488-a6ae-6b95b2be8a20@freebsd.org> <20170119055816.GA2184@c720-r292778-amd64> <20170119101636.5537f4fd@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--TdkiTnkLhLQllcMS Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 19, 2017 at 10:16:46AM +0100, O. Hartmann wrote: > On Thu, 19 Jan 2017 06:58:16 +0100 > Matthias Apitz <guru@unixarea.de> wrote: >=20 > > El d=EDa Wednesday, January 18, 2017 a las 08:00:04PM -0500, Allan Jude > > escribi=F3: > >=20 > > > On 2017-01-18 14:37, O. Hartmann wrote: =20 > > > > Am Wed, 18 Jan 2017 16:38:32 +0100 > > > > Matthias Apitz <guru@unixarea.de> schrieb: > > > > =20 > > > >> 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 ? > > > >> > > > >> I do not understand all this hassle? > > > >> > > > >> matthias > > > >> =20 > > > >=20 > > > > Wow! > > > >=20 > > > > As I initially stated, that is EXACTLY what I was inclined to do ex= cept > > > > the fact that I had already an intact /usr/obj and usr/src with a > > > > complete compiled system. > > > >=20 > > > > I booted from mem stick and I was lost due to no cc! > > > >=20 > > > > Even for "make installworld" it seems I have to rely on the compile= r. And > > > > the images (ISO, memstick et cetera) provided these days do not con= tain > > > > any clang. =20 > >=20 > > Yes, you will need it and it will complain about missing it, if for > > example you moved 'obj and 'src' to other dirs after 'make build...' > >=20 > > But, in your case the mem image really is lacking the cc/clang; I > > fetched the image an did: > >=20 > >=20 > > # mdconfig -a -t vnode -u 1 -f > > ~guru/Downloads/FreeBSD-11.0-RELEASE-amd64-memstick.img # mount -o > > ro /dev/md1p3 /mnt # find /mnt -name clang > > /mnt/usr/share/doc/llvm/clang > > /mnt/usr/lib/clang > > /mnt/usr/lib/debug/usr/lib/clang > > # find /mnt -name cc > > /mnt/usr/include/netinet/cc > >=20 > > With this img alone, you can't compile a system :-( > >=20 > > Setup a system from DVD and build your own image containing a complete > > system on an USB key; with this boot your damaged system, recompile and > > reinstall world and kernel. If you (O. Hartmann) need a step by step > > guide, I could send it to you. > >=20 > > matthias > >=20 >=20 > Hello, >=20 > thanks for your help offering! very kind. >=20 > I've already solved the problem - not with the suggested process, but via > copying missing libs and files from and identical intact source. After th= at, I > ran make buildword/buildkernel and was able to successfully install the n= ew > system. >=20 > As I stated before: I already had a complete compiled world and kernel ex= isting > in their proper, intact folders (usr/src and usr/obj). There was no need = to > compile a whole world. > Intending to "make installworld" failed, this is the real problem, becaus= e the > ISO/memstick images provided lack obviously in the required infrastructur= e and > so these images are worthless for sophisticated rescue operations - or ev= en > such a simple ask as described initially in my posting. >=20 > I created images on CURRENT of my own - they all lack in the ability of h= aving > the necessary tools aboard. So I consider every image useless for rescue > operations except, maybe, the DVD image - but this one is not provided an= ymore. > For what reason? Time? Accepted. Space/disk usage? Well, welcome back in = the > stoneage of computer technology ...=20 >=20 > I remember faintly that there was a small discussion on the @CURRENT list= , but > I didn't realize that the result would be the extraction of the compiler. >=20 > Just for the record: most servers delivered to us do not have CD/DVD driv= es > anymore - they are outdated and considered an extra these days. Purchasin= g 1 GB > USB thumbdrives is getting even harder, smallest size my employer provide= s now > is 2 GB. And most optical drives are DVD. From my point of view - and thi= s is a > personal view - the "standard" is > 1GB so there is no need to break down= by > force the FreeBSD image (if size is the reason) down to < 800 MB or < 1 G= B. I'd > consider having < 2GB the line of standards (2 GB USB mem drive). > And for those, with need of very small images, smaller images could be pr= ovided > as the extra. >=20 I do want to weigh in here and inform I am actively watching this thread. clang(1) is not in disc1.iso or bootonly.iso because the MK_TOOLCHAIN knob is disabled in the targets that generate them. This has actually been the case for quite some time for these images. dvd1.iso does contain clang, but very rarely (if ever, actually) are there dvd1.iso images produced for development snapshots. This is, in part, solely because of the additional space/bandwidth required on the mirrors (not just mirrors controlled by the Project, but third-party mirrors as well). I am working on splitting out how the memstick.img and disc1.iso images are produced, but ran into a problem which I'm looking into a workaround that is backwards-compatible. Since for USB images, a 700MB limit does not make sense, and right now it just so happens that the memstick.img is created from the same contents of disc1.iso. I know this does not help with the immediate issue, but wanted to chime in with I do see and understand the larger issue, and am working on a more long-term resolution instead of a one-line workaround. Glen --TdkiTnkLhLQllcMS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYgQ8DAAoJEAMUWKVHj+KT1k0P/0xOpo4YF54MMzHIPelLqc0P M+MKUfrEE2OszyL91UmSNzIquAXcfI+7UuwZlge2eIYB/7iRIdYJpTNy82rqulud lNFvU9nlbgVdhg78FuxwwTzlvq36L13vyEi1X7sk6QtYLFz5vJ1nzQs2Wa/sznGg vAZ9TrARryBIcWE5YYtAn2TjTqLfpOBAKEV1hJt4t95SrTckxT8r1oWvN6MVDWL3 /GwisKkuCBR+c8TwoYTfm9MsGgzXiyxIulGl6eUZB1dO7KVwTL6ztzgKXHHJ3svd yTqO4HZ8DxFQvD1HzDUpL8OjSJdC3NCxbsiK0AiCQ3xEQ+/uW4a7zG40lpu79QfP 1/7UZX+YafdGnk5PPkP64LGzuPH3LVYp9RIw1TbTpnon6z0R8benz/D7kMthwIMY A8l3bmmzAmiKHJwMqVhSXan5ZplJ6I6Ywam2UcxtnwX2P7lrnpoxba3DwefWg/lG PsWgvoW6biywNITNdW0ov/3MadNtTF39Mpf/tsd5hDAyQmNLgTG3TOSlDTd3KofX m+MFjjb43Ij38yo6AdNb9IroYuUxt5NnF6ptHHGPVPjEJfeCgKImEvnlg7TIvMRV FHzw2roTY7dSkFhLUgpJLKMrrVJRvby8jkuq/CJcST87uSUldxFn79cUAzX4vpl2 xykaF21nk3VDhgb2FRfU =8cgj -----END PGP SIGNATURE----- --TdkiTnkLhLQllcMS--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170119191000.GG1451>