Resolved (was: Re: Problem (re)building graphics/drm-61-kmod via PORTS_MODULES+=)

sing PORTS_MODULES+=graphics/drm-61-kmod in /etc/src.conf. Peace, david -- David H. Wolfskill da...@catwhisker.org It has been said that history repeats itself. This is perhaps not quite correct; it merely rhymes. -- Theodor Reik See https://www.catwhisker.org/~d

Re: Problem (re)building graphics/drm-61-kmod via PORTS_MODULES+=

Or maybe the port just insists on building linuxkpi_video: --- video_kmod.o --- cc: error: no such include directory: '/usr/ports/graphics/drm-61-kmod/work/drm-kmod-drm_v6.1.92_1/linuxkpi/dummy/include' [-Werror,-Wmissing-include-dirs] --- aperture.o --- cc: error: no such include directory: '/usr/

Re: Problem (re)building graphics/drm-61-kmod via PORTS_MODULES+=

Building either linuxkpi or linuxkpi_video from https://github.com/freebsd/drm-kmod.git is not necessary if I want functioning intel graphics, but the port version insists on building those unnecessary things. On Fri, Oct 25, 2024 at 6:10 PM Oleg Lelchuk wrote: > With clang 19, I can build i1915

Re: Problem (re)building graphics/drm-61-kmod via PORTS_MODULES+=

With clang 19, I can build i1915kms from https://github.com/freebsd/drm-kmod.git and I won't encounter any issues. However, with the port version of drm-61-kmod, I would still encounter an error. I think this happens because the port wants to build stuff in the linuxkpi_video directory, but with th

Re: Problem (re)building graphics/drm-61-kmod via PORTS_MODULES+=

On Fri, Oct 25, 2024 at 09:20:16AM +0200, Robert Clausecker wrote: > Hi David, > ... > The same issue was reported in another thread. Try this workaround: Aye; saw that, tried it, and it works for me (modulo MUA-mangling of whitespace). Here's a representation of what I used: diff --git a/grap

Re: Problem (re)building graphics/drm-61-kmod via PORTS_MODULES+=

generally, the > simplest way to ensure that that is done is to augment /etc/src.conf > with (e.g.): > > PORTS_MODULES+=graphics/drm-61-kmod > > which (again, generally) works a treat. :-) > > It even worked Just Fine yesterday (main-n273108-d1d839d0b593 -> > main-n2731

Problem (re)building graphics/drm-61-kmod via PORTS_MODULES+=

(e.g.): PORTS_MODULES+=graphics/drm-61-kmod which (again, generally) works a treat. :-) It even worked Just Fine yesterday (main-n273108-d1d839d0b593 -> main-n273133-419249c1cacc). This morning, however, after updating sources to main-n273188-1c83996beda7, running: g1-48(15.0-C)[12] uname -aUK FreeB

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: PORTS_MODULES fails with beinstall.sh

> > Hello all, > > > > I'm trying make.conf PORTS_MODULES=x11/nvidia-driver and it fails with > > beinstall.sh: > > --- > > [...] > > cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env -u CC -u CXX -u CPP > > -u MAKESYSPATH -u MK_AUTO_OBJ -u

Re: PORTS_MODULES fails with beinstall.sh

On Tue, 7 Mar 2023 13:47:53 + Nuno Teixeira wrote: > Hello all, > > I'm trying make.conf PORTS_MODULES=x11/nvidia-driver and it fails with > beinstall.sh: > --- > [...] > cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env -u CC -u CXX -u CPP > -u MA

PORTS_MODULES fails with beinstall.sh

Hello all, I'm trying make.conf PORTS_MODULES=x11/nvidia-driver and it fails with beinstall.sh: --- ===> Ports module x11/nvidia-driver (install) cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env -u CC -u CXX -u CPP -u MAKESYSPATH -u MK_AUTO_OBJ -u MAKEOBJDIR MAKEFLAGS="

Re: buildkernel doesn't respect PORTSDIR with PORTS_MODULES

Juraj Lutter wrote: > > >> On 24 Nov 2022, at 15:16, Juraj Lutter wrote: >>> >>> bsd.port.mk and bsd.port.subdir.mk use _PORTSDIR. You could try adding >>> that to your list. >>> >> >> PORTS_MODULES are being built from within ker

Re: buildkernel doesn't respect PORTSDIR with PORTS_MODULES

> On 24 Nov 2022, at 15:16, Juraj Lutter wrote: >> >> bsd.port.mk and bsd.port.subdir.mk use _PORTSDIR. You could try adding >> that to your list. >> > > PORTS_MODULES are being built from within kern.post.mk. I’d put PORTSDIR into > src-env.conf instea

Re: buildkernel doesn't respect PORTSDIR with PORTS_MODULES

> On 24 Nov 2022, at 15:05, Gary Jennejohn wrote: > > On Thu, 24 Nov 2022 12:02:35 + > Nuno Teixeira wrote: > >> Hello, >> >> I'm trying PORT_MODULES with make.conf: >> --- >> PORTSDIR=/work/freebsd/ports >> DISTDIR=/work/DISTFI

Re: buildkernel doesn't respect PORTSDIR with PORTS_MODULES

On Thu, 24 Nov 2022 12:02:35 + Nuno Teixeira wrote: > Hello, > > I'm trying PORT_MODULES with make.conf: > --- > PORTSDIR=/work/freebsd/ports > DISTDIR=/work/DISTFILES > PORTS_MODULES=graphics/drm-kmod x11/nvidia-driver > --- > and `make buildkernel` fa

buildkernel doesn't respect PORTSDIR with PORTS_MODULES

Hello, I'm trying PORT_MODULES with make.conf: --- PORTSDIR=/work/freebsd/ports DISTDIR=/work/DISTFILES PORTS_MODULES=graphics/drm-kmod x11/nvidia-driver --- and `make buildkernel` fails: --- linking kernel.full ctfmerge -L VERSION -g -o kernel.full ... text data bss

Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

On 12/13/20 12:25 PM, John Kennedy wrote: On Sun, Dec 13, 2020 at 08:19:30AM +, Graham Perrin wrote: Please: is there some way to include openzfs-kmod at buildkernel time? Not that I'm aware of, but you can write a script to build your system the way you like it and then build the kmod

Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

On Sun, Dec 13, 2020 at 06:49:07PM +, Graham Perrin wrote: > Not entirely moot; for > the description for > the most recent commit refers to building on 13-CURRENT Well, it's a port, so they'll want it to compile if nothing else. It just n

Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

On 13/12/2020 17:25, John Kennedy wrote: On Sun, Dec 13, 2020 at 08:19:30AM +, Graham Perrin wrote: Please: is there some way to include openzfs-kmod at buildkernel time? To work around I habitually remove openzfs-kmod from /etc/src

Re: (239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

On Sun, Dec 13, 2020 at 08:19:30AM +, Graham Perrin wrote: > Please: is there some way to include openzfs-kmod at buildkernel time? > > To work around > I habitually > remove openzfs-kmod from /etc/src.conf _and_ modify /boot/loader.

(239489) buildkernel fails if PORTS_MODULES= includes openzfs-kmod

Please: is there some way to include openzfs-kmod at buildkernel time? To work around I habitually remove openzfs-kmod from /etc/src.conf _and_ modify /boot/loader.conf before performing the build: zfs_load="YES" openzfs_load="NO" _

PORTS_MODULES if you built head between r359681 - r359690

TL;DR: You may want to take evasive action, such as manually copying the r359690 (or later) from src/share/mk/bsd.sys.mk to /usr/share/mk/bsd.sys.mk before attempting to make use of the PORTS_MODULES specificsation if the current version of /usr/share/mk/bsd.sys.mk is from r359681. Details

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

d installing kernel fails with >>>>>>> the error "Variable OBJTOP is recursive." when going to build/install >>>>>>> module from ports. >>>>>>> >>>>>>> Last successful build was at r328426. Next build at r328

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

e OBJTOP is recursive." when going to build/install > >>>>> module from ports. > >>>>> > >>>>> Last successful build was at r328426. Next build at r328527 failed and > >>>>> still broken at r328649. > >>>>> >

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

On Tue, Feb 13, 2018 at 6:02 AM, David Wolfskill wrote: > On Tue, Feb 13, 2018 at 12:48:19PM +0300, Vladimir Zakharov wrote: >> >> > > It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. >> > > At least, removing it fixes build for me. > > FWIW, I have never specified WITH_A

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

>>>>> >>>>> Last successful build was at r328426. Next build at r328527 failed and >>>>> still broken at r328649. >>>>> >>>>> Without PORTS_MODULES building and installing kernel succeeds. Another >>>>> work

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

On Tue, Feb 13, 2018 at 12:48:19PM +0300, Vladimir Zakharov wrote: > > > > It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. > > > At least, removing it fixes build for me. FWIW, I have never specified WITH_AUTO_OBJ -- and I do encounter the "Variable OBJTOP is recursive"

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

t;> For some time (about a week) building and installing kernel fails with > >>> the error "Variable OBJTOP is recursive." when going to build/install > >>> module from ports. > >>> > >>> Last successful build was at r328426. Next build at

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

gt;>> the error "Variable OBJTOP is recursive." when going to build/install >>> module from ports. >>> >>> Last successful build was at r328426. Next build at r328527 failed and >>> still broken at r328649. >>> >>> Without PORTS_MODU

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

o build/install > > module from ports. > > > > Last successful build was at r328426. Next build at r328527 failed and > > still broken at r328649. > > > > Without PORTS_MODULES building and installing kernel succeeds. Another > > workaround: ignore er

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

6. Next build at r328527 failed and > still broken at r328649. > > Without PORTS_MODULES building and installing kernel succeeds. Another > workaround: ignore error and build/install module directly from ports. > > # cat /etc/make.conf > MALLOC_PRODUCTION=yes > KERNCO

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

fails with > > > > > the error "Variable OBJTOP is recursive." when going to build/install > > > > > module from ports. > > > > > > > > > > Last successful build was at r328426. Next build at r328527 failed and > > > > > s

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

; > module from ports. > > > > > > > > Last successful build was at r328426. Next build at r328527 failed and > > > > still broken at r328649. > > > > > > > > Without PORTS_MODULES building and installing kernel succeeds. Another >

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

bout a week) building and installing kernel fails with > > > the error "Variable OBJTOP is recursive." when going to build/install > > > module from ports. > > > > > > Last successful build was at r328426. Next build at r328527 failed and > > >

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

ecursive." when going to build/install > > module from ports. > > > > Last successful build was at r328426. Next build at r328527 failed and > > still broken at r328649. > > > > Without PORTS_MODULES building and installing kernel succeeds. Another > > workar

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

d was at r328426. Next build at r328527 failed and > still broken at r328649. > > Without PORTS_MODULES building and installing kernel succeeds. Another > workaround: ignore error and build/install module directly from ports. > > # cat /etc/make.conf > MALLOC_PRODUCTION=yes >

buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

Hello! For some time (about a week) building and installing kernel fails with the error "Variable OBJTOP is recursive." when going to build/install module from ports. Last successful build was at r328426. Next build at r328527 failed and still broken at r328649. Without PORTS_MODULE

Re: PORTS_MODULES breakage on HEAD

On 12 Aug, Bryan Drewery wrote: > On 8/10/2016 4:20 PM, Bryan Drewery wrote: >> On 8/7/16 5:44 PM, Don Lewis wrote: >>> Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on >>> HEAD. When I do that I get this failure: >>> >>> ===>

Re: PORTS_MODULES breakage on HEAD

On 8/10/2016 4:20 PM, Bryan Drewery wrote: > On 8/7/16 5:44 PM, Don Lewis wrote: >> Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on >> HEAD. When I do that I get this failure: >> >> ===> Ports module emulators/virtualbox-ose-kmod (all) >>

Re: PORTS_MODULES breakage on HEAD

On 8/7/16 5:44 PM, Don Lewis wrote: > Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on > HEAD. When I do that I get this failure: > > ===> Ports module emulators/virtualbox-ose-kmod (all) > cd ${PORTSDIR:-/usr/ports}/emulators/virtualbox-ose-kmod; >

Re: PORTS_MODULES breakage on HEAD

On Sun, Aug 7, 2016 at 5:44 PM, Don Lewis wrote: > Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on > HEAD. When I do that I get this failure: > > ===> Ports module emulators/virtualbox-ose-kmod (all) > cd ${PORTSDIR:-/usr/ports}/emulators/virtualbox-ose

PORTS_MODULES breakage on HEAD

Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on HEAD. When I do that I get this failure: ===> Ports module emulators/virtualbox-ose-kmod (all) cd ${PORTSDIR:-/usr/ports}/emulators/virtualbox-ose-kmod; PATH=/usr/obj/usr/src/ tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/

Re: PORTS_MODULES

On Mon, Jun 18, 2012 at 12:40 AM, Daniel Braniss wrote: >> Howdy, >> >> This is an FYI to let people know about a really nice feature for those >> that have ports installed which include kernel modules. You can place a >> list in /etc/src.conf like this: >> >

Re: PORTS_MODULES

> Howdy, > > This is an FYI to let people know about a really nice feature for those > that have ports installed which include kernel modules. You can place a > list in /etc/src.conf like this: > > PORTS_MODULES= emulators/virtualbox-ose-kmod sysutils/fusefs-kmod > x11/

Re: PORTS_MODULES fix

On 06/09/2012 16:51, Doug Barton wrote: > Ok, never mind the last one ... this patch I've actually tested. :) Committed to HEAD and MFC'ed. Thanks everyone for the feedback and help. Doug -- This .signature sanitized for your protection ___ fre

PORTS_MODULES

Howdy, This is an FYI to let people know about a really nice feature for those that have ports installed which include kernel modules. You can place a list in /etc/src.conf like this: PORTS_MODULES= emulators/virtualbox-ose-kmod sysutils/fusefs-kmod x11/nvidia-driver which will cause those

Re: PORTS_MODULES fix

On Jun 9, 2012, at 4:51 PM, Doug Barton wrote: > Ok, never mind the last one ... this patch I've actually tested. :) This one looks good :) (and fixes the item I briefly mentioned in IRC); I'll test it one out. Thanks! -Garrett___ freebsd-curre

Re: PORTS_MODULES fix

rking copy) @@ -36,9 +36,30 @@ .endif .endfor -# Handle out of tree ports +# Handle ports (as defined by the user) that build kernel modules .if !defined(NO_MODULES) && defined(PORTS_MODULES) -PORTSMODULESENV=SYSDIR=${SYSDIR} +# +# The ports tree needs some environment variables defined

Re: PORTS_MODULES fix

revision 236818) +++ kern.post.mk(working copy) @@ -36,9 +36,30 @@ .endif .endfor -# Handle out of tree ports +# Handle ports (as defined by the user) that build kernel modules .if !defined(NO_MODULES) && defined(PORTS_MODULES) -PORTSMODULESENV=SYSDIR=${SYSDIR} +# +# Th

Re: PORTS_MODULES fix

On Sat, Jun 9, 2012 at 11:06 AM, Doug Barton wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On 06/09/2012 10:40, Matthew Seaman wrote: >> On 09/06/2012 18:26, Chris Rees wrote: >>> On 9 June 2012 18:15, Doug Barton wrote: >>>> I have rec

Re: PORTS_MODULES fix

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On 06/09/2012 10:40, Matthew Seaman wrote: > On 09/06/2012 18:26, Chris Rees wrote: >> On 9 June 2012 18:15, Doug Barton wrote: >>> I have recently tried the PORTS_MODULES knob, and found a >>> problem. The p

Re: PORTS_MODULES fix

On 09/06/2012 18:26, Chris Rees wrote: > On 9 June 2012 18:15, Doug Barton wrote: >> I have recently tried the PORTS_MODULES knob, and found a problem. The >> ports tree searches for some dependencies by finding a binary in PATH, >> and that fails since by default /usr/lo

Re: PORTS_MODULES fix

On 9 June 2012 18:15, Doug Barton wrote: > I have recently tried the PORTS_MODULES knob, and found a problem. The > ports tree searches for some dependencies by finding a binary in PATH, > and that fails since by default /usr/local/ isn't there. The attached > patch fixes tha

PORTS_MODULES fix

I have recently tried the PORTS_MODULES knob, and found a problem. The ports tree searches for some dependencies by finding a binary in PATH, and that fails since by default /usr/local/ isn't there. The attached patch fixes that problem. It would be more robust to use PREFIX there instead of