CURRENT: can't buildworld; /usr/bin/ld: error: cannot open crt1.o:

[O. Hartmann]

On Mon, 15 Jan 2018 13:21:22 +0100
"O. Hartmann" <o.hartmann at walstatt.org> wrote:

> On Mon, 15 Jan 2018 08:45:56 +0100
> Dimitry Andric <dim at FreeBSD.org> wrote:
> 
> > On 15 Jan 2018, at 07:42, O. Hartmann <ohartmann at walstatt.org> wrote:  
> > > 
> > > One of our CURRENT boxes is repeateadly disobeying to build
> > > "buildworld" (make buildkernel seems to work as I did several kernels
> > > right now).
> > > 
> > > The hosts's world is as of Wednesday, 10th January, the kernel's revison
> > > is
> > > 
> > > FreeBSD 12.0-CURRENT #0 r327871: Fri Jan 12 12:18:19 CET 2018 amd64.
> > > 
> > > I did, as a test, Friday, 12th Jan, as you can see, the last kernel build.
> > > 
> > > The host in question also carries a variety of release, package an jail
> > > builds in separate source trees (CURRENT in most cases, to keep them away
> > > from the host's source tree). Those separate source trees also reject to
> > > build.
> > > 
> > > After performing a "make cleanworld" to startover (even this morning,
> > > when I watched LLVM/CLANG 6.0.0 has slipped in), I face still the same
> > > error:    
> > ...  
> > > --------------------------------------------------------------    
> > >>>> stage 1.2: bootstrap tools    
> > > --------------------------------------------------------------    
> > ...  
> > > Building /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/llvm-tblgen
> > > /usr/bin/ld: error: cannot open crt1.o: No such file or directory
> > > c++: error: linker command failed with exit code 1 (use -v to see
> > > invocation)    
> > 
> > If this happens during bootstrap-tools, the toolchain on your host
> > system is busted.  Do you have the following .o files in /usr/lib?
> > 
> > Scrt1.o
> > crt1.o
> > crtbegin.o
> > crtbeginS.o
> > crtbeginT.o
> > crtend.o
> > crtendS.o
> > crti.o
> > crtn.o
> > gcrt1.o
> > 
> > If these are missing, restore them from a backup, or extract them from
> > an installation image.
> > 
> > -Dimitry
> >   
> 
> 
> # ll /usr/lib/Scrt1* /usr/lib/crt* /usr/lib/gcrt1.*
> 
> 160561 -r--r--r--  1 root  wheel  -  3.2K 10 Jan. 16:14 /usr/lib/Scrt1.o
> 161693 -r--r--r--  1 root  wheel  -  2.2K 10 Jan. 16:14 /usr/lib/crtbegin.o
> 161696 -r--r--r--  1 root  wheel  -  2.3K 10 Jan. 16:14 /usr/lib/crtbeginS.o
> 161695 -r--r--r--  1 root  wheel  -  2.7K 10 Jan. 16:14 /usr/lib/crtbeginT.o
> 161694 -r--r--r--  1 root  wheel  -  1.5K 10 Jan. 16:14 /usr/lib/crtend.o
> 161697 -r--r--r--  1 root  wheel  -  1.5K 10 Jan. 16:14 /usr/lib/crtendS.o
> 160518 -r--r--r--  1 root  wheel  -  800B 10 Jan. 16:14 /usr/lib/crti.o
> 160526 -r--r--r--  1 root  wheel  -  896B 10 Jan. 16:14 /usr/lib/crtn.o
> 160565 -r--r--r--  1 root  wheel  -  3.7K 10 Jan. 16:14 /usr/lib/gcrt1.o
> 
> Something went wrong :-(
> 
> Thank you for the hint,
> I try to recover from backup/image.
> 
> Oliver
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"

Sorry for the hurry (I was in a hurry).

As my listing indicates, crt1.o was missing. CURRENT does strange things
lately. The same day I've updated the base system, luckily the jail for
poudriere, based on the base system, has been updated and so I was able to
restore /usr/lib/crt1.o.

Oliver