Date: Thu, 19 Jan 2017 19:38:30 +0000 From: Glen Barber <gjb@FreeBSD.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: freebsd-current@freebsd.org Subject: Re: ISO image: where is the CLANG compiler? Message-ID: <20170119193830.GH1451@FreeBSD.org> In-Reply-To: <20170119191000.GG1451@FreeBSD.org> References: <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> <20170119191000.GG1451@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--VbfcI4OLZ4XW0yH2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 19, 2017 at 07:10:00PM +0000, Glen Barber wrote: > 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 Ju= de > > > 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 so= me disk > > > > >> space to /mnt, svn checkout CURRENT to /mnt and build a booteabl= e 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 = except > > > > > 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 compi= ler. And > > > > > the images (ISO, memstick et cetera) provided these days do not c= ontain > > > > > 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 a= nd > > > 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 v= ia > > copying missing libs and files from and identical intact source. After = that, I > > ran make buildword/buildkernel and was able to successfully install the= new > > system. > >=20 > > As I stated before: I already had a complete compiled world and kernel = existing > > in their proper, intact folders (usr/src and usr/obj). There was no nee= d to > > compile a whole world. > > Intending to "make installworld" failed, this is the real problem, beca= use the > > ISO/memstick images provided lack obviously in the required infrastruct= ure and > > so these images are worthless for sophisticated rescue operations - or = even > > 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= having > > the necessary tools aboard. So I consider every image useless for rescue > > operations except, maybe, the DVD image - but this one is not provided = anymore. > > For what reason? Time? Accepted. Space/disk usage? Well, welcome back i= n the > > stoneage of computer technology ...=20 > >=20 > > I remember faintly that there was a small discussion on the @CURRENT li= st, but > > I didn't realize that the result would be the extraction of the compile= r. > >=20 > > Just for the record: most servers delivered to us do not have CD/DVD dr= ives > > anymore - they are outdated and considered an extra these days. Purchas= ing 1 GB > > USB thumbdrives is getting even harder, smallest size my employer provi= des now > > is 2 GB. And most optical drives are DVD. From my point of view - and t= his is a > > personal view - the "standard" is > 1GB so there is no need to break do= wn by > > force the FreeBSD image (if size is the reason) down to < 800 MB or < 1= GB. 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 = provided > > as the extra. > >=20 >=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. >=20 > 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). >=20 > 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. >=20 > 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. >=20 Random thought: Brought up out-of-band, can you try this from a memstick.img and your already-built userland/kernel to do what you had originally tried to install the system? # make -C /usr/src WITHOUT_SYSTEM_COMPILER=3D1 DESTDIR=3D/wherever install= world I think this is why cc(1)/clang(1) is not being used from /usr/obj, and you don't have a compiler to compile the compiler. Glen --VbfcI4OLZ4XW0yH2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJYgRW2AAoJEAMUWKVHj+KTBygP/jNmaZg3r1mggd1tloq6+PGs EN0A934XnsPzI6tlppXWIJTl5DWN/CrrMKmGAW6jbnXI4lwjgUp6MnI83n8EbN+b YeZjnRLzQ88Ndybnkrmmd08Uvmttjdnm8KnitOgyx59rNNpx/pmw0RVwZyiiKpmY dWzRKsT+tHNmlcI9aVL4XhZgd+xTctCvJ9ogHjsYAFOH5V31AqUar9XpsO7Z6ORG ifIv6NXUG9wzJsPLN/INe8GYjXzJF0b5c1WlrA+gpitqoeQdMCPaHmJdSZEtmfaK BWk+yAWEkRA8MOyJsq61r8aThvPInpT01nIiUx4J1LHkuO5DW7KpDN7CDHWeHP1c D6A2LgG/t9Mgynqr8inku+Ptq78PHeCAJM3JtaF6/qWEdau7z0zCcNtfyQ+ZUaNv O1vVGj9gwJQ0ptFv9Rx0TvAbNWd2tPZ5mYmFTBK9WPcHpxLLmxGMEeLLwiYeIsbx 4RQCSR1FvdV2/HqQeuEu5OXSXIBGEShHTXmTWAgwIkb6GFZo2rutCUGCcTkMXUwB ggrcMQY4vHnOcdflTs9DZYDIRIDHT936THIkj+dSRdwW2SCFIxuENnxuA7HmIWhb N4G8ljYxVwayPfZn+dpKnCIBC36obnYn3Ne/HEmlNUq0xn2TRkDJK4HEOiuIdobE 44/NOUVxzZO9eeWrS5HU =VQOS -----END PGP SIGNATURE----- --VbfcI4OLZ4XW0yH2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170119193830.GH1451>