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

On 15 Jan 2018, at 07:42, O. Hartmann 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

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

Try updating? just upgraded to r327991 and it was smooth sailing. On Sun, Jan 14, 2018 at 10:42 PM, O. Hartmann wrote: > One of our CURRENT boxes is repeateadly disobeying to build "buildworld" > (make > buildkernel seems to work as I did several kernels right now). > >

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

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,

Re: [CFT] AMD cpu microcode update port sysutils/devcpu-data D13832

How far it's supposed to support legacy CPUs on FreeBSD? x86info Found 2 identical CPUs Extended Family: 0 Extended Model: 1 Family: 6 Model: 23 Stepping: 10 Type: 0 (Original OEM) CPU Model (x86info's best guess): Unknown model. Processor name string (BIOS programmed): Intel(R) Core(TM)2 Duo

Re: msdosfs_iconv

blubee blubeeme wrote (2018/01/14): > if you first run the mount_msdosfs command as root, it'll load the locale > settings just fine. > If you logout or reboot and try to call mount_msdosfs -L [locale] as a > regular user; > The command will fail. If you have kiconvtool already installed and

Re: /lib/casper: read error: Invalid argument

Am Sun, 14 Jan 2018 06:57:38 -0500 Charlie Li schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 14/01/2018 06:10, Hartmann, O. wrote: > > I tried to investigate with the USB image created 10th January > > 2018 from ISO downloads and it showed, that /boot/

Re: /lib/casper: read error: Invalid argument

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 14/01/2018 06:10, Hartmann, O. wrote: > I tried to investigate with the USB image created 10th January > 2018 from ISO downloads and it showed, that /boot/ was obviously > intact, but files in /usr/sbin, /usr/bin were zero in size, also > some

/lib/casper: read error: Invalid argument

Again, I ran into a havoc update of CURRENT last night. While booting a freshly installed kernel and performing "make -j4 installworld", the box suddenly rebooted - out of the blue. With the wrecked CURRENT left behind (r327866), I'm not able to boot even into single user mode. The box halts