Re: Kernel build broken without "options KTRACE"

2024-03-08 Thread Mark Johnston
On Wed, Mar 06, 2024 at 10:51:05AM -0700, John Nielsen wrote: > Getting a set but not used warning for “td” in sys/kern/kern_condvar.c when > doing a buildkernel for a config file without “options KTRACE”. I failed to > copy the full error message/line numbers but I will reproduce this evening if

Kernel build broken without "options KTRACE"

2024-03-06 Thread John Nielsen
Getting a set but not used warning for “td” in sys/kern/kern_condvar.c when doing a buildkernel for a config file without “options KTRACE”. I failed to copy the full error message/line numbers but I will reproduce this evening if needed. JN

Re: 15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Rainer Hurling
Am 10.09.23 um 05:18 schrieb Dag-Erling Smørgrav: Rainer Hurling writes: Unfortunately, here it breaks with: [...] /usr/src/lib/libc/gdtoa/machdep_ldisx.c:40:10: fatal error: 'sys/cdefs.h' file not found That's because you wiped /usr/obj before starting. Try running 'make buildincludes' ins

Re: 15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Dag-Erling Smørgrav
Rainer Hurling writes: > Unfortunately, here it breaks with: > [...] > /usr/src/lib/libc/gdtoa/machdep_ldisx.c:40:10: fatal error: 'sys/cdefs.h' > file not found That's because you wiped /usr/obj before starting. Try running 'make buildincludes' inside the buildenv before building libc. If tha

Re: 15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Rainer Hurling
Am 09.09.23 um 20:28 schrieb Dag-Erling Smørgrav: Rainer Hurling writes: After removing /usr/obj and 'make cleanworld', That was unnecessary. I tried to build libc like the following, but it fails: [...] $ cd /usr/src $ make buildenv done inside the buildenv, run: $ make -C lib/libc

Re: 15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Dag-Erling Smørgrav
Rainer Hurling writes: > After removing /usr/obj and 'make cleanworld', That was unnecessary. > I tried to build libc like the following, but it fails: > [...] $ cd /usr/src $ make buildenv inside the buildenv, run: $ make -C lib/libc -j$(nproc) then exit the buildenv and run $ sudo make -C

Re: 15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Rainer Hurling
Am 09.09.23 um 19:04 schrieb Dag-Erling Smørgrav: Rainer Hurling writes: If I try to build world from todays c1b26df2972d with 15.0-CURRENT (main-n265063-e0752f431b01), it aborts with an error. Either update your source tree or apply aca3bd160257, then build and install libc before attempting

Re: 15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Dag-Erling Smørgrav
Rainer Hurling writes: > If I try to build world from todays c1b26df2972d with 15.0-CURRENT > (main-n265063-e0752f431b01), it aborts with an error. Either update your source tree or apply aca3bd160257, then build and install libc before attempting buildworld. DES -- Dag-Erling Smørgrav - d...@f

Re: 15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Rainer Hurling
Just an update. This also happens in Poudriere, when I try to update my jails for 13.2, 14.0 and 15.0-CURRENT. It seems, that my installed version of 15.0-CURRENT (main-n265063-e0752f431b01) is the culprit :( Am 09.09.23 um 13:52 schrieb Rainer Hurling: If I try to build world from todays

15.0-CURRENT build broken in lib/libmagic

2023-09-09 Thread Rainer Hurling
If I try to build world from todays c1b26df2972d with 15.0-CURRENT (main-n265063-e0752f431b01), it aborts with an error. Seems it is not able to handle line 4979 of the magic file (Microsoft Advanced Streaming Format ASF): ===> lib/libmagic (all) echo libmagic.so.4: /usr/obj/usr/src/amd64.am

Re: aaarch64 main 9a3583bfbd17 debug build broken (race?): "clri.lo: No such file or directory" so "make[4]: stopped in /usr/main-src/rescue/rescue"

2022-05-03 Thread Mark Millard
[Looks to be some form of build race.] On 2022-May-3, at 15:38, Mark Millard wrote: > # ~/fbsd-based-on-what-commit.sh -C /usr/main-src/ > branch: main > merge-base: 9a3583bfbd1740a158b3916432286190e0f2bf60 > merge-base: CommitDate: 2022-05-03 19:12:42 + > 9a3583bfbd17 (HEAD -> main, freebsd

aaarch64 main 9a3583bfbd17 debug build broken: "clri.lo: No such file or directory" so "make[4]: stopped in /usr/main-src/rescue/rescue"

2022-05-03 Thread Mark Millard
# ~/fbsd-based-on-what-commit.sh -C /usr/main-src/ branch: main merge-base: 9a3583bfbd1740a158b3916432286190e0f2bf60 merge-base: CommitDate: 2022-05-03 19:12:42 + 9a3583bfbd17 (HEAD -> main, freebsd/main, freebsd/HEAD) OpenSSL: Merge OpenSSL 1.1.1o n255160 (--first-parent --count for merge-bas

tools/toos/{zfsboottest|bootparttest} build broken

2021-01-26 Thread Sergey V. Dyatko
Hi, root@hostname:/usr/src/tools/tools/bootparttest # make [Creating objdir /usr/obj/usr/src/amd64.amd64/tools/tools/bootparttest...] make: don't know how to make crc32.c. Stop make: stopped in /usr/src/tools/tools/bootparttest root@hostname:/usr/src/tools/tools/zfsboottest # make ln -sf /usr/s

Re: Current kernel build broken with linuxkpi?

2021-01-19 Thread Evilham
On dc., gen. 13 2021, David Wolfskill wrote: On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote: Hans Petter Selasky : > You need to update that DRM port you are using before the > issue > will be fixed. I'm confused. I have drm-current-kmod listed in PORTS_MODULE

Re: Current kernel build broken with linuxkpi?

2021-01-16 Thread Robert Huff
And ... we have a winner. (So far.) The system in question has 11+ hours uptime running: FreeBSD 13.0-ALPHA1 #1 main-c1149-g79a5c790bd: Sat Jan 16 09:02:47 EST 2021 amd64 (Now rebuilding 1100+ ports ) I commented out the IGNORE line from drm-current-kmod;

Re: Current kernel build broken with linuxkpi?

2021-01-15 Thread Robert Huff
Yesterday I typod: > So, yes as I believe I said buildkernel ran successfully. Please make that: So, yes as I believe I said buildworld ran successfully. [Whack! Whack! Whack!] Respectfully, Rober

Re: Current kernel build broken with linuxkpi?

2021-01-14 Thread Robert Huff
Greg writes: > also, did you upgrade the world? > The version stuff that ports checks comes from /usr/include. I follow the process specified at the end of UPDATING. So, yes as I believe I said buildkernel ran successfully. Respectfully,

Re: Current kernel build broken with linuxkpi?

2021-01-14 Thread Greg V
On Thu, Jan 14, 2021 at 08:36, Robert Huff wrote: Hello: > I am trying to upgrade a system running: > > FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64 > > Per this discussion, I cannot compile the kernel because > drm-current-kmod is

Re: Current kernel build broken with linuxkpi?

2021-01-14 Thread Robert Huff
Hello: > > I am trying to upgrade a system running: > > > > FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64 > > > > Per this discussion, I cannot compile the kernel because > > drm-current-kmod is out-of-date. > > When I try to upgrade drm-current-kmod (r

Re: Current kernel build broken with linuxkpi?

2021-01-14 Thread Greg V
On Thu, Jan 14, 2021 at 08:05, Robert Huff wrote: "Houston ... we have a problem." Scenario: Chicken, meet egg? I am trying to upgrade a system running: FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64 Per this discussion, I cannot compile

Re: Current kernel build broken with linuxkpi?

2021-01-14 Thread Robert Huff
"Houston ... we have a problem." Scenario: Chicken, meet egg? I am trying to upgrade a system running: FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64 Per this discussion, I cannot compile the kernel because drm-current-kmod is out-of-date.

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Robert Huff
Chris writes: > >> Further: if I have that set ... does that mean I can > >> remove it from PORTS_MODULES? > > > > I don't know what that is > eg; > PORTS_MODULES=x11/nvidia-driver-304 > for the nvidia driver, for example. see src.conf(5). Actually make.conf(5).

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Chris
On 2021-01-13 13:28, Emmanuel Vadot wrote: On Wed, 13 Jan 2021 16:19:09 -0500 Robert Huff wrote: Emmanuel Vadot writes: >That's one of the problems of having external kmods. >drm-current-kmod have the option by default to install it's > sources in /usr/local/sys/ and when doing a

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Emmanuel Vadot
On Wed, 13 Jan 2021 16:19:09 -0500 Robert Huff wrote: > > Emmanuel Vadot writes: > > > That's one of the problems of having external kmods. > > drm-current-kmod have the option by default to install it's > > sources in /usr/local/sys/ and when doing a make buildkernel > > those sou

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Robert Huff
Emmanuel Vadot writes: > That's one of the problems of having external kmods. > drm-current-kmod have the option by default to install it's > sources in /usr/local/sys/ and when doing a make buildkernel > those sources are getting built too. That would be the SOURCE opt

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Emmanuel Vadot
On Wed, 13 Jan 2021 14:52:32 -0500 Robert Huff wrote: > > Hans Petter Selasky : > > > You need to update that DRM port you are using before the issue > > will be fixed. > > I'm confused. > I have drm-current-kmod listed in PORTS_MODULES; things on that > list get built _after_

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread David Wolfskill
On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote: > > Hans Petter Selasky : > > > You need to update that DRM port you are using before the issue > > will be fixed. > > I'm confused. > I have drm-current-kmod listed in PORTS_MODULES; things on that > list get built _af

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Robert Huff
Hans Petter Selasky : > You need to update that DRM port you are using before the issue > will be fixed. I'm confused. I have drm-current-kmod listed in PORTS_MODULES; things on that list get built _after_ buildkernel (installkernel??) for reasons I thought I understood.

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Santiago Martinez
Hi HPS! thanks, that solved the issue. sorry dint realize i had to recompile the drm. Cheers Santi On 1/13/21 2:45 PM, Hans Petter Selasky wrote: > On 1/13/21 3:42 PM, Hans Petter Selasky wrote: >> On 1/13/21 3:40 PM, Santiago Martinez wrote: >>> Thanks Peter,  this is what i got >>> >>> root@t

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Hans Petter Selasky
On 1/13/21 3:42 PM, Hans Petter Selasky wrote: On 1/13/21 3:40 PM, Santiago Martinez wrote: Thanks Peter,  this is what i got root@tucho:/usr/src # git status On branch main Your branch is up to date with 'origin/main'. am i missing something? portsnap fetch update You need to update that

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Hans Petter Selasky
On 1/13/21 3:40 PM, Santiago Martinez wrote: Thanks Peter,  this is what i got root@tucho:/usr/src # git status On branch main Your branch is up to date with 'origin/main'. am i missing something? portsnap fetch update Maybe? --HPS ___ freebsd-cu

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Santiago Martinez
Thanks Peter,  this is what i got root@tucho:/usr/src # git status On branch main Your branch is up to date with 'origin/main'. am i missing something? Santi On 1/13/21 2:34 PM, Hans Petter Selasky wrote: > On 1/13/21 3:31 PM, Santiago Martinez wrote: >> Hi there, >> >> Just wondering if someb

Re: Current kernel build broken with linuxkpi?

2021-01-13 Thread Hans Petter Selasky
On 1/13/21 3:31 PM, Santiago Martinez wrote: Hi there, Just wondering if somebody else is having issues building the kernel (amd64) with the latest current. I have tried with clean,  etc and same issue. Uploaded the make output into "pastebin.com" https://pastebin.com/va5HCYtY Try to updat

Current kernel build broken with linuxkpi?

2021-01-13 Thread Santiago Martinez
Hi there, Just wondering if somebody else is having issues building the kernel  (amd64) with the latest current. I have tried with clean,  etc and same issue. Uploaded the make output into "pastebin.com" https://pastebin.com/va5HCYtY Thanks Santi OpenPGP_signature Description: OpenPGP d

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-05 Thread Gleb Smirnoff
On Tue, Nov 05, 2013 at 01:40:17PM -0700, Ian Lepore wrote: I> On Tue, 2013-11-05 at 19:12 +0400, Gleb Smirnoff wrote: I> > On Tue, Nov 05, 2013 at 08:00:52AM -0700, Ian Lepore wrote: I> > I> > I> You were just unlucky that your updates bracketed my checkin that I> > I> > I> changed the build proce

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-05 Thread Ian Lepore
On Tue, 2013-11-05 at 19:12 +0400, Gleb Smirnoff wrote: > On Tue, Nov 05, 2013 at 08:00:52AM -0700, Ian Lepore wrote: > I> > I> You were just unlucky that your updates bracketed my checkin that > I> > I> changed the build process for the aicasm tool so that it gets built as > I> > I> part of the to

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-05 Thread Brooks Davis
On Tue, Nov 05, 2013 at 08:00:52AM -0700, Ian Lepore wrote: > On Tue, 2013-11-05 at 11:01 +0400, Gleb Smirnoff wrote: > > On Mon, Nov 04, 2013 at 10:09:54PM -0700, Ian Lepore wrote: > > I> > > /usr/src/sys/dev/aic7xxx/aic7xxx.seq > > I> > > > make[2]: exec(aicasm) failed (No such file or directory)

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-05 Thread Gleb Smirnoff
On Tue, Nov 05, 2013 at 08:00:52AM -0700, Ian Lepore wrote: I> > I> You were just unlucky that your updates bracketed my checkin that I> > I> changed the build process for the aicasm tool so that it gets built as I> > I> part of the toolchain rather than as part of the kernel now. I> > I> > Before

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-05 Thread Ian Lepore
On Tue, 2013-11-05 at 11:01 +0400, Gleb Smirnoff wrote: > On Mon, Nov 04, 2013 at 10:09:54PM -0700, Ian Lepore wrote: > I> > > /usr/src/sys/dev/aic7xxx/aic7xxx.seq > I> > > > make[2]: exec(aicasm) failed (No such file or directory) > I> > > > *** Error code 1 > I> > > > > I> > > > Stop. > I> > > >

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-05 Thread Outback Dingo
On Tue, Nov 5, 2013 at 2:01 AM, Gleb Smirnoff wrote: > On Mon, Nov 04, 2013 at 10:09:54PM -0700, Ian Lepore wrote: > I> > > /usr/src/sys/dev/aic7xxx/aic7xxx.seq > I> > > > make[2]: exec(aicasm) failed (No such file or directory) > I> > > > *** Error code 1 > I> > > > > I> > > > Stop. > I> > > > m

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-04 Thread Gleb Smirnoff
On Mon, Nov 04, 2013 at 10:09:54PM -0700, Ian Lepore wrote: I> > > /usr/src/sys/dev/aic7xxx/aic7xxx.seq I> > > > make[2]: exec(aicasm) failed (No such file or directory) I> > > > *** Error code 1 I> > > > I> > > > Stop. I> > > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC I> > > > *** Error co

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-04 Thread Ian Lepore
On Mon, 2013-11-04 at 19:44 -0500, Outback Dingo wrote: > On Mon, Nov 4, 2013 at 7:36 PM, Ian Lepore wrote: > > > On Mon, 2013-11-04 at 19:25 -0500, Outback Dingo wrote: > > > cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls > > > -Wnested-externs -Wstrict-prototypes -Wmi

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-04 Thread Outback Dingo
On Mon, Nov 4, 2013 at 7:36 PM, Ian Lepore wrote: > On Mon, 2013-11-04 at 19:25 -0500, Outback Dingo wrote: > > cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > -Winline -Wcast-qual -Wundef

Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-04 Thread Ian Lepore
On Mon, 2013-11-04 at 19:25 -0500, Outback Dingo wrote: > cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-di

CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

2013-11-04 Thread Outback Dingo
cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wn

Re: CUURENT kernel build broken - /usr/src/sys/dev/xen/netback/netback.c

2013-10-28 Thread Gleb Smirnoff
On Mon, Oct 28, 2013 at 05:33:23PM -0400, Outback Dingo wrote: O> /usr/src/sys/dev/xen/netback/netback.c O> /usr/src/sys/dev/xen/netback/netback.c:588:7: error: incomplete definition O> of type 'struct mbuf' O> if (m->m_flags & M_PKTHDR) { This one already fixed. Sorry. -- Totus tuus, G

CUURENT kernel build broken - /usr/src/sys/dev/xen/netback/netback.c

2013-10-28 Thread Outback Dingo
cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compar

Re: rescue build broken?

2012-02-20 Thread Adrian Chadd
Ignore; purging obj properly worked. Adrian ___ 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: rescue build broken?

2012-02-20 Thread Tim Kientzle
On Feb 20, 2012, at 5:57 AM, Adrian Chadd wrote: > Hi, > > Is anyone seeing this? > > (cd /usr/home/adrian/work/freebsd/svn/src/rescue/rescue/../../usr.bin/tar > && make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/tar/ > depend && make -DRESCUE CRUNCH_CFLAGS=-DRESCUE > DIRPRFX=rescue/

rescue build broken?

2012-02-20 Thread Adrian Chadd
Hi, Is anyone seeing this? (cd /usr/home/adrian/work/freebsd/svn/src/rescue/rescue/../../usr.bin/tar && make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/tar/ depend && make -DRESCUE CRUNCH_CFLAGS=-DRESCUE DIRPRFX=rescue/rescue/tar/ bsdtar.o cmdline.o getdate.o read.o subst.o tree.o u

Re: libc build broken with clang ?

2011-08-01 Thread Alex Kuster
> > For now, remove the line: > > CFLAGS+="-march=native" > > from your make.conf, and try again. Clang still has some problems with > this setting, and you are most likely hitting them. Whoops, didn't know that ... I actually used "-march=native" before, but never had any kind of problems (I

Re: libc build broken with clang ?

2011-08-01 Thread Dimitry Andric
On 2011-07-31 19:15, Alex Kuster wrote: Hi! I'm writing because I'm having some issues with -CURRENT and clang in amd64. I first compiled latest revision at this date and everything went ok: [0][root@Symphony ~]# uname -a FreeBSD Symphony.Gl 9.0-CURRENT FreeBSD 9.0-CURRENT #4: Sun Jul 10 10:38

libc build broken with clang ?

2011-07-31 Thread Alex Kuster
Hi! I'm writing because I'm having some issues with -CURRENT and clang in amd64. I first compiled latest revision at this date and everything went ok: > [0][root@Symphony ~]# uname -a > FreeBSD Symphony.Gl 9.0-CURRENT FreeBSD 9.0-CURRENT #4: Sun Jul 10 10:38:28 > ART 2011 t...@symphony.gl:/u

Re: stable/8 kernel build broken on head without WITH_CTF

2010-09-01 Thread Andriy Gapon
The subject should have been what it is now, sorry. -- Andriy Gapon ___ 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"

stable/8 build broken on head without WITH_CTF

2010-09-01 Thread Andriy Gapon
stable/8 build seems to be broken for me on head without WITH_CTF: ... cc -c -x assembler-with-cpp -DLOCORE -O2 -fno-strict-aliasing -pipe -march=k8 -std=c99 -g -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-p

Build broken in sys/dev/pcic/i82365.c

2003-08-30 Thread Doug Barton
With latest sources: cc -c -O -fno-ident -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/local/src/sys -I/usr/local/src/sys/contrib/dev/acpic

Re: build broken by usbdivar.h 1.40

2003-07-15 Thread Larry Rosenman
--On Tuesday, July 15, 2003 22:31:38 -0500 Larry Rosenman <[EMAIL PROTECTED]> wrote: ===> netgraph/bluetooth/ubt cc -O -pipe -mcpu=pentiumpro -g -I/usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../netgraph/blueto ot h/include -I/usr/src/sys/modules/netgraph/bluetooth/ubt/../../../../netg

Re: build broken by usbdivar.h 1.40

2003-07-15 Thread Larry Rosenman
--On Tuesday, July 15, 2003 19:21:13 -0700 John-Mark Gurney <[EMAIL PROTECTED]> wrote: Larry Rosenman wrote this message on Tue, Jul 15, 2003 at 21:10 -0500: the fresh cvsup died in the same place, obviously. :-) Ok, this has been fixed and I have also fixed a few of the other usb modules that

Re: build broken by usbdivar.h 1.40

2003-07-15 Thread John-Mark Gurney
Larry Rosenman wrote this message on Tue, Jul 15, 2003 at 21:10 -0500: > the fresh cvsup died in the same place, obviously. :-) Ok, this has been fixed and I have also fixed a few of the other usb modules that suffered the same problems. Builds should be working again. > >>/usr/src/sys/dev/usb/i

Re: build broken by usbdivar.h 1.40

2003-07-15 Thread Larry Rosenman
Thanks, John-Mark. the fresh cvsup died in the same place, obviously. :-) LER --On Tuesday, July 15, 2003 19:09:26 -0700 John-Mark Gurney <[EMAIL PROTECTED]> wrote: Larry Rosenman wrote this message on Tue, Jul 15, 2003 at 21:06 -0500: I'm seeing the same thing, re-cvsup'd, and the kernel buil

Re: build broken by usbdivar.h 1.40

2003-07-15 Thread John-Mark Gurney
Larry Rosenman wrote this message on Tue, Jul 15, 2003 at 21:06 -0500: > I'm seeing the same thing, re-cvsup'd, and the kernel build is still > running, but here is where mine died: > > ===> aue > cc -O -pipe -mcpu=pentiumpro -D_KERNEL -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototy

Re: build broken by usbdivar.h 1.40

2003-07-15 Thread Larry Rosenman
--On Tuesday, July 15, 2003 19:04:17 -0700 John-Mark Gurney <[EMAIL PROTECTED]> wrote: Pawel Worach wrote this message on Wed, Jul 16, 2003 at 03:51 +0200: @/dev/usb/usbdivar.h:127: error: syntax error before "bus_dma_tag_t" Could you please include more information? like what file? I just com

Re: build broken by usbdivar.h 1.40

2003-07-15 Thread John-Mark Gurney
Pawel Worach wrote this message on Wed, Jul 16, 2003 at 03:51 +0200: > @/dev/usb/usbdivar.h:127: error: syntax error before "bus_dma_tag_t" Could you please include more information? like what file? I just completed a build of usb (module) w/o problems. -- John-Mark Gurney

build broken by usbdivar.h 1.40

2003-07-15 Thread Pawel Worach
@/dev/usb/usbdivar.h:127: error: syntax error before "bus_dma_tag_t" -Pawel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: build broken

2002-10-30 Thread Peter Schultz
Eric J. Chet wrote: Hello I just tried a -current buildworld which failed: --- "/usr/src/gnu/usr.bin/groff/tmac/Makefile", line 2: warning: duplicate script for target "-s" ignored make: don't know how to make doc-common-s. Stop --- Anybody else seeing this? Thanks, Eric Yes, buildworld

build broken

2002-10-28 Thread Eric J. Chet
Hello I just tried a -current buildworld which failed: --- "/usr/src/gnu/usr.bin/groff/tmac/Makefile", line 2: warning: duplicate script for target "-s" ignored make: don't know how to make doc-common-s. Stop --- Anybody else seeing this? Thanks, Eric To Unsubscribe: send mail to [EMA

Re: imake-4 build broken

2002-10-13 Thread Vallo Kallaste
On Sat, Oct 12, 2002 at 08:31:52PM -0400, Mike Barcroft <[EMAIL PROTECTED]> wrote: > > > I don't really understand how this is happening. The uses of NSIG are > > > also conditionalized. If _POSIX_SOURCE is defined, line 46 should not > > > be visible. What rev is your /usr/include/sys/cdefs.h

Re: imake-4 build broken

2002-10-12 Thread Kris Kennaway
On Sat, Oct 12, 2002 at 08:31:52PM -0400, Mike Barcroft wrote: > I've just committed the rest of my -related patches, can you > update your system and let me know if I've fixed the problem. Thanks, this fixes the wdm build too. Kris msg45285/pgp0.pgp Description: PGP signature

Re: imake-4 build broken

2002-10-12 Thread Mike Barcroft
Vallo Kallaste <[EMAIL PROTECTED]> writes: > On Thu, Oct 10, 2002 at 08:03:00PM -0400, Mike Barcroft <[EMAIL PROTECTED]> wrote: > > > > imake-4 port building is broken. I guess that's because > > > xc/config/makedepend/main.c defines _POSIX_SOURCE before including > > > . Signal.h includes which

Re: imake-4 build broken

2002-10-10 Thread Vallo Kallaste
On Thu, Oct 10, 2002 at 08:03:00PM -0400, Mike Barcroft <[EMAIL PROTECTED]> wrote: > > imake-4 port building is broken. I guess that's because > > xc/config/makedepend/main.c defines _POSIX_SOURCE before including > > . Signal.h includes which has conditional > > #if !defined(_POSIX_SOURCE) and

Re: imake-4 build broken

2002-10-10 Thread Mike Barcroft
Vallo Kallaste <[EMAIL PROTECTED]> writes: > Hi > > imake-4 port building is broken. I guess that's because > xc/config/makedepend/main.c defines _POSIX_SOURCE before including > . Signal.h includes which has conditional > #if !defined(_POSIX_SOURCE) and NSIG will be left undefined. Don't > know

imake-4 build broken

2002-10-10 Thread Vallo Kallaste
Hi imake-4 port building is broken. I guess that's because xc/config/makedepend/main.c defines _POSIX_SOURCE before including . Signal.h includes which has conditional #if !defined(_POSIX_SOURCE) and NSIG will be left undefined. Don't know who is in fault here, imake sources or our headers, my k

Re: kdebase-3.0.3 build broken in ksysguardd

2002-10-01 Thread Vallo Kallaste
On Tue, Oct 01, 2002 at 10:47:45AM +0200, Michael Hostbaek <[EMAIL PROTECTED]> wrote: > It it a style problem, and Will and Alan should be aware of it - and > when code freeze is over they should commit a patch. > > A temp solution is to edit 'kdebase-3.0.3/ksysguard/FreeBSD/netdev.c' > and movi

Re: kdebase-3.0.3 build broken in ksysguardd

2002-10-01 Thread Michael Hostbaek
It it a style problem, and Will and Alan should be aware of it - and when code freeze is over they should commit a patch. A temp solution is to edit 'kdebase-3.0.3/ksysguard/FreeBSD/netdev.c' and moving '#include ' to just above '#include ' Hint: You should read the kde-freebsd list - as this to

kdebase-3.0.3 build broken in ksysguardd

2002-09-30 Thread Vallo Kallaste
Hi On -current as of yesterday, the kdebase-3.0.3 build fails in ksysguardd. source='netdev.c' object='netdev.o' libtool=no \ depfile='.deps/netdev.Po' tmpdepfile='.deps/netdev.TPo' \ depmode=gcc3 /bin/sh ../../../admin/depcomp \ cc -DHAVE_CONFIG_H -I. -I. -I../../.. -DKSYSGUARDDRCFILE="\"\"" -I

perl build broken on current. Was: Re: Perl script rewrites - progress (2)

2002-05-19 Thread John Hay
> I just upgraded my machine, removed perl as far as I could find it, and > tried to rebuild perl from the ports tree. > > So far, I had to change the Makefile first, since it used perl for the > post-patch target. That was easy: > > change the CP and the PERL -pi to a: > > ${SED} <${FILES}/use

Re: Build broken and not building modules

2002-03-03 Thread Glenn Gombert
try "make -DNO_WERROR kernel" it overrides the complier warning messages being generated at the moment (that are treated as errors) . Aleksander Rozman - Andy <[EMAIL PROTECTED]> wrote: > > Hi ! > > I am trying to compile in my code for kernel, but every time I start > > compile (e

Build broken and not building modules

2002-03-03 Thread Aleksander Rozman - Andy
Hi ! I am trying to compile in my code for kernel, but every time I start compile (even without my code) it stops in modules. It seems that latest commits have a lot of modules errors. Is there a way to override building modules. To build kernel I usually go to i386/compile/NAME directory and

Re: libusb build broken due to structure member renaming

2002-02-25 Thread Bill Fenner
You could use http://people.freebsd.org/~fenner/__FreeBSD_version.html to find an already-existing value of __FreeBSD_version to test based on the date of the original change. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: libusb build broken due to structure member renaming

2002-02-24 Thread Terry Lambert
Terry Lambert wrote: > > Question #1: are there plans to MFC these changes in the USB structures to > > -stable in the near future? Too late. Alfred is too fast. > > Question #2: If not, is __FreeBSD_version >= 500030 the appropriate thing to > > "key" off of in order to make a patch set for l

Re: libusb build broken due to structure member renaming

2002-02-24 Thread Terry Lambert
John Reynolds wrote: > hello, I've got a -current-related question to ask. akbeech forwarded me > his build log when trying to build the "linux" user-land libusb from the > port which I maintain (it is below). At first I said "impossible" because I'd > tested things thoroughly, but then noticed he

Re: libusb build broken due to structure member renaming

2002-02-24 Thread Alfred Perlstein
* John Reynolds <[EMAIL PROTECTED]> [020224 14:33] wrote: > > hello, I've got a -current-related question to ask. akbeech forwarded me > his build log when trying to build the "linux" user-land libusb from the > port which I maintain (it is below). At first I said "impossible" because I'd > teste

libusb build broken due to structure member renaming

2002-02-24 Thread John Reynolds
determine it's on a system with the 'new' structures. Comments? -Jr (please cc: as I don't subscribe directly to -current) --- start of forwarded message --- From: Beech Rintoul <[EMAIL PROTECTED]> Subject: libusb build broken To: [EMAIL PROTECTED] Date: Sun, 24

Re: ghostscript-gnu build broken

2002-01-16 Thread Andreas Klemm
HP released a new version. 1.0.1. They have fixed a bug in the sources. Could someone try the new version with optimization -O / -O2 turned on ? I only can do it in 10 hours from now. Andreas /// -- Andreas Klemm Apsfilter Homepage http://www.apsfilter.org Suppo

Re: ghostscript-gnu build broken

2002-01-14 Thread Andreas Klemm
On Mon, Jan 14, 2002 at 08:17:39AM +0200, John Hay wrote: > > Do you think its possible to put "that logic" into the port ? > > I looked into it a bit. I think it is better if automake don't have to > be run. What about removeing files/patch-hpijs-1.0:configure.in and > patch the port Makefile wi

Re: ghostscript-gnu build broken

2002-01-13 Thread John Hay
> On Sat, Jan 12, 2002 at 01:25:55PM +0200, John Hay wrote: > > It is not a -current problem. It is if you use the latest automake port, > > which is using v1.5. I tried that command manually with automake14 and > > then I didn't get that error. > > John, what steps did you do exactly ? Somethin

Re: ghostscript-gnu build broken

2002-01-13 Thread Andreas Klemm
On Sat, Jan 12, 2002 at 01:25:55PM +0200, John Hay wrote: > It is not a -current problem. It is if you use the latest automake port, > which is using v1.5. I tried that command manually with automake14 and > then I didn't get that error. John, what steps did you do exactly ? Do you think its poss

Re: ghostscript-gnu build broken

2002-01-12 Thread Beech Rintoul
On Saturday 12 January 2002 01:47 am, Andreas Klemm wrote: > On Fri, Jan 11, 2002 at 08:33:25PM -0900, Beech Rintoul wrote: > > Hi, > > I'm glad to see the problem with hpijs is being fixed, however when I > > tried > > > > to build the port it died with the following: > > >>> building hpijs ser

Re: ghostscript-gnu build broken

2002-01-12 Thread Steve O'Hara-Smith
On Sat, 12 Jan 2002 06:11:10 -0500 "Gerald A. Speak" <[EMAIL PROTECTED]> wrote: GAS> I was having the same problem until I un-installed automake and autoconf, GAS> after which ghostscript-gnu installed just fine. I've seen this a lot since automake 1.5 hit my system there seems to be a

Re: ghostscript-gnu build broken

2002-01-12 Thread John Hay
> > > Hi, > > > I'm glad to see the problem with hpijs is being fixed, however when I > > > tried > > > > > > to build the port it died with the following: > > > >>> building hpijs server ... > > > > > > cd . && aclocal > > > cd . && automake --foreign --include-deps Makefile > > > automake: con

Re: ghostscript-gnu build broken

2002-01-12 Thread Gerald A. Speak
On Saturday 12 January 2002 05:47 am, Andreas Klemm wrote: > On Fri, Jan 11, 2002 at 08:33:25PM -0900, Beech Rintoul wrote: > > Hi, > > I'm glad to see the problem with hpijs is being fixed, however when I > > tried > > > > to build the port it died with the following: > > >>> building hpijs ser

Re: ghostscript-gnu build broken

2002-01-12 Thread Andreas Klemm
On Fri, Jan 11, 2002 at 08:33:25PM -0900, Beech Rintoul wrote: > Hi, > I'm glad to see the problem with hpijs is being fixed, however when I tried > to build the port it died with the following: > > >>> building hpijs server ... > cd . && aclocal > cd . && automake --foreign --include-deps Mak

Re: ghostscript-gnu build broken

2002-01-12 Thread Andreas Klemm
On Fri, Jan 11, 2002 at 08:33:25PM -0900, Beech Rintoul wrote: > Hi, > I'm glad to see the problem with hpijs is being fixed, however when I tried > to build the port it died with the following: > > >>> building hpijs server ... > cd . && aclocal > cd . && automake --foreign --include-deps Mak

ghostscript-gnu build broken

2002-01-11 Thread Beech Rintoul
Hi, I'm glad to see the problem with hpijs is being fixed, however when I tried to build the port it died with the following: >>> building hpijs server ... cd . && aclocal cd . && automake --foreign --include-deps Makefile automake: configure.in: required file `./depcomp' not found gmake: ***

Re: libpam build broken in current

2001-08-03 Thread Kris Kennaway
On Tue, Jul 31, 2001 at 08:53:56AM -0700, Manfred Antar wrote: > libpam will not build if you don't have the stock ssh installed. > I use ssh from ports. > > (libpam)502}make > ===> modules > ===> modules/pam_deny > ===> modules/pam_ftp > ===> modules/pam_nologin > ===> modules/pam_opie > ===> mo

libpam build broken in current

2001-07-31 Thread Manfred Antar
libpam will not build if you don't have the stock ssh installed. I use ssh from ports. (libpam)502}make ===> modules ===> modules/pam_deny ===> modules/pam_ftp ===> modules/pam_nologin ===> modules/pam_opie ===> modules/pam_permit ===> modules/pam_radius ===> modules/pam_rootok ===> modules/pam_s

Re: -STABLE kernel build broken?

2001-05-21 Thread David Wolfskill
>Date: Mon, 21 May 2001 17:15:32 +0300 >From: Ruslan Ermilov <[EMAIL PROTECTED]> [I note that I included -current by mistake; I had intended to include -stable. But since the thread has started dhw] >On Mon, May 21, 2001 at 07:01:19AM -0700, David Wolfskill wrote: >> Seems that perhaps the

Re: -STABLE kernel build broken?

2001-05-21 Thread Ruslan Ermilov
On Mon, May 21, 2001 at 07:01:19AM -0700, David Wolfskill wrote: > Seems that perhaps the MFC of some changes to mbuf.h also needed some > corresponding changes elsewhere (such as netncp/ncp_rq.c). > > This is on a system running: > FreeBSD dhcp-133.catwhisker.org 4.3-STABLE FreeBSD 4.3-STABLE #2

-STABLE kernel build broken?

2001-05-21 Thread David Wolfskill
Seems that perhaps the MFC of some changes to mbuf.h also needed some corresponding changes elsewhere (such as netncp/ncp_rq.c). This is on a system running: FreeBSD dhcp-133.catwhisker.org 4.3-STABLE FreeBSD 4.3-STABLE #20: Sun May 20 06:23:46 PDT 2001 [EMAIL PROTECTED]:/common/S2/obj/usr/s

Re: current kernel build broken in sc0

2001-03-24 Thread Michael C . Wu
On Sat, Mar 24, 2001 at 10:35:58PM -0600, Michael C . Wu scribbled: | I get this when I add the following lines to my kernel build | options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) | options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) | options SC_KERNEL_CONS_ATTR=(FG_LIGHTRED|BG_BLACK) | options SC_KERNEL_CON

  1   2   >