Date: Sun, 22 Jan 2017 00:24:52 +0100 From: "O. Hartmann" <ohartmann@walstatt.org> To: Glen Barber <gjb@FreeBSD.org> Cc: "O. Hartmann" <ohartmann@walstatt.org>, freebsd-current@freebsd.org Subject: Re: ISO image: where is the CLANG compiler? Message-ID: <20170122002452.69578804@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170121222001.40ce534c@thor.intern.walstatt.dynvpn.de> 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> <20170119193830.GH1451@FreeBSD.org> <20170121222001.40ce534c@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/zWj77xfIRzgcQkd9/5/pEtg Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Am Sat, 21 Jan 2017 22:20:01 +0100 "O. Hartmann" <o.hartmann@walstatt.org> schrieb: > Am Thu, 19 Jan 2017 19:38:30 +0000 > Glen Barber <gjb@FreeBSD.org> schrieb: >=20 > > On Thu, Jan 19, 2017 at 07:10:00PM +0000, Glen Barber wrote: =20 > > > On Thu, Jan 19, 2017 at 10:16:46AM +0100, O. Hartmann wrote: =20 > > > > 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, Alla= n 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, moun= t some disk > > > > > > >> space to /mnt, svn checkout CURRENT to /mnt and build a boot= eable 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 wi= th 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 c= ompiler. And > > > > > > > the images (ISO, memstick et cetera) provided these days do n= ot contain > > > > > > > any clang. =20 > > > > >=20 > > > > > Yes, you will need it and it will complain about missing it, if f= or > > > > > 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 com= plete > > > > > system on an USB key; with this boot your damaged system, recompi= le and > > > > > reinstall world and kernel. If you (O. Hartmann) need a step by s= tep > > > > > 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, b= ut via > > > > copying missing libs and files from and identical intact source. Af= ter 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 ker= nel existing > > > > 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, = because the > > > > ISO/memstick images provided lack obviously in the required infrast= ructure 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 abilit= y of having > > > > the necessary tools aboard. So I consider every image useless for r= escue > > > > operations except, maybe, the DVD image - but this one is not provi= ded anymore. > > > > For what reason? Time? Accepted. Space/disk usage? Well, welcome ba= ck in the > > > > stoneage of computer technology ...=20 > > > >=20 > > > > I remember faintly that there was a small discussion on the @CURREN= T list, but > > > > I didn't realize that the result would be the extraction of the com= piler. > > > >=20 > > > > Just for the record: most servers delivered to us do not have CD/DV= D drives > > > > anymore - they are outdated and considered an extra these days. Pur= chasing 1 GB > > > > USB thumbdrives is getting even harder, smallest size my employer p= rovides now > > > > is 2 GB. And most optical drives are DVD. From my point of view - a= nd this is a > > > > personal view - the "standard" is > 1GB so there is no need to brea= k down 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 imag= es > > > are produced, but ran into a problem which I'm looking into a workaro= und > > > that is backwards-compatible. Since for USB images, a 700MB limit do= es > > > 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 chi= me > > > 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 > >=20 > > Random thought: > >=20 > > 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? > >=20 > > # make -C /usr/src WITHOUT_SYSTEM_COMPILER=3D1 DESTDIR=3D/wherever ins= tallworld > >=20 > > 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. > >=20 > > Glen > > =20 >=20 > I ran on a different(!!!!) machine in the very same situation while insta= lling kernel > and world in SINGLE USER mode! Different machine, also SSD (different mod= el): the > symptomes are the very same. Close to the end of installations of lib32, = the box goes > down, crashes. >=20 > After reboot, it can not find any kernel because /boot/kernel as well as = every "per > default" installed file/directory is not existent anymore - except thiose= files I > touched/copied. >=20 > Files in /rescue do have all NULL size! That was the same on the other bo= x on which > crash I initiated this thread. The same in /sbin, /bin, /usr/bin, /usr/sb= in and /lib. > Some libs/files are NULL in size. >=20 > So, apart from the fact that CURRENT disrupts obviously filesystems on in= stallations, I > had the doubtful chance to take a test on your suggestion above: It doesn= 't work! >=20 > I booted this time again from the USB thumdrive with the recent FreeBSD 1= 2-CURRENT image > without the compiler and mount the still intact usr/obj and usr/src from = the corrupted > SSD onto the USB thumdrive and tried to do as requested. >=20 > make -C /usr/src WITHOUT_SYSTEM_COMPILER=3D1 DESTDIR=3D/wherever installw= orld >=20 > The script bugs out at "bsd.compiler.mk line 145: Unable to determine com= piler type for > CC=3Dcc. Consider setting COMPILER_TYPE" >=20 > Setting COMPILE_TYPE=3Dcc results in "sh: cc not found", setting to "clan= g" doesn't work > either. >=20 > Apart from the fact of CURRENT to be incapable of rescuing, there seems t= o be a very > serious issue with CURRENT regarding its filesystem stability and I do no= t know how to > address this in the correct way :-( >=20 > I use NanoBSD for about a year for several projects and I already have a = useful USB > thumdrive with a full grown system (~ 836 MB if I'm not confused includin= g the > compiler). I tried to makeinstallworld, but this time, it seems that also= the usr/obj > has been corrupted, so I had to perform a buildworld, which is still runn= ing. >=20 > From my little experiences with building NanoBSD and the use of etc/src.c= onf as the > source for delegating what is used in the target image and not, I was rea= lly wondering > that the "RELEASE" build infrastructure is not using a predefined src.con= f to reduce the > size and content of the resulting image. Instead, some "WITHOUT_TOOLCHAI= N" hidden and > hard coded knobs are used :-( Somehow the whole thing got more confusing. >=20 > I can understand that some people want some small images for their instal= lation > processes, but I think they can perform the task of creating their own im= ages via make > relaese very easily. > In cases were someone crashed, like me, it would a great benefit having s= ome real rescue > stuff around instead of crippled images. But this might be a different vi= ew. >=20 > regards, >=20 > oh=20 >=20 I now have on one box a partially restored system. It seems, that this time= , a very serious bug made proper work. I need to restore the library installation/structure in /usr/lib. It is cor= rupted and has been corrupted by "make installword" with WITHOUT_SYSTEM_COMPILER=3D1 (= which seems useless in this case) and COMPILER_TYPE=3Dclang. There are dead links in /u= sr/lib, especially libthr.so.X is pointing to nothing. As a result of this desaster I can state, that the images provided official= ly are not capable of performing such a rescue. Dead man in the water :-(=20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs. 4 BDS= G). --Sig_/zWj77xfIRzgcQkd9/5/pEtg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWIPtxAAKCRDS528fyFhY lPudAgCOSi45odEP9JBvo4NmLYsTb8p2vGu/glRB2YWLQHgx6FfWS4XSCPDXNMTt kjrpa3O67idnLS3yfIGAgmIotIvZAf4r/i3JsO+FEUA5aIKkEJ+XZ14Rx+wqVAeH w6ctv0riO1EOJqild0/oqVNihfs9jGGICvyaAh4BE/PTc7GCihWY =WpWs -----END PGP SIGNATURE----- --Sig_/zWj77xfIRzgcQkd9/5/pEtg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170122002452.69578804>