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

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

Re: Error during installkernel

tem 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

Re: Error during installkernel

* 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

Error during installkernel

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 fai

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

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

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

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

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

t; > >> >> 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 aft

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

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: &

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

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/kerne

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

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 inst

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

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

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

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

Re: installkernel ignoring WITHOUT_DEBUG_FILES?

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

Re: installkernel ignoring WITHOUT_DEBUG_FILES?

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 &

installkernel ignoring WITHOUT_DEBUG_FILES?

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

Re: impossible to installkernel without a compiler?

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.

Re: impossible to installkernel without a compiler?

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. --

Re: impossible to installkernel without a compiler?

-- > >>> Install check kernel > -- > -- > >>> Installing kernel KERNEL on Wed May 22 08:00:33 UTC 2019 > ----

Re: impossible to installkernel without a compiler?

---- > >>> 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. > > -- >

impossible to installkernel without a compiler?

t;>> 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@freebs

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

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 > inst

Fatal trap 9 when rebooting after installkernel on VirtualBox VM

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

r334236 error installkernel (i386)

===> 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

installkernel error WITHOUT_BLUETOOTH

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? >>>>>&

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

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&qu

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

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/o

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

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 >

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

> 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.

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

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"

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

b.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/

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

> /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 a

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

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/ handli

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

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 sim

ZSF and installkernel 10.0-BETA1

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

Re: ZSF and installkernel 10.0-BETA1

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

[make installworld installkernel] does not honor break at installworld

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

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

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

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

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

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

Re: problem after installkernel going from 9.0 to CURRENT

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

Re: problem after installkernel going from 9.0 to CURRENT

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

Re: problem after installkernel going from 9.0 to CURRENT

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

Re: problem after installkernel going from 9.0 to CURRENT

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

Re: problem after installkernel going from 9.0 to CURRENT

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 # Device

SOLVED: problem after installkernel going from 9.0 to CURRENT

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

Re: problem after installkernel going from 9.0 to CURRENT

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

problem after installkernel going from 9.0 to CURRENT

(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

Re: problem after installkernel going from 9.0 to CURRENT

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

Re: problem after installkernel going from 9.0 to CURRENT

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

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

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

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

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

MAKEOBJDIRPREFIX and installkernel

: 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

Re: MAKEOBJDIRPREFIX and installkernel

/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

Re: MAKEOBJDIRPREFIX and installkernel

May 2010) [~]b...@izar% echo $MAKEOBJDIRPREFIX /home/bsam/FreeBSD/base/head/obj [~]b...@izar% sudo make -C FreeBSD/base/head/src installkernel -- Installing kernel

installkernel broken - if.wi.ko

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

Re: installkernel broken - if.wi.ko

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

make installkernel fails

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

Re: make DESTDIR=foo failing in installkernel ?

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.

Re: make DESTDIR=foo failing in installkernel ?

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

make DESTDIR=foo failing in installkernel ?

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

Re: make DESTDIR=foo failing in installkernel ?

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

Re: make installkernel broken by recent manpage changes

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

Re: make installkernel broken by recent manpage changes

=== 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

Re: make installkernel broken by recent manpage changes

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

Re: make installkernel broken by recent manpage changes

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. -- --

make installkernel broken by recent manpage changes

=== 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

Installkernel

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

Installkernel

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..

Re: Installkernel

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

Re: Installkernel

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 /

Minor problems with build/installkernel

[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

Re: Minor problems with build/installkernel

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

installkernel broken?

\ 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

Re: installkernel broken?

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

Re: installkernel broken?

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

Re: installkernel broken?

: 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

Re: installkernel broken?

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

make installkernel broken ? (was Re: World broken)

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

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

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