installkernel with PORTS_MODULES+=graphics/drm-515-kmod stopped working

[Bakul Shah]

I build{world,kernel} on one machine but install
everything from the target machine, with /usr/obj
and /usr/src from the build machine nfs mounted.
/etc/src.conf (on target and build machines) has
PORTS_MODULES+=graphics/drm-515-kmod to build
this port at the same time. This used to work at
least until Nov 1, 2023 but now stopped working.

What I don't understand is why is install trying
to install to /usr/obj/..., which is really on
the build tree.

It this known? Is this style of building .ko ports
still supported?

The make infrastructure has gotten far too complicated
and baroque over the years so before diving into it
I am looking any shortcuts! Thanks!

[note: /usr/ports is mounted from the build machine
/usr/src is symlinked to /home/FreeBSD/stable-14
/etc/src.conf is the same on both machines.
From target (as root) I can create root owned files
under /usr/obj on the target]

===>   drm-515-kmod not installed, skipping
===>  Staging for drm-515-kmod-5.15.118_2
No name and/or group mapping for uid,gid:(0,0)
No name and/or group mapping for uid,gid:(0,0)
...
No name and/or group mapping for uid,gid:(0,0)
===>   Generating temporary packing list
===> dmabuf (install)
install -T release -o root -g wheel -m 555   dmabuf.ko 
/usr/obj/home/FreeBSD/stable-14/amd64.amd64/sys/GENERIC/usr/ports/graphics/drm-515-kmod/work/stage/boot/modules/
===> ttm (install)
install -T release -o root -g wheel -m 555   ttm.ko 
/usr/obj/home/FreeBSD/stable-14/amd64.amd64/sys/GENERIC/usr/ports/graphics/drm-515-kmod/work/stage/boot/modules/
===> drm (install)
install -T release -o root -g wheel -m 555   drm.ko 
/usr/obj/home/FreeBSD/stable-14/amd64.amd64/sys/GENERIC/usr/ports/graphics/drm-515-kmod/work/stage/boot/modules/
No name and/or group mapping for uid,gid:(0,0)
install: 
/usr/obj/home/FreeBSD/stable-14/amd64.amd64/sys/GENERIC/usr/ports/graphics/drm-515-kmod/work/stage/boot/modules/drm.ko:
 chown/chgrp: Operation not permitted
*** Error code 71

Stop.
make[6]: stopped in 
/usr/obj/home/FreeBSD/stable-14/amd64.amd64/sys/GENERIC/usr/ports/graphics/drm-515-kmod/work/drm-kmod-drm_v5.15.118_3/drm
*** Error code 1

Stop.
make[5]: stopped in 
/usr/obj/home/FreeBSD/stable-14/amd64.amd64/sys/GENERIC/usr/ports/graphics/drm-515-kmod/work/drm-kmod-drm_v5.15.118_3
*** Error code 1

Re: Error during installkernel

[Nuno Teixeira]

Same here:

---
kldxref /boot/testing
failed to read progbits
failed to read progbits
failed to read progbits
failed to read progbits
failed to read progbits
ef_read_entry failed
*** Signal 11

Stop.
make[3]: stopped in /usr/src/sys/modules
*** Error code 1

Stop.
make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
*** Error code 1

Stop.
make[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src
---

Felix Palmen  escreveu no dia terça, 26/10/2021 à(s)
15:18:

> * Filippo Moretti via current  [20211026 13:53]:
> > I tried to update my system today everything fine but installkernel:==>
> zlib (install)install -T release -o root -g wheel -m 555 zlib.ko
> /boot/kernel/install -T dbg -o root -g wheel -m 555 zlib.ko.debug
> /usr/lib/debug/boot/kernel/kldxref /boot/kernelfailed to read
> progbitsef_read_entry failed*** Signal 11Stop.make[3]: stopped in
> /usr/src/sys/modules*** Error code 1Stop.make[2]: stopped in
> /usr/obj/usr/src/amd64.amd64/sys/STING*** Error code 1Stop.make[1]: stopped
> in /usr/src*** Error code 1Stop.make: stopped in /usr/src[root@sting
> /usr/src]#
> >
> > [root@sting /usr/src]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD
> 14.0-CURRENT #57 heads/main-n250195-6ba2210ee03: Thu Oct 21 21:19:23 CEST
> 2021 filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64 Filippo
>
> Ignore it. The new kernel should boot anyways, and after installworld,
> installkernel will finish successfully.
>
> It seems kldxref again needs some new feature, but it's not part of the
> temporary tools built, so the host's (old) kldxref is used.
>
> --
>  Dipl.-Inform. Felix Palmen ,.//..
>  {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
>  {pgp public key} http://palmen-it.de/pub.txt   //   """""""""""
>  {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A
>

Re: Error during installkernel

[Felix Palmen]

* Filippo Moretti via current  [20211026 13:53]:
> I tried to update my system today everything fine but installkernel:==> zlib 
> (install)install -T release -o root -g wheel -m 555 zlib.ko 
> /boot/kernel/install -T dbg -o root -g wheel -m 555 zlib.ko.debug 
> /usr/lib/debug/boot/kernel/kldxref /boot/kernelfailed to read 
> progbitsef_read_entry failed*** Signal 11Stop.make[3]: stopped in 
> /usr/src/sys/modules*** Error code 1Stop.make[2]: stopped in 
> /usr/obj/usr/src/amd64.amd64/sys/STING*** Error code 1Stop.make[1]: stopped 
> in /usr/src*** Error code 1Stop.make: stopped in /usr/src[root@sting 
> /usr/src]# 
> 
> [root@sting /usr/src]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 
> 14.0-CURRENT #57 heads/main-n250195-6ba2210ee03: Thu Oct 21 21:19:23 CEST 
> 2021 filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64 Filippo

Ignore it. The new kernel should boot anyways, and after installworld,
installkernel will finish successfully.

It seems kldxref again needs some new feature, but it's not part of the
temporary tools built, so the host's (old) kldxref is used.

-- 
 Dipl.-Inform. Felix Palmen ,.//..
 {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
 {pgp public key} http://palmen-it.de/pub.txt   //   """""""""""
 {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A


signature.asc
Description: PGP signature

Error during installkernel

[Filippo Moretti via current]

I tried to update my system today everything fine but installkernel:==> zlib 
(install)install -T release -o root -g wheel -m 555 zlib.ko 
/boot/kernel/install -T dbg -o root -g wheel -m 555 zlib.ko.debug 
/usr/lib/debug/boot/kernel/kldxref /boot/kernelfailed to read 
progbitsef_read_entry failed*** Signal 11Stop.make[3]: stopped in 
/usr/src/sys/modules*** Error code 1Stop.make[2]: stopped in 
/usr/obj/usr/src/amd64.amd64/sys/STING*** Error code 1Stop.make[1]: stopped in 
/usr/src*** Error code 1Stop.make: stopped in /usr/src[root@sting /usr/src]# 

[root@sting /usr/src]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT 
#57 heads/main-n250195-6ba2210ee03: Thu Oct 21 21:19:23 CEST 2021 
filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64 Filippo

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[Mateusz Guzik]

On 9/4/20, O. Hartmann  wrote:
> On Tue, 1 Sep 2020 19:21:36 +0200
> Mateusz Guzik  wrote:
>
>> It's not my bug but i'll make sure it is taken care of.
>
> Oh, I'm sorry. But I grasp for every help I can get ...
>
> The problem is that I do not know whether the process "make installkernel"
> does
> silently proceed and drop the error message and everything is fine or the
> fact
> that zfs.ko is the very last kernel module in the alphabetical order makes
> it
> by accident work. So, rebooting with an inconsistent /boot/kernel folder
> has
> revealed itself as a very unpleasant situation in the past.
>

markj got to this before I could. Can you please test the patch?

Index: sys/modules/zfs/Makefile
===
--- sys/modules/zfs/Makefile(revision 365318)
+++ sys/modules/zfs/Makefile(working copy)
@@ -44,8 +44,6 @@ CFLAGS+= -DDEBUG_VFS_LOCKS
 CFLAGS+=-fprofile-arcs -ftest-coverage
 .endif

-DEBUG_FLAGS=-g
-
 .if ${MACHINE_ARCH} == "i386" || ${MACHINE_ARCH} == "powerpc" || \
${MACHINE_ARCH} == "powerpcspe" || ${MACHINE_ARCH} == "arm"
 CFLAGS+= -DBITS_PER_LONG=32

>
>>
>> On 8/30/20, Hartmann, O.  wrote:
>> > On Fri, 28 Aug 2020 13:16:05 +0200
>> > Mateusz Guzik  wrote:
>> >
>> >> On 8/28/20, Hartmann, O.  wrote:
>> >> > On Fri, 28 Aug 2020 12:31:21 +0200
>> >> > Mateusz Guzik  wrote:
>> >> >
>> >> >> Can you show more of the log?
>> >> >>
>> >> >> When you installkernel you should see:
>> >> >> mkdir -p /boot/kernel
>> >> >> install -p -m 555 -o root -g wheel kernel /boot/kernel/
>> >> >
>> >> > These lines are seen right after the beginning of "make
>> >> > installkernel".
>> >> >> mkdir -p /usr/lib/debug/boot/kernel
>> >> >> install -p -m 555 -o root -g wheel kernel.debug
>> >> >> /usr/lib/debug/boot/kernel/
>> >> >
>> >> > I wouldn't expect these lines according to my /etc/src.conf, since I
>> >> > disbaled debugging and installing debugging infos.
>> >> >>
>> >> >> Did these succeed? Do these dirs exist now?
>> >> >
>> >> > It is not existent, as expected:
>> >> >
>> >> >
>> >> > # ll /usr/lib/debug/boot/kernel/
>> >> > ls: /usr/lib/debug/boot/kernel/: No such file or directory
>> >> >
>> >>
>> >> Ok. I recently made changes to the namecache, which if buggy, could
>> >> have resulted in woes like the above.
>> >>
>> >> Thus it looks like the newly imported zfs does not respect
>> >> WITHOUT_DEBUG_FILES.
>> >
>> > Even in r364973 the problem still remains.
>> > Disabling option WITHOUT_DEBUG_FILES in src.conf is exhausting the
>> > /usr/obj partition (using UFS/FFS) and no option.
>> >
>> > Got now several boxes having "make installkernel" issued with a running
>> > system but incomplete kernel installation, as buildkernel suggested a
>> > clean build. Can this be fixed, please?
>> >
>> >
>> >>
>> >> >>
>> >> >> On 8/28/20, Hartmann, O.  wrote:
>> >> >> > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25
>> >> >> > 16:10:50 CEST 2020 amd64), /usr/src at  revision 364907,
>> >> >> > installkernel fails now due to an error as shown below. For the
>> >> >> > record, "options ZFS" ist statically in the kernel config file.
>> >> >> >
>> >> >> > Also deleting /usr/obj and restarting buildworld and buildkernel
>> >> >> > from scratch doesn't solve the problem. The buildworld and
>> >> >> > buildkernel mutually finish without error (I do not see any on
>> >> >> > the console), installworld also finishes fine, but installkernel
>> >> >> > not.
>> >> >> >
>> >> >> > /etc/src.conf looks as follows:
>> >> >> >
>> >> >> > [...]
>> >> >> > CPUTYPE?=   native
>> >> >> > # World
>> >> >> > CFLAGS+=-O3
>> >> >> > #CFLAGS+=   -DNDEBUG
>> >> >> &

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[O. Hartmann]

On Tue, 1 Sep 2020 19:21:36 +0200
Mateusz Guzik  wrote:

> It's not my bug but i'll make sure it is taken care of.

Oh, I'm sorry. But I grasp for every help I can get ...

The problem is that I do not know whether the process "make installkernel" does
silently proceed and drop the error message and everything is fine or the fact
that zfs.ko is the very last kernel module in the alphabetical order makes it
by accident work. So, rebooting with an inconsistent /boot/kernel folder has
revealed itself as a very unpleasant situation in the past.

Thanks anyway for your concern.

Kind regards

Oliver

>
> On 8/30/20, Hartmann, O.  wrote:
> > On Fri, 28 Aug 2020 13:16:05 +0200
> > Mateusz Guzik  wrote:
> >
> >> On 8/28/20, Hartmann, O.  wrote:
> >> > On Fri, 28 Aug 2020 12:31:21 +0200
> >> > Mateusz Guzik  wrote:
> >> >
> >> >> Can you show more of the log?
> >> >>
> >> >> When you installkernel you should see:
> >> >> mkdir -p /boot/kernel
> >> >> install -p -m 555 -o root -g wheel kernel /boot/kernel/
> >> >
> >> > These lines are seen right after the beginning of "make
> >> > installkernel".
> >> >> mkdir -p /usr/lib/debug/boot/kernel
> >> >> install -p -m 555 -o root -g wheel kernel.debug
> >> >> /usr/lib/debug/boot/kernel/
> >> >
> >> > I wouldn't expect these lines according to my /etc/src.conf, since I
> >> > disbaled debugging and installing debugging infos.
> >> >>
> >> >> Did these succeed? Do these dirs exist now?
> >> >
> >> > It is not existent, as expected:
> >> >
> >> >
> >> > # ll /usr/lib/debug/boot/kernel/
> >> > ls: /usr/lib/debug/boot/kernel/: No such file or directory
> >> >
> >>
> >> Ok. I recently made changes to the namecache, which if buggy, could
> >> have resulted in woes like the above.
> >>
> >> Thus it looks like the newly imported zfs does not respect
> >> WITHOUT_DEBUG_FILES.
> >
> > Even in r364973 the problem still remains.
> > Disabling option WITHOUT_DEBUG_FILES in src.conf is exhausting the
> > /usr/obj partition (using UFS/FFS) and no option.
> >
> > Got now several boxes having "make installkernel" issued with a running
> > system but incomplete kernel installation, as buildkernel suggested a
> > clean build. Can this be fixed, please?
> >
> >
> >>
> >> >>
> >> >> On 8/28/20, Hartmann, O.  wrote:
> >> >> > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25
> >> >> > 16:10:50 CEST 2020 amd64), /usr/src at  revision 364907,
> >> >> > installkernel fails now due to an error as shown below. For the
> >> >> > record, "options ZFS" ist statically in the kernel config file.
> >> >> >
> >> >> > Also deleting /usr/obj and restarting buildworld and buildkernel
> >> >> > from scratch doesn't solve the problem. The buildworld and
> >> >> > buildkernel mutually finish without error (I do not see any on
> >> >> > the console), installworld also finishes fine, but installkernel
> >> >> > not.
> >> >> >
> >> >> > /etc/src.conf looks as follows:
> >> >> >
> >> >> > [...]
> >> >> > CPUTYPE?=   native
> >> >> > # World
> >> >> > CFLAGS+=-O3
> >> >> > #CFLAGS+=   -DNDEBUG
> >> >> > # Kernel
> >> >> > COPTFLAGS+= -O3
> >> >> > #COPTFLAGS+=-DNDEBUG
> >> >> > #CXXFLAGS+= -std=c++17
> >> >> > WITH_CLANG_EXTRAS=  YES
> >> >> > WITH_LLDB=  YES
> >> >> > #WITH_BSD_GREP= YES
> >> >> > WITH_OFED_EXTRA=YES
> >> >> > WITH_NAND=  YES
> >> >> > #WITH_CTF=  YES
> >> >> > WITH_SVN=   YES
> >> >> > WITH_BEARSSL=   YES
> >> >> > WITH_PIE=   YES
> >> >> > WITH_SORT_THREADS=  YES
> >&

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[Mateusz Guzik]

It's not my bug but i'll make sure it is taken care of.

On 8/30/20, Hartmann, O.  wrote:
> On Fri, 28 Aug 2020 13:16:05 +0200
> Mateusz Guzik  wrote:
>
>> On 8/28/20, Hartmann, O.  wrote:
>> > On Fri, 28 Aug 2020 12:31:21 +0200
>> > Mateusz Guzik  wrote:
>> >
>> >> Can you show more of the log?
>> >>
>> >> When you installkernel you should see:
>> >> mkdir -p /boot/kernel
>> >> install -p -m 555 -o root -g wheel kernel /boot/kernel/
>> >
>> > These lines are seen right after the beginning of "make
>> > installkernel".
>> >> mkdir -p /usr/lib/debug/boot/kernel
>> >> install -p -m 555 -o root -g wheel kernel.debug
>> >> /usr/lib/debug/boot/kernel/
>> >
>> > I wouldn't expect these lines according to my /etc/src.conf, since I
>> > disbaled debugging and installing debugging infos.
>> >>
>> >> Did these succeed? Do these dirs exist now?
>> >
>> > It is not existent, as expected:
>> >
>> >
>> > # ll /usr/lib/debug/boot/kernel/
>> > ls: /usr/lib/debug/boot/kernel/: No such file or directory
>> >
>>
>> Ok. I recently made changes to the namecache, which if buggy, could
>> have resulted in woes like the above.
>>
>> Thus it looks like the newly imported zfs does not respect
>> WITHOUT_DEBUG_FILES.
>
> Even in r364973 the problem still remains.
> Disabling option WITHOUT_DEBUG_FILES in src.conf is exhausting the
> /usr/obj partition (using UFS/FFS) and no option.
>
> Got now several boxes having "make installkernel" issued with a running
> system but incomplete kernel installation, as buildkernel suggested a
> clean build. Can this be fixed, please?
>
>
>>
>> >>
>> >> On 8/28/20, Hartmann, O.  wrote:
>> >> > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25
>> >> > 16:10:50 CEST 2020 amd64), /usr/src at  revision 364907,
>> >> > installkernel fails now due to an error as shown below. For the
>> >> > record, "options ZFS" ist statically in the kernel config file.
>> >> >
>> >> > Also deleting /usr/obj and restarting buildworld and buildkernel
>> >> > from scratch doesn't solve the problem. The buildworld and
>> >> > buildkernel mutually finish without error (I do not see any on
>> >> > the console), installworld also finishes fine, but installkernel
>> >> > not.
>> >> >
>> >> > /etc/src.conf looks as follows:
>> >> >
>> >> > [...]
>> >> > CPUTYPE?=   native
>> >> > # World
>> >> > CFLAGS+=-O3
>> >> > #CFLAGS+=   -DNDEBUG
>> >> > # Kernel
>> >> > COPTFLAGS+= -O3
>> >> > #COPTFLAGS+=-DNDEBUG
>> >> > #CXXFLAGS+= -std=c++17
>> >> > WITH_CLANG_EXTRAS=  YES
>> >> > WITH_LLDB=  YES
>> >> > #WITH_BSD_GREP= YES
>> >> > WITH_OFED_EXTRA=YES
>> >> > WITH_NAND=  YES
>> >> > #WITH_CTF=  YES
>> >> > WITH_SVN=   YES
>> >> > WITH_BEARSSL=   YES
>> >> > WITH_PIE=   YES
>> >> > WITH_SORT_THREADS=  YES
>> >> > WITH_ZONEINFO_LEAPSECONDS_SUPPORT=  YES
>> >> > MALLOC_PRODUCTION=  YES
>> >> > WITHOUT_ASSERT_DEBUG=   YES
>> >> > WITHOUT_TESTS=  YES
>> >> > WITHOUT_PROFILE=YES
>> >> > WITHOUT_DEBUG_FILES=YES
>> >> > WITHOUT_REPRODUCIBLE_BUILD= YES
>> >> >
>> >> > [...]
>> >> >
>> >> > Debugging facilities are disabled as src.conf indicates.
>> >> >
>> >> > [...]
>> >> > install -T release -o root -g wheel -m 555   xz.ko
>> >> > /boot/kernel/ ===> zfs (install)
>> >> > install -T release -o root -g wheel -m 555   zfs.ko /boot/kernel/
>> >> > install -T dbg -o root -g wheel -m 555   zfs.ko.debug
>> >> >   /usr/lib/debug/boot/kernel/
>> >> > install: /usr/lib/debug/boot/kernel/: No such file or directory
>> >> > *** Error code 71
>> >> >
>> >> > Stop.
>> >> > make[4]: stopped in /usr/src/sys/modules/zfs
>> >> > *** Error code 1
>> >> > *** Error code 1
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>


-- 
Mateusz Guzik 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[Hartmann, O.]

On Fri, 28 Aug 2020 13:16:05 +0200
Mateusz Guzik  wrote:

> On 8/28/20, Hartmann, O.  wrote:
> > On Fri, 28 Aug 2020 12:31:21 +0200
> > Mateusz Guzik  wrote:
> >  
> >> Can you show more of the log?
> >>
> >> When you installkernel you should see:
> >> mkdir -p /boot/kernel
> >> install -p -m 555 -o root -g wheel kernel /boot/kernel/  
> >
> > These lines are seen right after the beginning of "make
> > installkernel". 
> >> mkdir -p /usr/lib/debug/boot/kernel
> >> install -p -m 555 -o root -g wheel kernel.debug
> >> /usr/lib/debug/boot/kernel/  
> >
> > I wouldn't expect these lines according to my /etc/src.conf, since I
> > disbaled debugging and installing debugging infos.  
> >>
> >> Did these succeed? Do these dirs exist now?  
> >
> > It is not existent, as expected:
> >
> >
> > # ll /usr/lib/debug/boot/kernel/
> > ls: /usr/lib/debug/boot/kernel/: No such file or directory
> >  
> 
> Ok. I recently made changes to the namecache, which if buggy, could
> have resulted in woes like the above.
> 
> Thus it looks like the newly imported zfs does not respect
> WITHOUT_DEBUG_FILES.

Even in r364973 the problem still remains.
Disabling option WITHOUT_DEBUG_FILES in src.conf is exhausting the
/usr/obj partition (using UFS/FFS) and no option.

Got now several boxes having "make installkernel" issued with a running
system but incomplete kernel installation, as buildkernel suggested a
clean build. Can this be fixed, please?

 
> 
> >>
> >> On 8/28/20, Hartmann, O.  wrote:  
> >> > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25
> >> > 16:10:50 CEST 2020 amd64), /usr/src at  revision 364907,
> >> > installkernel fails now due to an error as shown below. For the
> >> > record, "options ZFS" ist statically in the kernel config file.
> >> >
> >> > Also deleting /usr/obj and restarting buildworld and buildkernel
> >> > from scratch doesn't solve the problem. The buildworld and
> >> > buildkernel mutually finish without error (I do not see any on
> >> > the console), installworld also finishes fine, but installkernel
> >> > not.
> >> >
> >> > /etc/src.conf looks as follows:
> >> >
> >> > [...]
> >> > CPUTYPE?=   native
> >> > # World
> >> > CFLAGS+=-O3
> >> > #CFLAGS+=   -DNDEBUG
> >> > # Kernel
> >> > COPTFLAGS+= -O3
> >> > #COPTFLAGS+=-DNDEBUG
> >> > #CXXFLAGS+= -std=c++17
> >> > WITH_CLANG_EXTRAS=  YES
> >> > WITH_LLDB=  YES
> >> > #WITH_BSD_GREP= YES
> >> > WITH_OFED_EXTRA=YES
> >> > WITH_NAND=  YES
> >> > #WITH_CTF=  YES
> >> > WITH_SVN=   YES
> >> > WITH_BEARSSL=   YES
> >> > WITH_PIE=   YES
> >> > WITH_SORT_THREADS=  YES
> >> > WITH_ZONEINFO_LEAPSECONDS_SUPPORT=  YES
> >> > MALLOC_PRODUCTION=  YES
> >> > WITHOUT_ASSERT_DEBUG=   YES
> >> > WITHOUT_TESTS=  YES
> >> > WITHOUT_PROFILE=YES
> >> > WITHOUT_DEBUG_FILES=YES
> >> > WITHOUT_REPRODUCIBLE_BUILD= YES
> >> >
> >> > [...]
> >> >
> >> > Debugging facilities are disabled as src.conf indicates.
> >> >
> >> > [...]
> >> > install -T release -o root -g wheel -m 555   xz.ko
> >> > /boot/kernel/ ===> zfs (install)
> >> > install -T release -o root -g wheel -m 555   zfs.ko /boot/kernel/
> >> > install -T dbg -o root -g wheel -m 555   zfs.ko.debug
> >> >   /usr/lib/debug/boot/kernel/
> >> > install: /usr/lib/debug/boot/kernel/: No such file or directory
> >> > *** Error code 71
> >> >
> >> > Stop.
> >> > make[4]: stopped in /usr/src/sys/modules/zfs
> >> > *** Error code 1
> >> > *** Error code 1
> >> >  
> >>
> >>  
> >
> >  
> 
> 



pgp9ygOHkxprd.pgp
Description: OpenPGP digital signature

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[Mateusz Guzik]

On 8/28/20, Hartmann, O.  wrote:
> On Fri, 28 Aug 2020 12:31:21 +0200
> Mateusz Guzik  wrote:
>
>> Can you show more of the log?
>>
>> When you installkernel you should see:
>> mkdir -p /boot/kernel
>> install -p -m 555 -o root -g wheel kernel /boot/kernel/
>
> These lines are seen right after the beginning of "make installkernel".
>
>> mkdir -p /usr/lib/debug/boot/kernel
>> install -p -m 555 -o root -g wheel kernel.debug
>> /usr/lib/debug/boot/kernel/
>
> I wouldn't expect these lines according to my /etc/src.conf, since I
> disbaled debugging and installing debugging infos.
>>
>> Did these succeed? Do these dirs exist now?
>
> It is not existent, as expected:
>
>
> # ll /usr/lib/debug/boot/kernel/
> ls: /usr/lib/debug/boot/kernel/: No such file or directory
>

Ok. I recently made changes to the namecache, which if buggy, could
have resulted in woes like the above.

Thus it looks like the newly imported zfs does not respect WITHOUT_DEBUG_FILES.

>>
>> On 8/28/20, Hartmann, O.  wrote:
>> > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 16:10:50
>> > CEST 2020 amd64), /usr/src at  revision 364907, installkernel fails
>> > now due to an error as shown below. For the record, "options ZFS"
>> > ist statically in the kernel config file.
>> >
>> > Also deleting /usr/obj and restarting buildworld and buildkernel
>> > from scratch doesn't solve the problem. The buildworld and
>> > buildkernel mutually finish without error (I do not see any on the
>> > console), installworld also finishes fine, but installkernel not.
>> >
>> > /etc/src.conf looks as follows:
>> >
>> > [...]
>> > CPUTYPE?=   native
>> > # World
>> > CFLAGS+=-O3
>> > #CFLAGS+=   -DNDEBUG
>> > # Kernel
>> > COPTFLAGS+= -O3
>> > #COPTFLAGS+=-DNDEBUG
>> > #CXXFLAGS+= -std=c++17
>> > WITH_CLANG_EXTRAS=  YES
>> > WITH_LLDB=  YES
>> > #WITH_BSD_GREP= YES
>> > WITH_OFED_EXTRA=YES
>> > WITH_NAND=  YES
>> > #WITH_CTF=  YES
>> > WITH_SVN=   YES
>> > WITH_BEARSSL=   YES
>> > WITH_PIE=   YES
>> > WITH_SORT_THREADS=  YES
>> > WITH_ZONEINFO_LEAPSECONDS_SUPPORT=  YES
>> > MALLOC_PRODUCTION=  YES
>> > WITHOUT_ASSERT_DEBUG=   YES
>> > WITHOUT_TESTS=  YES
>> > WITHOUT_PROFILE=YES
>> > WITHOUT_DEBUG_FILES=YES
>> > WITHOUT_REPRODUCIBLE_BUILD= YES
>> >
>> > [...]
>> >
>> > Debugging facilities are disabled as src.conf indicates.
>> >
>> > [...]
>> > install -T release -o root -g wheel -m 555   xz.ko
>> > /boot/kernel/ ===> zfs (install)
>> > install -T release -o root -g wheel -m 555   zfs.ko /boot/kernel/
>> > install -T dbg -o root -g wheel -m 555   zfs.ko.debug
>> >   /usr/lib/debug/boot/kernel/
>> > install: /usr/lib/debug/boot/kernel/: No such file or directory ***
>> >Error code 71
>> >
>> > Stop.
>> > make[4]: stopped in /usr/src/sys/modules/zfs
>> > *** Error code 1
>> > *** Error code 1
>> >
>>
>>
>
>


-- 
Mateusz Guzik 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[Hartmann, O.]

On Fri, 28 Aug 2020 12:31:21 +0200
Mateusz Guzik  wrote:

> Can you show more of the log?
> 
> When you installkernel you should see:
> mkdir -p /boot/kernel
> install -p -m 555 -o root -g wheel kernel /boot/kernel/

These lines are seen right after the beginning of "make installkernel".

> mkdir -p /usr/lib/debug/boot/kernel
> install -p -m 555 -o root -g wheel kernel.debug
> /usr/lib/debug/boot/kernel/

I wouldn't expect these lines according to my /etc/src.conf, since I
disbaled debugging and installing debugging infos.
> 
> Did these succeed? Do these dirs exist now?

It is not existent, as expected:


# ll /usr/lib/debug/boot/kernel/
ls: /usr/lib/debug/boot/kernel/: No such file or directory

> 
> On 8/28/20, Hartmann, O.  wrote:
> > On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 16:10:50
> > CEST 2020 amd64), /usr/src at  revision 364907, installkernel fails
> > now due to an error as shown below. For the record, "options ZFS"
> > ist statically in the kernel config file.
> >
> > Also deleting /usr/obj and restarting buildworld and buildkernel
> > from scratch doesn't solve the problem. The buildworld and
> > buildkernel mutually finish without error (I do not see any on the
> > console), installworld also finishes fine, but installkernel not.
> >
> > /etc/src.conf looks as follows:
> >
> > [...]
> > CPUTYPE?=   native
> > # World
> > CFLAGS+=-O3
> > #CFLAGS+=   -DNDEBUG
> > # Kernel
> > COPTFLAGS+= -O3
> > #COPTFLAGS+=-DNDEBUG
> > #CXXFLAGS+= -std=c++17
> > WITH_CLANG_EXTRAS=  YES
> > WITH_LLDB=  YES
> > #WITH_BSD_GREP= YES
> > WITH_OFED_EXTRA=YES
> > WITH_NAND=  YES
> > #WITH_CTF=  YES
> > WITH_SVN=   YES
> > WITH_BEARSSL=   YES
> > WITH_PIE=   YES
> > WITH_SORT_THREADS=  YES
> > WITH_ZONEINFO_LEAPSECONDS_SUPPORT=  YES
> > MALLOC_PRODUCTION=  YES
> > WITHOUT_ASSERT_DEBUG=   YES
> > WITHOUT_TESTS=  YES
> > WITHOUT_PROFILE=YES
> > WITHOUT_DEBUG_FILES=YES
> > WITHOUT_REPRODUCIBLE_BUILD= YES
> >
> > [...]
> >
> > Debugging facilities are disabled as src.conf indicates.
> >
> > [...]
> > install -T release -o root -g wheel -m 555   xz.ko
> > /boot/kernel/ ===> zfs (install)
> > install -T release -o root -g wheel -m 555   zfs.ko /boot/kernel/
> > install -T dbg -o root -g wheel -m 555   zfs.ko.debug
> >   /usr/lib/debug/boot/kernel/
> > install: /usr/lib/debug/boot/kernel/: No such file or directory ***
> >Error code 71
> >
> > Stop.
> > make[4]: stopped in /usr/src/sys/modules/zfs
> > *** Error code 1
> > *** Error code 1
> >  
> 
> 



pgpSBCEFhC_XL.pgp
Description: OpenPGP digital signature

Re: installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[Mateusz Guzik]

Can you show more of the log?

When you installkernel you should see:
mkdir -p /boot/kernel
install -p -m 555 -o root -g wheel kernel /boot/kernel/
mkdir -p /usr/lib/debug/boot/kernel
install -p -m 555 -o root -g wheel kernel.debug /usr/lib/debug/boot/kernel/

Did these succeed? Do these dirs exist now?

On 8/28/20, Hartmann, O.  wrote:
> On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 16:10:50 CEST
> 2020 amd64), /usr/src at  revision 364907, installkernel fails now due
> to an error as shown below. For the record, "options ZFS" ist
> statically in the kernel config file.
>
> Also deleting /usr/obj and restarting buildworld and buildkernel from
> scratch doesn't solve the problem. The buildworld and buildkernel
> mutually finish without error (I do not see any on the console),
> installworld also finishes fine, but installkernel not.
>
> /etc/src.conf looks as follows:
>
> [...]
> CPUTYPE?=   native
> # World
> CFLAGS+=-O3
> #CFLAGS+=   -DNDEBUG
> # Kernel
> COPTFLAGS+= -O3
> #COPTFLAGS+=-DNDEBUG
> #CXXFLAGS+= -std=c++17
> WITH_CLANG_EXTRAS=  YES
> WITH_LLDB=  YES
> #WITH_BSD_GREP= YES
> WITH_OFED_EXTRA=YES
> WITH_NAND=  YES
> #WITH_CTF=  YES
> WITH_SVN=   YES
> WITH_BEARSSL=   YES
> WITH_PIE=   YES
> WITH_SORT_THREADS=  YES
> WITH_ZONEINFO_LEAPSECONDS_SUPPORT=  YES
> MALLOC_PRODUCTION=  YES
> WITHOUT_ASSERT_DEBUG=   YES
> WITHOUT_TESTS=  YES
> WITHOUT_PROFILE=YES
> WITHOUT_DEBUG_FILES=YES
> WITHOUT_REPRODUCIBLE_BUILD= YES
>
> [...]
>
> Debugging facilities are disabled as src.conf indicates.
>
> [...]
> install -T release -o root -g wheel -m 555   xz.ko
> /boot/kernel/ ===> zfs (install)
> install -T release -o root -g wheel -m 555   zfs.ko /boot/kernel/
> install -T dbg -o root -g wheel -m 555   zfs.ko.debug
>   /usr/lib/debug/boot/kernel/
> install: /usr/lib/debug/boot/kernel/: No such file or directory ***
>Error code 71
>
> Stop.
> make[4]: stopped in /usr/src/sys/modules/zfs
> *** Error code 1
> *** Error code 1
>


-- 
Mateusz Guzik 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

installkernel: install: /usr/lib/debug/boot/kernel/: No such file or directory *** Error code 71

[Hartmann, O.]

On CURRENT (FreeBSD 13.0-CURRENT #185 r364767: Tue Aug 25 16:10:50 CEST
2020 amd64), /usr/src at  revision 364907, installkernel fails now due
to an error as shown below. For the record, "options ZFS" ist
statically in the kernel config file.

Also deleting /usr/obj and restarting buildworld and buildkernel from
scratch doesn't solve the problem. The buildworld and buildkernel
mutually finish without error (I do not see any on the console),
installworld also finishes fine, but installkernel not.

/etc/src.conf looks as follows:

[...]
CPUTYPE?=   native
# World
CFLAGS+=-O3
#CFLAGS+=   -DNDEBUG
# Kernel
COPTFLAGS+= -O3
#COPTFLAGS+=-DNDEBUG
#CXXFLAGS+= -std=c++17
WITH_CLANG_EXTRAS=  YES
WITH_LLDB=  YES
#WITH_BSD_GREP= YES
WITH_OFED_EXTRA=YES
WITH_NAND=  YES
#WITH_CTF=  YES
WITH_SVN=   YES
WITH_BEARSSL=   YES
WITH_PIE=   YES
WITH_SORT_THREADS=  YES
WITH_ZONEINFO_LEAPSECONDS_SUPPORT=  YES
MALLOC_PRODUCTION=  YES
WITHOUT_ASSERT_DEBUG=   YES
WITHOUT_TESTS=  YES
WITHOUT_PROFILE=YES
WITHOUT_DEBUG_FILES=YES
WITHOUT_REPRODUCIBLE_BUILD= YES

[...]

Debugging facilities are disabled as src.conf indicates.

[...]
install -T release -o root -g wheel -m 555   xz.ko
/boot/kernel/ ===> zfs (install)
install -T release -o root -g wheel -m 555   zfs.ko /boot/kernel/
install -T dbg -o root -g wheel -m 555   zfs.ko.debug
  /usr/lib/debug/boot/kernel/ 
install: /usr/lib/debug/boot/kernel/: No such file or directory ***
   Error code 71

Stop.
make[4]: stopped in /usr/src/sys/modules/zfs
*** Error code 1
*** Error code 1


pgpKHQqTUBRFE.pgp
Description: OpenPGP digital signature

Re: installkernel ignoring WITHOUT_DEBUG_FILES?

[Yuri Pankov]

Mark Johnston wrote:

On Wed, Apr 29, 2020 at 08:49:00AM +0300, Yuri Pankov wrote:

I'm trying to replace the kernel on memstick image with the help of
mdconfig, and installkernel runs out of space despite
WITHOUT_DEBUG_FILES= added to /etc/src.conf.

/usr/src$ make -V MK_DEBUG_FILES
no
/usr/src$ sudo rm -rf /mnt/usr/lib/debug
/usr/src$ sudo make DESTDIR=/mnt installkernel


You need WITHOUT_KERNEL_SYMBOLS= instead for the kernel.  I'm not sure
why it's a different option.


Thank you, somehow I missed it, and its description is a bit misleading 
as well.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: installkernel ignoring WITHOUT_DEBUG_FILES?

[Mark Johnston]

On Wed, Apr 29, 2020 at 08:49:00AM +0300, Yuri Pankov wrote:
> I'm trying to replace the kernel on memstick image with the help of 
> mdconfig, and installkernel runs out of space despite 
> WITHOUT_DEBUG_FILES= added to /etc/src.conf.
> 
> /usr/src$ make -V MK_DEBUG_FILES
> no
> /usr/src$ sudo rm -rf /mnt/usr/lib/debug
> /usr/src$ sudo make DESTDIR=/mnt installkernel

You need WITHOUT_KERNEL_SYMBOLS= instead for the kernel.  I'm not sure
why it's a different option.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

installkernel ignoring WITHOUT_DEBUG_FILES?

[Yuri Pankov]

I'm trying to replace the kernel on memstick image with the help of 
mdconfig, and installkernel runs out of space despite 
WITHOUT_DEBUG_FILES= added to /etc/src.conf.


/usr/src$ make -V MK_DEBUG_FILES
no
/usr/src$ sudo rm -rf /mnt/usr/lib/debug
/usr/src$ sudo make DESTDIR=/mnt installkernel
--
>>> Install check kernel
--
--
>>> Installing kernel GENERIC on Wed Apr 29 08:43:19 MSK 2020
--
cd /usr/obj/usr/src/amd64.amd64/sys/GENERIC;  MACHINE_ARCH=amd64 
MACHINE=amd64  CPUTYPE= CC="cc -target x86_64-unknown-freebsd13.0 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin" CXX="c++  -target 
x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  CPP="cpp -target 
x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin"  AS="as" AR="ar" LD="ld" 
LLVM_LINK=""  NM=nm OBJCOPY="objcopy"  RANLIB=ranlib STRINGS= 
SIZE="size" 
PATH=/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin 
make  KERNEL=kernel install thiskernel=`sysctl -n kern.bootfile` ;  if [ 
! "`dirname "$thiskernel"`" -ef /mnt/boot/kernel ] ; then  chflags
-R noschg /mnt/boot/kernel ;  rm -rf /mnt/boot/kernel ;  rm -rf 
/mnt/usr/lib/debug/boot/kernel ;  else  if [ -d /mnt/boot/kernel.old ] ; 
then  chflags -R noschg /mnt/boot/kernel.old ;  rm -rf 
/mnt/boot/kernel.old ;  fi ;  mv /mnt/boot/kernel /mnt/boot/kernel.old ; 
 if [ -n "/usr/lib/debug" -a  -d /mnt/usr/lib/debug/boot/kernel ]; then 
rm -rf /mnt/usr/lib/debug/boot/kernel.old ;  mv 
/mnt/usr/lib/debug/boot/kernel /mnt/usr/lib/debug/boot/kernel.old ;  fi 
;  sysctl kern.bootfile=/mnt/boot/kernel.old/"`basename "$thiskernel"`" 
;  fi

mkdir -p /mnt/boot/kernel
install -p -m 555 -o root -g wheel kernel /mnt/boot/kernel/
mkdir -p /mnt/usr/lib/debug/boot/kernel
install -p -m 555 -o root -g wheel kernel.debug 
/mnt/usr/lib/debug/boot/kernel/
cd /usr/src/sys/modules; 
MAKEOBJDIRPREFIX=/usr/obj/usr/src/amd64.amd64/sys/GENERIC/modules 
KMODDIR=/boot/kernel MACHINE_CPUARCH=amd64 MACHINE=amd64 
MACHINE_ARCH=amd64 MODULES_EXTRA="" WITHOUT_MODULES="" ARCH_FLAGS="" 
DEBUG_FLAGS="-g" __MPATH="" DESTDIR="/mnt" 
KERNBUILDDIR="/usr/obj/usr/src/amd64.amd64/sys/GENERIC" 
SYSDIR="/usr/src/sys" MODULE_TIED=yes WITH_CTF="1" KCSAN_ENABLED="yes" 
make  install

===> aac (install)
install -T release -o root -g wheel -m 555   aac.ko /mnt/boot/kernel/
install -T debug -o root -g wheel -m 555   aac.ko.debug 
/mnt/usr/lib/debug/boot/kernel/

...
===> dummynet (install)
install -T release -o root -g wheel -m 555   dummynet.ko /mnt/boot/kernel/

/mnt: write failed, filesystem is full
install: /mnt/boot/kernel/dummynet.ko: No space left on device
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: impossible to installkernel without a compiler?

[Warner Losh]

There's already a list of targets to except... It's hard to have an opt-in
list, however :(

Warner

On Wed, May 29, 2019 at 4:26 AM Andriy Gapon  wrote:

>
> Just want to note that the problem extends to doing such things as "make
> aliases" in /etc/mail on a system installed without a compiler.
>
> I guess it would be nice if COMPILER_TYPE was enforced only when a
> compiler is
> actually needed.  make can be used for more things than building C code.
>
>
> --
> Andriy Gapon
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: impossible to installkernel without a compiler?

[Andriy Gapon]

Just want to note that the problem extends to doing such things as "make
aliases" in /etc/mail on a system installed without a compiler.

I guess it would be nice if COMPILER_TYPE was enforced only when a compiler is
actually needed.  make can be used for more things than building C code.


-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: impossible to installkernel without a compiler?

[Andriy Gapon]

On 22/05/2019 16:37, Warner Losh wrote:
> Try setting _NO_INCLUDE_COMPILERMK=t in your environment and then doing the 
> make
> install.

This works a bit worse than my original hack:

sh: ld: not found
make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 58: warning: Unable
to determine linker type from LD=ld
make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 71: warning: Unknown
linker from LD=ld: none, defaulting to bfd
--
>>> Install check kernel
--
--
>>> Installing kernel KERNEL on Wed May 22 14:43:41 UTC 2019
--
make[2]: "/usr/devel/svn/head/sys/conf/kern.pre.mk" line 157: Malformed
conditional (${LINKER_TYPE} != "lld")
make[2]: Fatal errors encountered -- cannot continue


> On Wed, May 22, 2019 at 2:09 AM Andriy Gapon  <mailto:a...@freebsd.org>> wrote:
> 
> 
> Trying to update a small system with a kernel built for it on a bigger 
> machine I
> get this:
> 
> sh: cc: not found
> make: "/usr/devel/svn/head/share/mk/bsd.compiler.mk
> <http://bsd.compiler.mk>" line 176: Unable to
> determine compiler type for CC=cc.  Consider setting COMPILER_TYPE.
> 
> Sources and objects are mounted over NFS, all configuration knobs match.
> Just adding COMPILER_TYPE=gcc to the command line allows the installation 
> to
> succeed with a little bit of noise:
> 
> sh: cc: not found
> sh: ld: not found
> make: "/usr/devel/svn/head/share/mk/bsd.linker.mk <http://bsd.linker.mk>"
> line 58: warning: Unable to
> determine linker type from LD=ld
> make: "/usr/devel/svn/head/share/mk/bsd.linker.mk <http://bsd.linker.mk>"
> line 71: warning: Unknown
> linker from LD=ld: none, defaulting to bfd
> sh: cc: not found
> sh: ld: not found
> make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk 
> <http://bsd.linker.mk>"
> line 58: warning: Unable
> to determine linker type from LD=ld
> make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk 
> <http://bsd.linker.mk>"
> line 71: warning: Unknown
> linker from LD=ld: none, defaulting to bfd
> sh: cc: not found
> sh: cc: not found
> --
> >>> Install check kernel
> --
> --
> >>> Installing kernel KERNEL on Wed May 22 08:00:33 UTC 2019
> ------
> ...
> --
> >>> Installing kernel KERNEL completed on Wed May 22 08:00:42 UTC 2019
> --
> 
> I think that installkernel should not care about cc (and ld) at all.
> 
> -- 
> Andriy Gapon
> ___
> freebsd-current@freebsd.org <mailto:freebsd-current@freebsd.org> mailing 
> list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org
> <mailto:freebsd-current-unsubscr...@freebsd.org>"
> 


-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: impossible to installkernel without a compiler?

[Warner Losh]

Try setting _NO_INCLUDE_COMPILERMK=t in your environment and then doing the
make install.

Warner

On Wed, May 22, 2019 at 2:09 AM Andriy Gapon  wrote:

>
> Trying to update a small system with a kernel built for it on a bigger
> machine I
> get this:
>
> sh: cc: not found
> make: "/usr/devel/svn/head/share/mk/bsd.compiler.mk" line 176: Unable to
> determine compiler type for CC=cc.  Consider setting COMPILER_TYPE.
>
> Sources and objects are mounted over NFS, all configuration knobs match.
> Just adding COMPILER_TYPE=gcc to the command line allows the installation
> to
> succeed with a little bit of noise:
>
> sh: cc: not found
> sh: ld: not found
> make: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 58: warning:
> Unable to
> determine linker type from LD=ld
> make: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 71: warning:
> Unknown
> linker from LD=ld: none, defaulting to bfd
> sh: cc: not found
> sh: ld: not found
> make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 58: warning:
> Unable
> to determine linker type from LD=ld
> make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 71: warning:
> Unknown
> linker from LD=ld: none, defaulting to bfd
> sh: cc: not found
> sh: cc: not found
> --
> >>> Install check kernel
> --
> --
> >>> Installing kernel KERNEL on Wed May 22 08:00:33 UTC 2019
> --
> ...
> ------
> >>> Installing kernel KERNEL completed on Wed May 22 08:00:42 UTC 2019
> --
>
> I think that installkernel should not care about cc (and ld) at all.
>
> --
> Andriy Gapon
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

impossible to installkernel without a compiler?

[Andriy Gapon]

Trying to update a small system with a kernel built for it on a bigger machine I
get this:

sh: cc: not found
make: "/usr/devel/svn/head/share/mk/bsd.compiler.mk" line 176: Unable to
determine compiler type for CC=cc.  Consider setting COMPILER_TYPE.

Sources and objects are mounted over NFS, all configuration knobs match.
Just adding COMPILER_TYPE=gcc to the command line allows the installation to
succeed with a little bit of noise:

sh: cc: not found
sh: ld: not found
make: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 58: warning: Unable to
determine linker type from LD=ld
make: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 71: warning: Unknown
linker from LD=ld: none, defaulting to bfd
sh: cc: not found
sh: ld: not found
make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 58: warning: Unable
to determine linker type from LD=ld
make[1]: "/usr/devel/svn/head/share/mk/bsd.linker.mk" line 71: warning: Unknown
linker from LD=ld: none, defaulting to bfd
sh: cc: not found
sh: cc: not found
--
>>> Install check kernel
--
--
>>> Installing kernel KERNEL on Wed May 22 08:00:33 UTC 2019
--
...
--
>>> Installing kernel KERNEL completed on Wed May 22 08:00:42 UTC 2019
--

I think that installkernel should not care about cc (and ld) at all.

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Fatal trap 9 when rebooting after installkernel on VirtualBox VM

[Yasuhiro KIMURA]

From: Yasuhiro KIMURA 
Subject: Fatal trap 9 when rebooting after installkernel on VirtualBox VM
Date: Sun, 02 Sep 2018 23:51:45 +0900 (JST)

> I'm tracking head with VirtualBox VM. Everytime new snapshot is
> released I update to same revision. So buildworld, buildkernel and
> installkernel always completes sucsessfully. But when rebooting system
> always crashes with 'Fatal trap 9: general protection fault while in
> kernel mode' message. And I closed VM window and restart VM, new
> kernel start up without any problem.
> https://www.utahime.org/FreeBSD/VirtualBox_FreeBSD_12.0-ALPHA3.png
> This is a screenshot of latest update (ALPHA3 -> ALPHA4).
> Does anyone else experienced it?

I submitted this problem to bugzilla.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231430

Screenshots when updateing to ALPHA5, ALPHA6 and ALPHA7 are also
attached. According to the advice of Mark Johnston (ma...@freebsd.org)
they include output of 'bt' command.

Just FYI.

---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Fatal trap 9 when rebooting after installkernel on VirtualBox VM

[Yasuhiro KIMURA]

Hello.

I'm tracking head with VirtualBox VM. Everytime new snapshot is
released I update to same revision. So buildworld, buildkernel and
installkernel always completes sucsessfully. But when rebooting system
always crashes with 'Fatal trap 9: general protection fault while in
kernel mode' message. And I closed VM window and restart VM, new
kernel start up without any problem.

https://www.utahime.org/FreeBSD/VirtualBox_FreeBSD_12.0-ALPHA3.png

This is a screenshot of latest update (ALPHA3 -> ALPHA4).

Does anyone else experienced it?

Conditions about VM and host are following:

VM:
  CPU: x4
  Memory: 8GB
  Disk: 100GB SATA
Host:
  CPU: Intel Core i7 4770S
  Memory: 16GB
  Disk: 2TB SATA
  OS: 64bit Windows 10 Enterprise 1803

Best Regards.

---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

r334236 error installkernel (i386)

[Alex V. Petrov]

===> usb/muge (install)
install -T release -o root -g wheel -m 555   if_muge.ko /boot/kernel/
install: if_muge.ko: No such file or directory
*** Error code 71

Stop.
make[5]: stopped in /usr/src/sys/modules/usb/muge
*** Error code 1

Stop.
make[4]: stopped in /usr/src/sys/modules/usb
*** Error code 1

Stop.
make[3]: stopped in /usr/src/sys/modules
*** Error code 1

Stop.
make[2]: stopped in /usr/obj/usr/src/i386.i386/sys/ALEX
*** Error code 1

Stop.
make[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src


kernel:
include GENERIC-NODEBUG
ident   ALEX


-- 
-
Alex.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

installkernel error WITHOUT_BLUETOOTH

[James Wright]

Hi,

   Just ran into this issue when trying to "make installkernel" after 
adding the "WITHOUT_BLUETOOTH" flag to my "/etc/src.conf" (see snippet 
below). Is this expected behaviour? Do I need to add "WITHOUT_NETGRAPH" 
also?


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

install -T release -o root -g wheel -m 555   ng_atmllc.ko /boot/kernel/
install -T debug -o root -g wheel -m 555   ng_atmllc.ko.debug 
/usr/lib/debug/boot/kernel/

===> netgraph/bluetooth (install)
===> netgraph/bluetooth/bluetooth (install)
install -T release -o root -g wheel -m 555   ng_bluetooth.ko /boot/kernel/
install: ng_bluetooth.ko: No such file or directory
*** Error code 71

Stop.
make[6]: stopped in /usr/src/sys/modules/netgraph/bluetooth/bluetooth
*** Error code 1

Stop.
make[5]: stopped in /usr/src/sys/modules/netgraph/bluetooth
*** Error code 1

Stop.
make[4]: stopped in /usr/src/sys/modules/netgraph
*** Error code 1

Stop.
make[3]: stopped in /usr/src/sys/modules
*** Error code 1

Stop.
make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC
*** Error code 1

Stop.
make[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Thanks,
James



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Missing in action during arm64/aarch64 builds: no pine64_plus.dtb to be found from buildkernel, installkernel, or u-boot-pine64

[Emmanuel Vadot]

On Sat, 9 Sep 2017 16:35:11 -0700
Mark Millard <mar...@dsl-only.net> wrote:

> The context here is head -r323246 amd64 -> arm64/aarch64
> cross build activity.
> 
> From installkernel :
> 
> # find /usr/obj/DESTDIRs/clang-cortexA53-installkernel/ -name "*.dtb" -print
> # 
> 
> From buildkernel :
> 
> # find /usr/obj/cortexA53_clang/arm64.aarch64/ -name "*.dtb" -print
> # 
> 
> From installing u-boot-pine64 :
> 
> # ls -lTd /usr/local/share/u-boot/u-boot-pine64/*
> -rw-r--r--  1 root  wheel 125 Sep  6 00:49:44 2017 
> /usr/local/share/u-boot/u-boot-pine64/README
> -rw-r--r--  1 root  wheel  505940 Sep  6 00:49:43 2017 
> /usr/local/share/u-boot/u-boot-pine64/u-boot-sunxi-with-spl.bin
> 
> 
> As stands the file must be manually produced.

 Since the latest update of u-boot-pine64 the dtb is included in u-boot.
 U-Boot loads it and pass it to boot1.efi.

> crochet goes to the trouble to have logic to
> build and install pine64_plus.dtb (based on
> arm64/pine64_plus.dts ).
> 
> Is pine64_plus.dtb required for the likes of
> Pine64+ 2GB's? If yes: should it be automatically
> built and installed someplace for arm64/aarch64
> builds (even if more manual steps are required to
> have the final placement on the Pine64 media)?
> 
> 
> ===
> Mark Millard
> markmi at  dsl-only.net
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


-- 
Emmanuel Vadot <m...@bidouilliste.com> <m...@freebsd.org>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Missing in action during arm64/aarch64 builds: no pine64_plus.dtb to be found from buildkernel, installkernel, or u-boot-pine64

[Mark Millard]

On 2017-Sep-11, at 12:56 AM, Emmanuel Vadot  wrote:

> On Sat, 9 Sep 2017 16:35:11 -0700
> Mark Millard  wrote:
> 
>> The context here is head -r323246 amd64 -> arm64/aarch64
>> cross build activity.
>> 
>> From installkernel :
>> 
>> # find /usr/obj/DESTDIRs/clang-cortexA53-installkernel/ -name "*.dtb" -print
>> # 
>> 
>> From buildkernel :
>> 
>> # find /usr/obj/cortexA53_clang/arm64.aarch64/ -name "*.dtb" -print
>> # 
>> 
>> From installing u-boot-pine64 :
>> 
>> # ls -lTd /usr/local/share/u-boot/u-boot-pine64/*
>> -rw-r--r--  1 root  wheel 125 Sep  6 00:49:44 2017 
>> /usr/local/share/u-boot/u-boot-pine64/README
>> -rw-r--r--  1 root  wheel  505940 Sep  6 00:49:43 2017 
>> /usr/local/share/u-boot/u-boot-pine64/u-boot-sunxi-with-spl.bin
>> 
>> 
>> As stands the file must be manually produced.
> 
> Since the latest update of u-boot-pine64 the dtb is included in u-boot.
> U-Boot loads it and pass it to boot1.efi.

Cool . . .

Trying:

# mv /boot/efi/dtb/pine64_plus.dtb /boot/efi/dtb/no_pine64_plus.dtb
# shutdown -r now

does reboot just fine. As does:

# rm -fr /boot/efi/dtb
# shutdown -r now

A cold  boot also boots into the kernel.

So no .dts or .dtb is needed for the Pine64+ 2GB .

For reference after this:

# mount
/dev/label/PINE642GAroot on / (ufs, NFS exported, local, noatime, soft-updates, 
nfsv4acls)
devfs on /dev (devfs, local, multilabel)
/dev/label/PINE642GAboot on /boot/efi (msdosfs, local, noatime)

# find /boot/efi
/boot/efi
/boot/efi/startup.nsh
/boot/efi/EFI
/boot/efi/EFI/BOOT
/boot/efi/EFI/BOOT/bootaa64.efi
/boot/efi/System Volume Information
/boot/efi/System Volume Information/WPSettings.dat


I have no clue if this hidden dtb contributes to the
USB problem(s) or not:

. . .
cryptosoft0: 
NULL mp in getnewvnode(9), tag crossmp
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1:  at usbus0
uhub0:  on usbus0
uhub_attach: getting USB 2.0 HUB descriptor failed,error=USB_ERR_SHORT_XFER
device_attach: uhub0 attach returned 6
usbus0: Root HUB problem, error=USB_ERR_NO_ROOT_HUB
mmcsd0: 32GB  at mmc0 
50.0MHz/4bit/65535-block
. . .

My old -r308??? context not only could use
usb devices but had the root file system on
a USB SSD. But modernizing made plugged in
USB devices not show up.


>> crochet goes to the trouble to have logic to
>> build and install pine64_plus.dtb (based on
>> arm64/pine64_plus.dts ).

Looks like crochet does not need to produce the
.dtb .

It is not even clear that if a dtb/pine64_plus.dtb
exists that it is used for anything.

>> Is pine64_plus.dtb required for the likes of
>> Pine64+ 2GB's?

Now answered as: no.

>> If yes: should it be automatically
>> built and installed someplace for arm64/aarch64
>> builds (even if more manual steps are required to
>> have the final placement on the Pine64 media)?


===
Mark Millard
markmi at  dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Missing in action during arm64/aarch64 builds: no pine64_plus.dtb to be found from buildkernel, installkernel, or u-boot-pine64

[Mark Millard]

On 2017-Sep-10, at 10:26 AM, Tim Kientzle  wrote:

>> On Sep 9, 2017, at 4:35 PM, Mark Millard  wrote:
>> 
>> crochet goes to the trouble to have logic to
>> build and install pine64_plus.dtb (based on
>> arm64/pine64_plus.dts ).
>> 
> 
> I'm not sure about Pine64 in particular, but generally
> only the DTS file is actually required.

[Note:
I used crochet source code to figure out a set of manual
steps sufficient to produce a pine64_plus.dtb to copy to
the boot msdosfs file system.]

Some of the #include structure that the existing
pine64_plus.dts.dts depends on:

# grep "#include" /usr/src/sys /usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts
/usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts:#include 
"sun50i-a64-pine64-plus.dts"
/usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts:#include "a64.dtsi"
/usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts:#include 


# grep "#include" /usr/src/sys 
/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64-pine64-plus.dts
/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64-pine64-plus.dts:#include 
"sun50i-a64-pine64-common.dtsi"

# grep "#include" /usr/src/sys /usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts
/usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts:#include 
"sun50i-a64-pine64-plus.dts"
/usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts:#include "a64.dtsi"
/usr/src/sys/boot/fdt/dts/arm64/pine64_plus.dts:#include 


# grep "#include" /usr/src/sys 
/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64-pine64-plus.dts
/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64-pine64-plus.dts:#include 
"sun50i-a64-pine64-common.dtsi"

# grep "#include" /usr/src/sys 
/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64-pine64-common.dtsi
/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64-pine64-common.dtsi:#include 
"sun50i-a64.dtsi"

# grep "#include" /usr/src/sys /usr/src/sys/boot/fdt/dts/arm64/sun50i-a64.dtsi 
/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64.dtsi:#include 

/usr/src/sys/boot/fdt/dts/arm64/sun50i-a64.dtsi:#include 


# grep "#include" /usr/src/sys /usr/src/sys/boot/fdt/dts/arm64/a64.dtsi 

(Yep: nothing for that last one.)

I would not guess that the full structure is a appropriate as a
substitute for the dtb/pine64_plus.dtb part of the msdosfs
partition for booting the Pine64+ 2GB :

# find /mnt -print
/mnt
/mnt/startup.nsh
/mnt/EFI
/mnt/EFI/BOOT
/mnt/EFI/BOOT/bootaa64.efi
/mnt/dtb
/mnt/dtb/pine64_plus.dtb
/mnt/System Volume Information
/mnt/System Volume Information/WPSettings.dat

# ls -lt /usr/local/share/u-boot/u-boot-pine64/u-boot-sunxi-with-spl.bin 
-rw-r--r--  1 root  wheel  505940 Sep  6 00:49 
/usr/local/share/u-boot/u-boot-pine64/u-boot-sunxi-with-spl.bin

(*.bin dd'd appropriately.)

So there still seems to be a lack of appropriate .dt* material for
direct use/placement on the boot media. Instead manual extra steps
are required relative to *.dt* files.

> Crochet tries to provide a dtb file (converting the dts if necessary)
> partly for documentation and partly to make it easier to edit the
> device tree file.
> 
> This is especially convenient in cases where the
> original DTB file depends heavily on other include files;
> converting DTS to DTB gives you a fully standalone DTB
> file that can be edited (for example, to enable additional
> serial ports) and recompiled without having the full source
> tree available.

The above is the kind of context that the Pine64+'s
have.

It does not appear to me that the existing pine64_plus.dts
is set up for more direct use (even with other supporting
files).

> This is probably less important now that overlay DTBs are
> more commonly supported.

Whatever this is, it seems to not be in use for much (any?)
of the Pine64+ structuring of such things in head -r323246 .


===
Mark Millard
markmi at dsl-only.net




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Missing in action during arm64/aarch64 builds: no pine64_plus.dtb to be found from buildkernel, installkernel, or u-boot-pine64

[Tim Kientzle]

> On Sep 9, 2017, at 4:35 PM, Mark Millard  wrote:
> 
> crochet goes to the trouble to have logic to
> build and install pine64_plus.dtb (based on
> arm64/pine64_plus.dts ).
> 

I'm not sure about Pine64 in particular, but generally
only the DTS file is actually required.

Crochet tries to provide a dtb file (converting the dts if necessary)
partly for documentation and partly to make it easier to edit the
device tree file.

This is especially convenient in cases where the
original DTB file depends heavily on other include files;
converting DTS to DTB gives you a fully standalone DTB
file that can be edited (for example, to enable additional
serial ports) and recompiled without having the full source
tree available.

This is probably less important now that overlay DTBs are
more commonly supported.

Tim




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Missing in action during arm64/aarch64 builds: no pine64_plus.dtb to be found from buildkernel, installkernel, or u-boot-pine64

[Mark Millard]

The context here is head -r323246 amd64 -> arm64/aarch64
cross build activity.

>From installkernel :

# find /usr/obj/DESTDIRs/clang-cortexA53-installkernel/ -name "*.dtb" -print
# 

>From buildkernel :

# find /usr/obj/cortexA53_clang/arm64.aarch64/ -name "*.dtb" -print
# 

>From installing u-boot-pine64 :

# ls -lTd /usr/local/share/u-boot/u-boot-pine64/*
-rw-r--r--  1 root  wheel 125 Sep  6 00:49:44 2017 
/usr/local/share/u-boot/u-boot-pine64/README
-rw-r--r--  1 root  wheel  505940 Sep  6 00:49:43 2017 
/usr/local/share/u-boot/u-boot-pine64/u-boot-sunxi-with-spl.bin


As stands the file must be manually produced.

crochet goes to the trouble to have logic to
build and install pine64_plus.dtb (based on
arm64/pine64_plus.dts ).

Is pine64_plus.dtb required for the likes of
Pine64+ 2GB's? If yes: should it be automatically
built and installed someplace for arm64/aarch64
builds (even if more manual steps are required to
have the final placement on the Pine64 media)?


===
Mark Millard
markmi at  dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: if_igb.ko symbolic link generation is still messed up in that it hard wires the path at installkernel time, messing up copying to other places

[Ian Lepore]

On Sat, 2017-09-09 at 15:31 -0700, Simon J. Gerraty wrote:
> Mark Millard <mar...@dsl-only.net> wrote:
> > 
> > # ls -lTt /media/boot/kernel/if_igb.ko /mnt/boot/kerndb/if_igb.ko
> > lrwxr-xr-x  1 root  wheel  25 Sep  8 22:47:36 2017
> > /mnt/boot/kerndb/if_igb.ko -> /mnt/boot/kernel/if_em.ko
> > lrwxr-xr-x  1 root  wheel  68 Sep  6 20:27:20 2017
> > /media/boot/kernel/if_igb.ko -> /usr/obj/DESTDIRs/clang-cortexA53-
> > installkernel/boot/kernel/if_em.ko
> > 
> > In both of these cases the /mnt and /usr/obj/DESTDIRs/ prefixes
> > would not exist for booting the PINE64 that the USB SSD is for:
> > so file not found if a usage attempt is made.
> Yes, when making symlinks in presence of DESTDIR, the src should have
> $DESTDIR removed - the following should usually be safe:
> 
> ln -s ${src#$DESTDIR} $DESTDIR${target#$DESTDIR}
> 

I think the modern fix for this would be "install -l rs $src $DESTDIR",
that should result in if_igb.ko -> if_em.ko without any dir nodes in
the link.

-- Ian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: if_igb.ko symbolic link generation is still messed up in that it hard wires the path at installkernel time, messing up copying to other places

[Simon J. Gerraty]

Mark Millard <mar...@dsl-only.net> wrote:
> # ls -lTt /media/boot/kernel/if_igb.ko /mnt/boot/kerndb/if_igb.ko
> lrwxr-xr-x  1 root  wheel  25 Sep  8 22:47:36 2017 /mnt/boot/kerndb/if_igb.ko 
> -> /mnt/boot/kernel/if_em.ko
> lrwxr-xr-x  1 root  wheel  68 Sep  6 20:27:20 2017 
> /media/boot/kernel/if_igb.ko -> 
> /usr/obj/DESTDIRs/clang-cortexA53-installkernel/boot/kernel/if_em.ko
> 
> In both of these cases the /mnt and /usr/obj/DESTDIRs/ prefixes
> would not exist for booting the PINE64 that the USB SSD is for:
> so file not found if a usage attempt is made.

Yes, when making symlinks in presence of DESTDIR, the src should have
$DESTDIR removed - the following should usually be safe:

ln -s ${src#$DESTDIR} $DESTDIR${target#$DESTDIR}

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

if_igb.ko symbolic link generation is still messed up in that it hard wires the path at installkernel time, messing up copying to other places

[Mark Millard]

[The example here happens to be for amd64 -> aarch64 cross builds.]

The following is from after copying/moving the kernel from where it
was originally, such as (locally) installed on the build machine.
Example of symbolic links from some recent activity under head
-r323246 (producing -r323246 again):

# ls -lTt /media/boot/kernel/if_igb.ko /mnt/boot/kerndb/if_igb.ko
lrwxr-xr-x  1 root  wheel  25 Sep  8 22:47:36 2017 /mnt/boot/kerndb/if_igb.ko 
-> /mnt/boot/kernel/if_em.ko
lrwxr-xr-x  1 root  wheel  68 Sep  6 20:27:20 2017 /media/boot/kernel/if_igb.ko 
-> /usr/obj/DESTDIRs/clang-cortexA53-installkernel/boot/kernel/if_em.ko

In both of these cases the /mnt and /usr/obj/DESTDIRs/ prefixes
would not exist for booting the PINE64 that the USB SSD is for:
so file not found if a usage attempt is made.

Installing absolute path links messes up even the /boot/kernel.old/
handling unless that process carefully replaces the original link
that was in /boot/kernel/ .

In the /mnt/boot/kerndb/if_igb.ko -> /mnt/boot/kernel/if_em.ko
example I made a copy of the installed /mnt/boot/kernel/ area
while the drive was still mounted.

In the /usr/obj/DESTDIRs/ case I had installed to the local
file system before attaching the USB SSD it was to be copied
to.

A relative path would not have such problems with binding to
the wrong file or to no file when copies are made or renames
along the path are done.


[This has come up before on the lists, multiple-times as I
remember.]

===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

head -r320192 -> -r320387 kernel build and install to a DESTDIR: if_igb.ko vs. DESTDIR use for installkernel has symbolic link that seems inapproriate

[Mark Millard]

installkernel  
DESTDIR=/usr/obj/DESTDIRs/clang-amd64-installkernel-r320192_r320387

produced a if_igb.ko (this used: ls -lD %C ):

lrwxr-xr-x  1 root  wheel80 20 if_igb.ko -> 
/usr/obj/DESTDIRs/clang-amd64-installkernel-r320192_r320387/boot/kernel/if_em.ko

This does not allow simple copies of such directory trees
that have if_igb.ko pointing to the right if_em.ko.

Looking in my -r320192 based /boot/kernel/ that had been filled in
via a default DESTDIR for installkernel  (this used: ls -lD %C ):

lrwxr-xr-x  1 root  wheel21 20 if_igb.ko -> /boot/kernel/if_em.ko

So something like:

cp -aRx /boot/kernel/ /boot/kercgd

ends up with /boot/kercgd/if_igb.ko pointing into /boot/kernel/ instead
of into /boot/kercgd/ .



===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ZSF and installkernel 10.0-BETA1

[Phillip Kinsley]

I installed Beta1 using the ZFS option, all default settings. I sync the
source the other day and did a buildworld and buildkernel. When I do
installkernel I get

mkdir -p /boot/kernel
mkdir: /boot: No such file or directory

and the install stops. With another box that used a standard UFS
installation I have no problem.

I'm sure the ZFS installkernel is know issue, but I can't seem to find if
there is a solution or not.
Is there a work around or not?

Thanks


Phillip
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: ZSF and installkernel 10.0-BETA1

[Allan Jude]

On 2013-11-14 12:48, Phillip Kinsley wrote:
 I installed Beta1 using the ZFS option, all default settings. I sync the
 source the other day and did a buildworld and buildkernel. When I do
 installkernel I get

 mkdir -p /boot/kernel
 mkdir: /boot: No such file or directory

 and the install stops. With another box that used a standard UFS
 installation I have no problem.

 I'm sure the ZFS installkernel is know issue, but I can't seem to find if
 there is a solution or not.
 Is there a work around or not?

 Thanks


 Phillip
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

What do you mean 'the zfs option'? You mean you used the ZFS
installation option in bsdinstall?

That is a known issue that was fixed in later versions, here are the
instructions to fix it:

http://lists.freebsd.org/pipermail/freebsd-stable/2013-October/075504.html

o Updates to bsdinstall(8).  Please note the following:
- 10.0-BETA1 introduces a number of updates to bsdinstall(8),
  notably the ability to install to a full ZFS filesystem.
  Please keep in mind that this is an experimental feature.
- If using the ZFS installation option in *and* have enabled
  full-disk encryption is enabled, a few entries will need to be
  manually added to loader.conf(5) before the 'bootpool' zpool
  will be available after the system boots.  This manual step
  is expected to be fixed in 10.0-BETA2.

  The entries that need to be added are:

zpool_cache_load=YES
zpool_cache_type=/boot/zfs/zpool.cache
zpool_cache_name=/boot/zfs/zpool.cache

  This can be done at the final menu of bsdinstall(8), when
  prompted to boot into the newly-installed system;
  alternatively, this can be done post-install, in which case,
  the following must be run before appending loader.conf(5):

# zpool import -f bootpool




-- 
Allan Jude




signature.asc
Description: OpenPGP digital signature

[make installworld installkernel] does not honor break at installworld

[Boris Samorodov]

Hi All,

while installing FreeBSD at a new disk the installworld phase breaks
(see the thread ...cannot create mapper.dir: Permission denied).
However the command make installworld installkernel proceeds to
installkernel phase.

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

CURRENT r253794: make installkernel fails: install: runfw.ko: No such file or directory

[O. Hartmann]

make installkernel  fails in r253794 with the following error:

=== usb/runfw (install)
install -o root -g wheel -m 555   runfw.ko /boot/kernel
install: runfw.ko: No such file or directory
*** Error code 71

regards,

oliver


signature.asc
Description: PGP signature

Re: CURRENT r253794: make installkernel fails: install: runfw.ko: No such file or directory

[O. Hartmann]

On Tue, 30 Jul 2013 09:29:56 +0200
O. Hartmann ohart...@zedat.fu-berlin.de wrote:

 
 
 make installkernel  fails in r253794 with the following error:
 
 === usb/runfw (install)
 install -o root -g wheel -m 555   runfw.ko /boot/kernel
 install: runfw.ko: No such file or directory
 *** Error code 71
 
 regards,
 
 oliver

This is fun:

The make buildworld buildkernel command worked once, world and
kernel/modules got built. 

While make installkernel fails with the above shown error, a make
kernel issued again failed then at

=== usb/runfw (all)
make: don't know how to
make /usr/src/sys/modules/usb/runfw/../../contrib/dev/run/rt2870.fw.uu.
Stop

make: stopped in /usr/src/sys/modules/usb/runfw
*** Error code 2



signature.asc
Description: PGP signature

Re: CURRENT r253794: make installkernel fails: install: runfw.ko: No such file or directory

[Sergey Kandaurov]

On 30 July 2013 11:44, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
 On Tue, 30 Jul 2013 09:29:56 +0200
 O. Hartmann ohart...@zedat.fu-berlin.de wrote:



 make installkernel  fails in r253794 with the following error:

 === usb/runfw (install)
 install -o root -g wheel -m 555   runfw.ko /boot/kernel
 install: runfw.ko: No such file or directory
 *** Error code 71

 regards,

 oliver

 This is fun:

 The make buildworld buildkernel command worked once, world and
 kernel/modules got built.

 While make installkernel fails with the above shown error, a make
 kernel issued again failed then at

 === usb/runfw (all)
 make: don't know how to
 make /usr/src/sys/modules/usb/runfw/../../contrib/dev/run/rt2870.fw.uu.
 Stop

 make: stopped in /usr/src/sys/modules/usb/runfw
 *** Error code 2


Please try this patch.

Index: sys/modules/usb/runfw/Makefile
===
--- sys/modules/usb/runfw/Makefile  (revision 253794)
+++ sys/modules/usb/runfw/Makefile  (working copy)
@@ -5,7 +5,7 @@

 CLEANFILES=run.fw

-run.fw: ${.CURDIR}/../../contrib/dev/run/rt2870.fw.uu
-   uudecode -p ${.CURDIR}/../../contrib/dev/run/rt2870.fw.uu  ${.TARGET}
+run.fw: ${.CURDIR}/../../../contrib/dev/run/rt2870.fw.uu
+   uudecode -p ${.CURDIR}/../../../contrib/dev/run/rt2870.fw.uu  
${.TARGET}

 .include bsd.kmod.mk


-- 
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Warren Block]

On Wed, 2 Jan 2013, Robert Huff wrote:

	(While this may not be a strictly CURRENT issue, I asked on 
questions@, but have not found a solution.)


Situation:
	One of my boxes failed, and for various reasons it became easier to 
just scrub and rebuild it. Like its predecessor it will run CURRENT

1) Using BSDinstall, I flushed then created the first disk:

ada2p1  freebsd-boot128k
ada2p2  freebsd-swap4g
ada2p3  freebsd-ufs 25g

(There are non-bootable disks at ada0, -1, and -3.)

	2) Installed off the 9.0 CD, got it up and running, everything was 
good.

3) Used csup (tag=.) to update the source tree as of 00:01 on 12/30.
4a) Built world - OK.
4b) Build kernel - OK.
4c) Ran mergemaster - OK.
4d) Installed kernel - OK.
5) On rebooting, the loader(??) claims to not be able to find a
bootable partition - i.e. I get a screen that ends in mountroot  .
Providing the presumptive value by hand returns error 19.
	6) Boot using installation CD and use gpart show to double check 
device names and partitions; everything looks good.

7) Try normal booting again, no go.

	This is my first time installing to a completely GPT partitioned 
system, and I have (obviously) failed to grok something.  I checked 
src/UPDATING and found nothing which covered this.

What have I bungled, and how do I fix it?


It really does not sound like a GPT problem, because 9.0 booted.  The 
-current kernel can't find/detect the device.  Scrolling back in the 
console buffer might find a problem.  buildworld/kernel/installworld do 
not affect the disk partitioning, but can change the code that looks for 
those partitions.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Robert Huff]

On 1/3/2013 11:40 AM, Warren Block wrote:

On Wed, 2 Jan 2013, Robert Huff wrote:


(While this may not be a strictly CURRENT issue, I asked on
questions@, but have not found a solution.)

Situation:
One of my boxes failed, and for various reasons it became easier
to just scrub and rebuild it. Like its predecessor it will run CURRENT
1) Using BSDinstall, I flushed then created the first disk:

ada2p1freebsd-boot128k
ada2p2freebsd-swap4g
ada2p3freebsd-ufs25g

5) On rebooting, the loader(??) claims to not be able to find a
bootable partition - i.e. I get a screen that ends in mountroot  .
Providing the presumptive value by hand returns error 19.


It really does not sound like a GPT problem, because 9.0 booted.


	I don't (at the moment) think it's GPT caused; but I do think it may be 
GPT related.




  The
-current kernel can't find/detect the device.  Scrolling back in the
console buffer might find a problem.  buildworld/kernel/installworld do
not affect the disk partitioning, but can change the code that looks for
those partitions.


	Exactly.  I'm looking for help figuring out how the hand-off from 
loader to kernel got broken and what I have to do to fix it.
	One possibility: I believe I labeled each of the partitions during the 
gpt creation process.  Can I use those labels to (hopefully) by-pass 
this issue?



Robert Huff
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Kevin Oberman]

On Wed, Jan 2, 2013 at 12:03 PM, Robert Huff roberth...@rcn.com wrote:
 On 1/2/2013 1:57 PM, Benjamin Kaduk wrote:

 On Wed, 2 Jan 2013, Robert Huff wrote:


 For a full clean install, I believe that bsdinstall should prompt about
 installing bootcode around here.  I don't really understand from your
 procedure how bsdinstall was used; there might be some edge case where
 there is no prompt about bootcode.

 2) Installed off the 9.0 CD, got it up and running, everything was
 good.


 Let me elaborate on this:

 2) Installed off the 9.0 CD, had a fully bootable system connected
 to the Internet, everything was good.


 I think you should investigate the 'bootcode' subcommand of gpart(8).


 Does the above change things?
 It was my expectation installkernel would Do The Right Thing with
 respect to new bootcode, and I am surprised it did not.

installkernel does absolutely nothing to the boot partition. You need
to use bsdinstall or gpart to write the new image to disk.

That said, I know of no reason that the boot code written by the 9.0
install would fail to boot head. I am running 9.1 on a GPT disk and it
works fine, but I that disk is ada1 and I have booteasy installed on
the MBR of ada0. It has no problems booting the 9.1 system. (Windows 7
in on ada0.) Then again, I am hardly an expert on the subject.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Kevin Oberman]

On Thu, Jan 3, 2013 at 3:23 PM, Robert Huff roberth...@rcn.com wrote:
 On 1/3/2013 11:40 AM, Warren Block wrote:

 On Wed, 2 Jan 2013, Robert Huff wrote:

 (While this may not be a strictly CURRENT issue, I asked on
 questions@, but have not found a solution.)

 Situation:
 One of my boxes failed, and for various reasons it became easier
 to just scrub and rebuild it. Like its predecessor it will run CURRENT
 1) Using BSDinstall, I flushed then created the first disk:

 ada2p1freebsd-boot128k
 ada2p2freebsd-swap4g
 ada2p3freebsd-ufs25g

 5) On rebooting, the loader(??) claims to not be able to find a
 bootable partition - i.e. I get a screen that ends in mountroot  .
 Providing the presumptive value by hand returns error 19.


 It really does not sound like a GPT problem, because 9.0 booted.


 I don't (at the moment) think it's GPT caused; but I do think it may
 be GPT related.



   The
 -current kernel can't find/detect the device.  Scrolling back in the
 console buffer might find a problem.  buildworld/kernel/installworld do
 not affect the disk partitioning, but can change the code that looks for
 those partitions.


 Exactly.  I'm looking for help figuring out how the hand-off from
 loader to kernel got broken and what I have to do to fix it.
 One possibility: I believe I labeled each of the partitions during
 the gpt creation process.  Can I use those labels to (hopefully) by-pass
 this issue?

Yes! This is the current recommended way of doing it.
 cat /etc/fstab
# DeviceMountpoint  FStype  Options DumpPass#
/dev/gpt/swap   noneswapsw  0   0
/dev/gpt/root   /   ufs rw  1   1
/dev/gpt/tmp/tmpufs rw  2   2
/dev/gpt/usr/usrufs rw  2   2
/dev/gpt/var/varufs rw  2   2
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Warren Block]

On Thu, 3 Jan 2013, Kevin Oberman wrote:


One possibility: I believe I labeled each of the partitions during
the gpt creation process.  Can I use those labels to (hopefully) by-pass
this issue?


Yes! This is the current recommended way of doing it.

cat /etc/fstab

# DeviceMountpoint  FStype  Options DumpPass#
/dev/gpt/swap   noneswapsw  0   0
/dev/gpt/root   /   ufs rw  1   1
/dev/gpt/tmp/tmpufs rw  2   2
/dev/gpt/usr/usrufs rw  2   2
/dev/gpt/var/varufs rw  2   2


To avoid collisions, I recommend people use unique labels on each 
system.  I sometimes pick a couple of letters from the system name or 
drive: xfswap, xfrootfs, xftmpfs, xfusrfs, xfvarfs.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

SOLVED: problem after installkernel going from 9.0 to CURRENT

[Robert Huff]

   Using the GPT labels is a winning solution.

   Thanks to all those who helped,


 Robert Huff


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Kevin Oberman]

On Thu, Jan 3, 2013 at 7:24 PM, Warren Block wbl...@wonkity.com wrote:
 On Thu, 3 Jan 2013, Kevin Oberman wrote:

 One possibility: I believe I labeled each of the partitions
 during
 the gpt creation process.  Can I use those labels to (hopefully) by-pass
 this issue?


 Yes! This is the current recommended way of doing it.

 cat /etc/fstab

 # DeviceMountpoint  FStype  Options Dump
 Pass#
 /dev/gpt/swap   noneswapsw  0   0
 /dev/gpt/root   /   ufs rw  1   1
 /dev/gpt/tmp/tmpufs rw  2   2
 /dev/gpt/usr/usrufs rw  2   2
 /dev/gpt/var/varufs rw  2   2


 To avoid collisions, I recommend people use unique labels on each system.  I
 sometimes pick a couple of letters from the system name or drive: xfswap,
 xfrootfs, xftmpfs, xfusrfs, xfvarfs.

Good point (as usual).

The example was from my laptop where this is not an issue, but in
larger environments it is an excellent suggestion.

I would put the unique ID at the end of the label as the eye tends to
read from left to right (at least in most language so you can
recognize whether it is usr or swap or home pretty much instantly.
Sticking letters at the start make the most fundamental information
harder to see.
swaprxf xfswap
usrfsxf  xfusrfs

Still, this is a nit and I appreciate the suggestion!..
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

problem after installkernel going from 9.0 to CURRENT

[Robert Huff]

	(While this may not be a strictly CURRENT issue, I asked on questions@, 
but have not found a solution.)


Situation:
	One of my boxes failed, and for various reasons it became easier to 
just scrub and rebuild it. Like its predecessor it will run CURRENT

1) Using BSDinstall, I flushed then created the first disk:

ada2p1  freebsd-boot128k
ada2p2  freebsd-swap4g
ada2p3  freebsd-ufs 25g

(There are non-bootable disks at ada0, -1, and -3.)

2) Installed off the 9.0 CD, got it up and running, everything was good.
3) Used csup (tag=.) to update the source tree as of 00:01 on 12/30.
4a) Built world - OK.
4b) Build kernel - OK.
4c) Ran mergemaster - OK.
4d) Installed kernel - OK.
5) On rebooting, the loader(??) claims to not be able to find a
bootable partition - i.e. I get a screen that ends in mountroot  .
Providing the presumptive value by hand returns error 19.
	6) Boot using installation CD and use gpart show to double check 
device names and partitions; everything looks good.

7) Try normal booting again, no go.

	This is my first time installing to a completely GPT partitioned 
system, and I have (obviously) failed to grok something.  I checked 
src/UPDATING and found nothing which covered this.

What have I bungled, and how do I fix it?


Respectfully,


Robert Huff


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Benjamin Kaduk]

On Wed, 2 Jan 2013, Robert Huff wrote:

	(While this may not be a strictly CURRENT issue, I asked on 
questions@, but have not found a solution.)


Situation:
	One of my boxes failed, and for various reasons it became easier to 
just scrub and rebuild it. Like its predecessor it will run CURRENT

1) Using BSDinstall, I flushed then created the first disk:

ada2p1  freebsd-boot128k
ada2p2  freebsd-swap4g
ada2p3  freebsd-ufs 25g

(There are non-bootable disks at ada0, -1, and -3.)


For a full clean install, I believe that bsdinstall should prompt about 
installing bootcode around here.  I don't really understand from your 
procedure how bsdinstall was used; there might be some edge case where 
there is no prompt about bootcode.


	2) Installed off the 9.0 CD, got it up and running, everything was 
good.

3) Used csup (tag=.) to update the source tree as of 00:01 on 12/30.
4a) Built world - OK.
4b) Build kernel - OK.
4c) Ran mergemaster - OK.
4d) Installed kernel - OK.
5) On rebooting, the loader(??) claims to not be able to find a
bootable partition - i.e. I get a screen that ends in mountroot  .
Providing the presumptive value by hand returns error 19.
	6) Boot using installation CD and use gpart show to double check 
device names and partitions; everything looks good.

7) Try normal booting again, no go.

	This is my first time installing to a completely GPT partitioned 
system, and I have (obviously) failed to grok something.  I checked 
src/UPDATING and found nothing which covered this.

What have I bungled, and how do I fix it?


I think you should investigate the 'bootcode' subcommand of gpart(8).

-Ben Kaduk
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: problem after installkernel going from 9.0 to CURRENT

[Robert Huff]

On 1/2/2013 1:57 PM, Benjamin Kaduk wrote:

On Wed, 2 Jan 2013, Robert Huff wrote:



For a full clean install, I believe that bsdinstall should prompt about
installing bootcode around here.  I don't really understand from your
procedure how bsdinstall was used; there might be some edge case where
there is no prompt about bootcode.


2) Installed off the 9.0 CD, got it up and running, everything was
good.


Let me elaborate on this:

	2) Installed off the 9.0 CD, had a fully bootable system connected to 
the Internet, everything was good.



I think you should investigate the 'bootcode' subcommand of gpart(8).


Does the above change things?
	It was my expectation installkernel would Do The Right Thing with 
respect to new bootcode, and I am surprised it did not.


Respectfully,


Robert Huff


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: ports/171426: multimedia/cuse4bsd-kmod now breaks rebuild of kmods during kernel or installkernel build

[Hans Petter Selasky]

On Saturday 08 September 2012 01:00:33 ed...@freebsd.org wrote:
 Synopsis: multimedia/cuse4bsd-kmod now breaks rebuild of kmods during
 kernel or installkernel build
 
 Responsible-Changed-From-To: freebsd-ports-bugs-hselasky
 Responsible-Changed-By: edwin
 Responsible-Changed-When: Fri Sep 7 23:00:33 UTC 2012
 Responsible-Changed-Why:
 Over to maintainer (via the GNATS Auto Assign Tool)
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=171426

Cuse4BSD needs OSVERSION set. This does not appear to be a cuse4bsd-kmod 
issue.

You can try to wrap the OSVERSION check into:

.if defined(OSVERSION)

.endif

--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Upgrading 8.2 to 9.0-rc2: missing directories at 'make installkernel'

[Mark Martinec]

When upgrading a FreeBSD 8.2 (amd64) to today's csup (tag=RELENG_9,
i.e. 9.0-RC2), the standard procedure got itself into trouble:

  rm -rf /usr/obj
  make buildworld
  make buildkernel KERNCONF=xxx
  make installkernel KERNCONF=xxx

(the xxx is mostly a plain vanilla 'include GENERIC'
with pf altq and GEOM_ELI added).

The 'make installkernel' phase was failing on missing directories.
Creating these manually and repeating the make installkernel
eventually lead to a successful installation.

The missing directories that needed to be created manually were:

  /usr/include/clang  (and possibly /usr/include/clang/3.0 )
  /usr/include/gcc(and possibly /usr/include/gcc/4.2 )
  /libexec/resolvconf
  /usr/share/doc/llvm
  /usr/share/locale/la_LN.ISO8859-13/LC_COLLATE [...]

Actually the /usr/share/locale was a mess, missing several
files, so I ended up replacing this directory by what has been
built in the 'make buildworld' phase under /usr/obj.

Just wanted to point out a possible problem others may encounter.

  Mark
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

MAKEOBJDIRPREFIX and installkernel

[Boris Samorodov]

Hi List,

here is something strange with current CURRENT:
-
[~]b...@izar% LANG=C svn info FreeBSD/base/head/src
Path: FreeBSD/base/head/src
URL: svn+ssh://svn.freebsd.org/base/head
Repository Root: svn+ssh://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 208354
Node Kind: directory
Schedule: normal
Last Changed Author: jkim
Last Changed Rev: 208353
Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010)

[~]b...@izar% echo $MAKEOBJDIRPREFIX
/home/bsam/FreeBSD/base/head/obj

[~]b...@izar% sudo make -C FreeBSD/base/head/src installkernel
--
 Installing kernel
--
cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR;  
MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=  
GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin  
GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font
  
GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac
 
PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  make KERNEL=kernel install
cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR
*** Error code 2

Stop in /usr/home/bsam/FreeBSD/base/head/src.
*** Error code 1

Stop in /usr/home/bsam/FreeBSD/base/head/src.
[~]b...@izar%
-

That command used to work fine for years...

-- 
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: MAKEOBJDIRPREFIX and installkernel

[Yuri Pankov]

On Thu, May 20, 2010 at 09:59:25PM +0400, Boris Samorodov wrote:
 Hi List,
 
 here is something strange with current CURRENT:
 -
 [~]b...@izar% LANG=C svn info FreeBSD/base/head/src
 Path: FreeBSD/base/head/src
 URL: svn+ssh://svn.freebsd.org/base/head
 Repository Root: svn+ssh://svn.freebsd.org/base
 Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
 Revision: 208354
 Node Kind: directory
 Schedule: normal
 Last Changed Author: jkim
 Last Changed Rev: 208353
 Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010)
 
 [~]b...@izar% echo $MAKEOBJDIRPREFIX
 /home/bsam/FreeBSD/base/head/obj
 
 [~]b...@izar% sudo make -C FreeBSD/base/head/src installkernel
 --
  Installing kernel
 --
 cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR;  
 MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=  
 GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin
   
 GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font
   
 GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac
  
 PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
   make KERNEL=kernel install
 cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR
 *** Error code 2
 
 Stop in /usr/home/bsam/FreeBSD/base/head/src.
 *** Error code 1
 
 Stop in /usr/home/bsam/FreeBSD/base/head/src.
 [~]b...@izar%
 -
 
 That command used to work fine for years...

Works here. May you've recently changed your sudoers to not keep env
variables?

 
 -- 
 WBR, Boris Samorodov (bsam)
 Research Engineer, http://www.ipt.ru Telephone  Internet SP
 FreeBSD Committer, http://www.FreeBSD.org The Power To Serve

Yuri
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: MAKEOBJDIRPREFIX and installkernel

[Boris Samorodov]

On Thu, 20 May 2010 22:58:00 +0400 Yuri Pankov wrote:
 On Thu, May 20, 2010 at 09:59:25PM +0400, Boris Samorodov wrote:
  Hi List,
  
  here is something strange with current CURRENT:
  -
  [~]b...@izar% LANG=C svn info FreeBSD/base/head/src
  Path: FreeBSD/base/head/src
  URL: svn+ssh://svn.freebsd.org/base/head
  Repository Root: svn+ssh://svn.freebsd.org/base
  Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
  Revision: 208354
  Node Kind: directory
  Schedule: normal
  Last Changed Author: jkim
  Last Changed Rev: 208353
  Last Changed Date: 2010-05-20 20:24:12 +0400 (Thu, 20 May 2010)
  
  [~]b...@izar% echo $MAKEOBJDIRPREFIX
  /home/bsam/FreeBSD/base/head/obj
  
  [~]b...@izar% sudo make -C FreeBSD/base/head/src installkernel
  --
   Installing kernel
  --
  cd /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR;  
  MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=  
  GROFF_BIN_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin

  GROFF_FONT_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/groff_font

  GROFF_TMAC_PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/share/tmac
   
  PATH=/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/legacy/usr/games:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/sbin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/bin:/usr/obj/usr/home/bsam/FreeBSD/base/head/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
make KERNEL=kernel install
  cd: can't cd to /usr/obj/usr/home/bsam/FreeBSD/base/head/src/sys/IZAR
  *** Error code 2
  
  Stop in /usr/home/bsam/FreeBSD/base/head/src.
  *** Error code 1
  
  Stop in /usr/home/bsam/FreeBSD/base/head/src.
  [~]b...@izar%
  -
  
  That command used to work fine for years...

 Works here. May you've recently changed your sudoers to not keep env
 variables?

Hm. I've upgraded ports recently. However sudoers is the same.
Thanks for the tip. I'll try to find out what has changed at my
system.

-- 
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone  Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

installkernel broken - if.wi.ko

[Raman Ng]

I have cvsup the source (current) yesterday that is about 14 hours ago.
Buildworld and buildkernel without any problem.  However, when I tried to
installkernel the following error is found.
.
.
.
install -c -o root -g wheel -m 555   splash_bmp.ko /boot/kernel/
=== splash/pcx
install -c -o root -g wheel -m 555   splash_pcx.ko /boot/kernel/
=== sr
install -c -o root -g wheel -m 555   if_sr.ko /boot/kernel/
=== stg
install -c -o root -g wheel -m 555   stg.ko /boot/kernel/
=== streams
install -c -o root -g wheel -m 555   streams.ko /boot/kernel/
=== vesa
install -c -o root -g wheel -m 555   vesa.ko /boot/kernel/
=== wi
install -c -o root -g wheel -m 555   if_wi.ko /boot/kernel/
kldxref /boot/kernel
*** Error code 1 (ignored)

Cheers,
Raman


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: installkernel broken - if.wi.ko

[M. Warner Losh]

In message: 001601c19bf8$04c1f7e0$ae60dacb@joannaraman
Raman Ng [EMAIL PROTECTED] writes:
: I have cvsup the source (current) yesterday that is about 14 hours ago.
: Buildworld and buildkernel without any problem.  However, when I tried to
: installkernel the following error is found.
: kldxref /boot/kernel
: *** Error code 1 (ignored)

Don't worry about it.  you build and installed -current on a -stable
machine.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

make installkernel fails

[P. U. (Uli) Kruppa]

Hi

I cvsupped my sources yesterday.
# make bulidworld
# make buildkernel
were o.k. ,
# make installkernel stopped with

cd /usr/obj/usr/src/sys/PUKRUPPA-5.5;
MAKEOBJDIRPREFIX=/usr/obj
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec
CFLAGS=-nostdinc -O -pipe 
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0
GROFF_BIN_PATH=/usr/obj/usr/src/i386/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/i386/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/i386/usr/share/tmac
MACHINE=i386 make KERNEL=kernel install *** Error code 2

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

Regards.

Uli.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: make DESTDIR=foo failing in installkernel ?

[Adrian Chadd]

On Mon, Oct 30, 2000, David O'Brien wrote:
 On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote:
  cd /crash/usr/src/sys/modules  env
  MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules
  KMODDIR=/crash/boot/kernel make install
 
 
 Don't explicitly add DESTDIR to KMODDIR.
 
 -- 
 -- David  ([EMAIL PROTECTED])
   GNU is Not Unix / Linux Is Not UniX

Thats all fine and good, but I don't want to touch the makefile magic.
Can someone else proficient in Makefile h0h0magick do it if it hasn't
been done already? :)

Thanks!


Adrian

-- 
Adrian Chadd"Programming is like sex:
[EMAIL PROTECTED]   One mistake and you have to support for
a lifetime." -- rec.humor.funny



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make DESTDIR=foo failing in installkernel ?

[David O'Brien]

On Thu, Nov 02, 2000 at 10:20:36AM +0100, Adrian Chadd wrote:
 On Mon, Oct 30, 2000, David O'Brien wrote:
  On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote:
   cd /crash/usr/src/sys/modules  env
   MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules
   KMODDIR=/crash/boot/kernel make install
  
  Don't explicitly add DESTDIR to KMODDIR.
 
 Thats all fine and good, but I don't want to touch the makefile magic.

I mean when you set KMODDIR, only use "/boot/kernel", as the bsd.*.mk
Makefiles will add DESTDIR for you.

 Can someone else proficient in Makefile h0h0magick do it if it hasn't
 been done already? :)

Not sure what Makefile hackery is needed as I'm not sure what you're
wanting to do.
 
-- 
-- David  ([EMAIL PROTECTED])
  GNU is Not Unix / Linux Is Not UniX


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

make DESTDIR=foo failing in installkernel ?

[Adrian Chadd]

I can't be the only person who is trying to do this :)

I have my laptop with two BSD partitions - one active, and one for the
most current -current. (Its running -current from a couple months ago.)
So, I do the following:


roaming# cat crash-buildworld.sh
#!/bin/sh

DESTDIR=/crash ; export DESTDIR
MAKEOBJDIRPREFIX=/crash ; export MAKEOBJDIRPREFIX

cd /crash/usr/src
make buildworld  make installworld
make buildkernel  make installkernel

now, besides needing to copy GENERIC.hints to /crash/boot/device.hints, this
should work, right ?

Unfortunately, I get this error:

mkdir -p /crash/boot/kernel
install -c -m 555 -o root -g wheel -fschg  kernel /crash/boot/kernel
cd /crash/usr/src/sys/modules  env 
MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules KMODDIR=/crash/boot/kernel 
make install
=== 3dfx
install -c -o root -g wheel -m 555   3dfx.ko /crash/crash/boot/kernel
install: /crash/crash/boot/kernel: No such file or directory
*** Error code 71

Now, in src/sys/conf/kmod.mk, is this bit of magic:

realinstall: _SUBDIR
${INSTALL} ${COPY} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \
${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR}

KMODDIR includes DESTDIR from what I can see, in
/usr/obj/crash/usr/src/sys/GENERIC/Makefile :


MKMODULESENV=   MAKEOBJDIRPREFIX=${.OBJDIR}/modules KMODDIR=${DESTDIR}${KODIR}


To be triple-sure, i did a make install in /usr/src/share/mk/ to update my
mkfiles, but that still hasn't helped.

Any clues?



Adrian
-- 
Adrian Chadd"Programming is like sex:
[EMAIL PROTECTED]   One mistake and you have to support for
a lifetime." -- rec.humor.funny



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make DESTDIR=foo failing in installkernel ?

[David O'Brien]

On Mon, Oct 30, 2000 at 09:15:00AM +0100, Adrian Chadd wrote:
 cd /crash/usr/src/sys/modules  env
 MAKEOBJDIRPREFIX=/usr/obj/crash/usr/src/sys/GENERIC/modules
 KMODDIR=/crash/boot/kernel make install


Don't explicitly add DESTDIR to KMODDIR.

-- 
-- David  ([EMAIL PROTECTED])
  GNU is Not Unix / Linux Is Not UniX


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make installkernel broken by recent manpage changes

[Wesley Morgan]

Since we are on the subject of installing kernels, i noticed last night
that the target "make kernel-install" (not part of world) will cause your
modules to be moved into modules.old. It looks like the routine that moved
the kernel - kernel.old was not changed or something like that. Or maybe
this is what was intended... But it surely was not what I expected.
Shouldnt the tree be pushed over to "old" under different circumstances
(like a new module installation, and of course for the install target)?

On Sat, 7 Oct 2000, Tony Fleisher wrote:

 I just ran through this myself trying to update to newest -current. 
 I am not exactly sure what caused the breakage (perhaps some 
 changes inthe share/mk/* files?), nor what the "proper" fix is, 
 however I was able to get the kernel to install properly by adding
 NOMANCOMPRESS=true in the
 following Makefiles:
 

-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED] _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
  6bone: 3ffe:1ce3:7::b4ff:fe53:c297
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make installkernel broken by recent manpage changes

[David O'Brien]

 === joy
 install -C -c -o root -g wheel -m 555   joy.ko /boot/kernel
 install -C -c -o root -g wheel -m 444 joy.8.gz  /usr/share/man/man8
 install: joy.8.gz: No such file or directory
 *** Error code 71

Since the manpages are being moved elsewhere, I went ahead and removed
them from the Makefile's since they were causing problems.

-- 
-- David  ([EMAIL PROTECTED])
  Gnu is Not Unix / Linux Is Not UniX


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make installkernel broken by recent manpage changes

[Wilko Bulte]

On Fri, Oct 06, 2000 at 01:27:08PM -0700, Steve Kargl wrote:
 === joy
 install -C -c -o root -g wheel -m 555   joy.ko /boot/kernel
 install -C -c -o root -g wheel -m 444 joy.8.gz  /usr/share/man/man8
 install: joy.8.gz: No such file or directory
 *** Error code 71

Saw this 2 minutes ago too on alpha

-- 
Wilko Bulte  
[EMAIL PROTECTED]   Arnhem, the Netherlands


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make installkernel broken by recent manpage changes

[David O'Brien]

On Fri, Oct 06, 2000 at 01:27:08PM -0700, Steve Kargl wrote:
 === joy
 install -C -c -o root -g wheel -m 555   joy.ko /boot/kernel
 install -C -c -o root -g wheel -m 444 joy.8.gz  /usr/share/man/man8
 install: joy.8.gz: No such file or directory
 *** Error code 71

I'll check it out.
 
-- 
-- David  ([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

make installkernel broken by recent manpage changes

[Steve Kargl]

=== joy
install -C -c -o root -g wheel -m 555   joy.ko /boot/kernel
install -C -c -o root -g wheel -m 444 joy.8.gz  /usr/share/man/man8
install: joy.8.gz: No such file or directory
*** Error code 71


-- 
Steve


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Installkernel

[Mike Meyer]

James Johnson writes:
 The method of building and installing a kernel to me seems a bit off.. Both
 the buildworld and installworld targets default to GENERIC, yet GENERIC is a
 file checked into the -CURRENT CVS repository.. Any changes to this file
 will get blown away if whenever you update the sources unless you explicity
 exclude this file. No one I know runs BSD with a GENERIC kernel, they have
 specific requirements for the hardware in their machines. Having to specify
 which kernel to build with the KERNEL= parameter seems to indicate that
 people should be running GENERIC kernels all the time as it is the default.
 This just doesnt seem right.

Now that it's all working properly, I like it. I build for multiple
machines on one box, and then NFS-mount /usr/src  /usr/obj to do the
installs. Being able to build all the kernels with one command, and
use the same install commands on each box makes my life much simpler.

As for GENERIC, it's what people run by default, and it can be used as
is on much hardware. The documentation is a bit behind - the handbook
should mention setting KERNEL in /etc/make.conf when it talks about
buildkernel and installkernel.

mike


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Installkernel

[James Johnson]

Just a little usability observation(or I am too lazy to script_my_own_tools
and want to whine!)

The method of building and installing a kernel to me seems a bit off.. Both
the buildworld and installworld targets default to GENERIC, yet GENERIC is a
file checked into the -CURRENT CVS repository.. Any changes to this file
will get blown away if whenever you update the sources unless you explicity
exclude this file. No one I know runs BSD with a GENERIC kernel, they have
specific requirements for the hardware in their machines. Having to specify
which kernel to build with the KERNEL= parameter seems to indicate that
people should be running GENERIC kernels all the time as it is the default.
This just doesnt seem right.

I know a script could easily be written to grab a filename out of something
like /boot/loader.conf to get which kernel config file you want to use by
default.. Are there any plans to change this or is this method final?







To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Installkernel

[Scot W. Hetzel]

From: "James Johnson" [EMAIL PROTECTED]
 The method of building and installing a kernel to me seems a bit off.. Both
 the buildworld and installworld targets default to GENERIC, yet GENERIC is a
 file checked into the -CURRENT CVS repository.. Any changes to this file
 will get blown away if whenever you update the sources unless you explicity

Your supposed to copy GENERIC to a new name, and then build your kernel with that file.

You can change the default kernel to build by specifying:

KERNEL= MY-KERNEL

in the /etc/make.conf file.







To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Installkernel

[Ben Smithurst]

James Johnson wrote:

 Having to specify
 which kernel to build with the KERNEL= parameter seems to indicate that
 people should be running GENERIC kernels all the time as it is the default.

No, it seems to indicate that you should specify KERNEL=YOURKERNEL in
make.conf.

-- 
Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Minor problems with build/installkernel

[Johan Karlsson]

[current cc:ed since this might be interesting]

Hi Marcel
Can you please have a look at some PRs which deals with some minor problem
with the buldkernel/installkernel targets of Makefile.inc1 and the
install-modules target of sys/conf/Makefile.${MACHINE}

I think you are the right person for this since you have done most 
of the recent work with these targets.

PR 20325 http://www.freebsd.org/cgi/query-pr.cgi?pr=20325
If KERNEL=GENRIC is set in /etc/make.conf the build/installkernel
will create/install kernel as 'GENERIC'.

PR 20326 http://www.freebsd.org/cgi/query-pr.cgi?pr=20326
If DESTDIR=path_to_empty_dir installkernel will fail.

PR 20327 http://www.freebsd.org/cgi/query-pr.cgi?pr=20327
When backing-up modules ${KMODDIR} should be used instead of /modules


Thanks
Johan K



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Minor problems with build/installkernel

[Marcel Moolenaar]

Johan Karlsson wrote:
 
 Can you please have a look at some PRs which deals with some minor problem
 with the buldkernel/installkernel targets of Makefile.inc1 and the
 install-modules target of sys/conf/Makefile.${MACHINE}

I will. Thanks for the pointers,

-- 
Marcel Moolenaar
  mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
  tel:  (408) 447-4222


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

installkernel broken?

[Bill Fumerola]

A little context

CROSSENV=   MAKEOBJDIRPREFIX=${OBJTREE} \
COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \
LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \
OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \
PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.6.0
STRICTTMPPATH=  ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
INSTALLTMP= ${TMPDIR}/install.${TMPPID}
IMAKEENV=   ${CROSSENV} \
PATH=${STRICTTMPPATH}:${INSTALLTMP}

installkernel:
cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \
${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \
${MAKE} KERNEL=${INSTALLKERNEL} install


Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be
looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin...

Disgruntled and reverting back to making kernels the way they were intended,

-- 
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installkernel broken?

[Marcel Moolenaar]

Bill Fumerola wrote:

 STRICTTMPPATH=  ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
 INSTALLTMP= ${TMPDIR}/install.${TMPPID}
 IMAKEENV=   ${CROSSENV} \
 PATH=${STRICTTMPPATH}:${INSTALLTMP}
 
 installkernel:
 cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \
 ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \
 ${MAKE} KERNEL=${INSTALLKERNEL} install
 
 Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be
 looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin...

WORLDTMP is a place to *install* binaries we made during the build. We
don't install in /usr.bin or /usr.sbin; we install in /usr/bin and
/usr/sbin resp.

 Disgruntled and reverting back to making kernels the way they were intended,

So, what's broken then?

-- 
Marcel Moolenaar
  mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
  tel:  (408) 447-4222


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installkernel broken?

[Bill Fumerola]

On Wed, Jul 26, 2000 at 08:56:03AM -0700, Marcel Moolenaar wrote:

  Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be
  looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin...
 
 WORLDTMP is a place to *install* binaries we made during the build. We
 don't install in /usr.bin or /usr.sbin; we install in /usr/bin and
 /usr/sbin resp.

And then we try and install the kernel using those utilties that are in 
directories that don't exist:

crazyhorse# make kernel=GENERIC installkernel
cd /usr/obj/usr/src/sys/GENERIC;  MAKEOBJDIRPREFIX=/usr/obj  
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin  
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib  
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec  
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0  
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.1532
 MACHINE=i386 KERNEL=GENERIC  make KERNEL=GENERIC install
make: not found
*** Error code 127

crezyhorse# ls -l /usr/obj/usr/src/{,i386/}usr{.,/}{s,}bin/make/make
ls: /usr/obj/usr/src/i386/usr.bin/make: No such file or directory
ls: /usr/obj/usr/src/i386/usr.sbin/make: No such file or directory
ls: /usr/obj/usr/src/i386/usr/bin/make: No such file or directory
ls: /usr/obj/usr/src/i386/usr/sbin/make: No such file or directory
ls: /usr/obj/usr/src/usr.sbin/make: No such file or directory
ls: /usr/obj/usr/src/usr/bin/make: No such file or directory
ls: /usr/obj/usr/src/usr/sbin/make: No such file or directory
-rwxr-xr-x  1 root  wheel  112614 Jul 26 08:20 /usr/obj/usr/src/usr.bin/make/make

  Disgruntled and reverting back to making kernels the way they were intended,
 
 So, what's broken then?

Look where we define the PATH and look where I finally found make.
We seem to not be sticking it in the places we look to build with virgin
binaries.

-- 
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installkernel broken?

[Marcel Moolenaar]

Bill Fumerola wrote:
 
  WORLDTMP is a place to *install* binaries we made during the build. We
  don't install in /usr.bin or /usr.sbin; we install in /usr/bin and
  /usr/sbin resp.
 
 And then we try and install the kernel using those utilties that are in
 directories that don't exist:
 
 crazyhorse# make kernel=GENERIC installkernel
 cd /usr/obj/usr/src/sys/GENERIC;  MAKEOBJDIRPREFIX=/usr/obj  
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin  
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib  
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec  
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0  
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.1532
 MACHINE=i386 KERNEL=GENERIC  make KERNEL=GENERIC install
 make: not found
 *** Error code 127

Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The
installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV
was changed to have the very restricted path that broke the
installkernel target as you describe above. This has been fixed in
1.162.

-- 
Marcel Moolenaar
  mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
  tel:  (408) 447-4222


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: installkernel broken?

[Bill Fumerola]

On Wed, Jul 26, 2000 at 10:02:40AM -0700, Marcel Moolenaar wrote:

 Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The
 installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV
 was changed to have the very restricted path that broke the
 installkernel target as you describe above. This has been fixed in
 1.162.

okay. I'm going to go find who made our local cvsup mirror stop
mirroring and feed them to the paper shredder.

thanks.

-- 
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

make installkernel broken ? (was Re: World broken)

[Salvo Bartolotta]

 Original Message 

On 7/23/00, 7:19:03 AM, Warner Losh [EMAIL PROTECTED] wrote regarding 
World broken:


 cc -O -pipe -DMD5 -DSHA1 -DRMD160   
-I/usr/obj/home/imp/FreeBSD/src/i386/usr/include  -o mtree compare.o 
crc.o create.o excludes.o misc.o mtree.o spec.o verify.o  -lmd
 misc.o: In function `flags_to_string':
 misc.o(.text+0x89): undefined reference to `fflagstostr'
 spec.o: In function `set':
 spec.o(.text+0x5f5): undefined reference to `strtofflags'
 *** Error code 1

 I'm kludging mtree so that make buildworld isn't broken.  Don't remove
 the kludge until such time as the underlying problems have been
 corrected.



Dear FreeBSd'ers,

The good news: I have just made buildworld (sources cvsup'ed today), 
and made buildkernel with no problems.

The (moderately) bad news: make installkernel fails:

/usr/src #  make installkernel

cd /usr/obj/usr/src/sys/GENERIC;  MAKEOBJDIRPREFIX=/usr/obj  
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386
/usr/bin  
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/
lib  OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec  
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0  
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/us
r/obj/usr/src/i386/usr/games:/tmp/install.12899 MACHINE=i386 
KERNEL=GENERIC  make KERNEL=GENERIC install
make: not found
*** Error code 127

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.



It is a few weeks since I last made a -CURRENT world, so I have been 
cautious enough, and I have chosen the buildkernel and installkernel 
targets -- as if I were updating from -STABLE.

Since I am already well "flamed" (~ 35/40 °C down here), please be so 
kind as not to flame me :-) 

Best regards,
Salvo





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make installkernel broken ? (was Re: World broken)

[Marcel Moolenaar]

Salvo Bartolotta wrote:
 
 Dear FreeBSd'ers,
 
 The good news: I have just made buildworld (sources cvsup'ed today),
 and made buildkernel with no problems.
 
 The (moderately) bad news: make installkernel fails:

Already fixed. Please re-cvsup. Note that the kernel will be called
'kernel' (again)! If you used the installkernel before and have modified
your /boot/loader.conf, make sure it's booting /kernel again.

HTH,

-- 
Marcel Moolenaar
  mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
  tel:  (408) 447-4222


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message