Re: kernel build failure

On 8/14/18 1:35 AM, Matthew Macy wrote: > On Mon, Aug 13, 2018 at 5:33 PM Rick Macklem wrote: > >> Rodney W. Grimes wrote: On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an >> option to > statically link and

Re: kernel build failure

[ Charset ISO-8859-1 unsupported, converting... ] > Rodney W. Grimes wrote: > >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > >> > >> > Sorry guys, last time I touched ZFS I tried to push to make it an option > >> > to > >> > statically link and was actually told that it wasn't something

Re: kernel build failure

On Mon, Aug 13, 2018 at 5:33 PM Rick Macklem wrote: > Rodney W. Grimes wrote: > >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > >> > >> > Sorry guys, last time I touched ZFS I tried to push to make it an > option to > >> > statically link and was actually told that it wasn't something

Re: kernel build failure

Rodney W. Grimes wrote: >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: >> >> > Sorry guys, last time I touched ZFS I tried to push to make it an option to >> > statically link and was actually told that it wasn't something anyone else >> > wanted. The issue comes from ZFS not being in

Re: kernel build failure

Rodney W. Grimes wrote: On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: Sorry guys, last time I touched ZFS I tried to push to make it an option to statically link and was actually told that it wasn't something anyone else wanted. The issue comes from ZFS not being in NOTES and thus not in

Re: kernel build failure

> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > > > Sorry guys, last time I touched ZFS I tried to push to make it an option to > > statically link and was actually told that it wasn't something anyone else > > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. > >

Re: kernel build failure

On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an option to > statically link and was actually told that it wasn't something anyone else > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. If consensus

Re: kernel build failure

On Sun, Aug 12, 2018, 4:27 PM Matthew Macy wrote: > > > On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote: > >> >> >> On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: >> >>> Sorry guys, last time I touched ZFS I tried to push to make it an option >>> to >>> statically link and was actually

Re: kernel build failure

On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote: > > > On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: > >> Sorry guys, last time I touched ZFS I tried to push to make it an option >> to >> statically link and was actually told that it wasn't something anyone else >> wanted. The issue comes

Re: kernel build failure

On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an option to > statically link and was actually told that it wasn't something anyone else > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. > LINT is

Re: kernel build failure

Sorry guys, last time I touched ZFS I tried to push to make it an option to statically link and was actually told that it wasn't something anyone else wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. -M On Sun, Aug 12, 2018 at 12:46 PM Trond Endrestøl <

Re: kernel build failure

On Sun, 12 Aug 2018 16:51+0200, Trond Endrestøl wrote: > On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > > > Is anyone else seeing this when building a new kernel with ZFS compiled in? > > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > > Building

Re: kernel build failure

On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > Is anyone else seeing this when building a new kernel with ZFS compiled in? > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel > --- kernel --- > linking kernel > ld: error:

kernel build failure

Is anyone else seeing this when building a new kernel with ZFS compiled in? Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel --- kernel --- linking kernel ld: error: undefined symbol: dbuf_stats_init >>> referenced by dbuf.c >>>

r311977: kernel build failure when NANDFS in kernel

On r311977, buildkernel fails with the error shown below. Kernel ist customised and "options NANDFS" has been added as well as "device nand" - the error shown suggest that is has to do with NANDFS. [...] ===> cc/cc_cdg (all) --- nand_geom.o --- /usr/src/sys/dev/nand/nand_geom.c:419:2: error:

Re: r311871: kernel build failure: ieee80211_vht.c:94:2: error: implicit declaration ...

Am Tue, 10 Jan 2017 11:32:00 +0100 "O. Hartmann" schrieb: > On CURRENT (r311871), I'm bothered with this error schown below. Buildkernel > fails. It is a customized kernel. > > [...] > Building > /usr/obj/usr/src/sys/FREYJA/modules/usr/src/sys/modules/wlan/ieee80211.o >

r311871: kernel build failure: ieee80211_vht.c:94:2: error: implicit declaration ...

On CURRENT (r311871), I'm bothered with this error schown below. Buildkernel fails. It is a customized kernel. [...] Building /usr/obj/usr/src/sys/FREYJA/modules/usr/src/sys/modules/wlan/ieee80211.o Building /usr/obj/usr/src/sys/FREYJA/modules/usr/src/sys/modules/wlan/ieee80211_vht.o

Re: r310188: kernel build failure due to mlx4_ib_sysfs.c:90:22: error: format specifies type 'unsigned long long

Am Sun, 18 Dec 2016 16:22:31 +0100 Dimitry Andric schrieb: > On 18 Dec 2016, at 16:10, O. Hartmann wrote: > > > > Am Sat, 17 Dec 2016 18:27:18 +0100 > > Dimitry Andric schrieb: > > > >> On 17 Dec 2016, at 12:46, O. Hartmann

Re: r310188: kernel build failure due to mlx4_ib_sysfs.c:90:22: error: format specifies type 'unsigned long long

On 18 Dec 2016, at 16:10, O. Hartmann wrote: > > Am Sat, 17 Dec 2016 18:27:18 +0100 > Dimitry Andric schrieb: > >> On 17 Dec 2016, at 12:46, O. Hartmann wrote: >>> >>> Recent kernel source reject to build: >>> >>> [...] >>>

Re: r310188: kernel build failure due to mlx4_ib_sysfs.c:90:22: error: format specifies type 'unsigned long long

Am Sat, 17 Dec 2016 18:27:18 +0100 Dimitry Andric schrieb: > On 17 Dec 2016, at 12:46, O. Hartmann wrote: > > > > Recent kernel source reject to build: > > > > [...] > > --- all_subdir_mlx4ib --- > > --- mlx4_ib_sysfs.o --- > >

Re: r310188: kernel build failure due to mlx4_ib_sysfs.c:90:22: error: format specifies type 'unsigned long long

Am Sat, 17 Dec 2016 18:27:18 +0100 Dimitry Andric schrieb: > On 17 Dec 2016, at 12:46, O. Hartmann wrote: > > > > Recent kernel source reject to build: > > > > [...] > > --- all_subdir_mlx4ib --- > > --- mlx4_ib_sysfs.o --- > >

Re: r310188: kernel build failure due to mlx4_ib_sysfs.c:90:22: error: format specifies type 'unsigned long long

On 17 Dec 2016, at 12:46, O. Hartmann wrote: > > Recent kernel source reject to build: > > [...] > --- all_subdir_mlx4ib --- > --- mlx4_ib_sysfs.o --- > /usr/src/sys/modules/mlx4ib/../../dev/mlx4/mlx4_ib/mlx4_ib_sysfs.c:90:22: > error: format > specifies type 'unsigned

r310188: kernel build failure due to mlx4_ib_sysfs.c:90:22: error: format specifies type 'unsigned long long

Recent kernel source reject to build: [...] --- all_subdir_mlx4ib --- --- mlx4_ib_sysfs.o --- /usr/src/sys/modules/mlx4ib/../../dev/mlx4/mlx4_ib/mlx4_ib_sysfs.c:90:22: error: format specifies type 'unsigned long long *' but the argument has type 'u64 *' (aka 'unsigned long *')

kernel build failure in if_lmc when bpf(4) disabled!

Building a custom kernel fails when bpf(4) is disabled as suggested in security(7) due to the error shown below. I also tried to define in make.conf WITHOUT_MODULES="lmc" or WITHOU_MODULES="if_lmc" assuming I could avoid building the culprit module/device, but it did not work as expected! I

Revision: 270871: kernel build failure due to: [...]/netmap.c:556:23: error: no member named 'if_pspare' in 'struct ifnet'

cc -c -O3 -fno-strict-aliasing -march=native -std=c99 -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

ARM LINT kernel build failure

Started recently (within the last day or so). -- Kernel build for LINT started on Fri Aug 15 11:08:29 UTC 2014 -- === LINT

[CURRENT r256850]: kernel build failure due to issues in freebsd32/freebsd32_misc.c and sys/ufs/ufs/ufs_vnops.c

Most recent kernel (r256850) fails to build: cc -c -pipe -O3 -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs

r254147: kernel build failure: vm_page.c:1206:20: error: use of undeclared identifier 'VPO_BUSY'

Most recent sources fails in kernel build: [...] cc -c -pipe -O3 -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions

r248093: Kernel build failure: /usr/src/sys/net80211/ieee80211_output.c:600:23: error: unused variable 'ic' [-Werror,-Wunused-variable]

On CURRENT, r248093, build of kernel fails due to the below shown error. [...] cc -c -O3 -O3 -Wno-error=unused-variable -fno-strict-aliasing -march=native -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef

Re: r248093: Kernel build failure: /usr/src/sys/net80211/ieee80211_output.c:600:23: error: unused variable 'ic' [-Werror,-Wunused-variable]

On Sat, Mar 09, 2013 at 11:59:21AM +0100, Hartmann, O. wrote: On CURRENT, r248093, build of kernel fails due to the below shown error. [...] cc -c -O3 -O3 -Wno-error=unused-variable -fno-strict-aliasing ... -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror

kernel build failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 SVN r247736 prompts this .. cc -c -O2 -pipe -fno-strict-aliasing -march=pentium4 -std=c99 -Wall - -Wredundant-decls -Wnested-externs -Wstrict-prototypes - -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef - -Wno-pointer-sign

Re: kernel build failure

On Sun, Mar 03, 2013 at 06:47:00PM -0500, Michael Butler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 SVN r247736 prompts this .. cc -c -O2 -pipe -fno-strict-aliasing -march=pentium4 -std=c99 -Wall - -Wredundant-decls -Wnested-externs -Wstrict-prototypes - -Wmissing-prototypes

Re: [clang] kernel build failure

09.08.2012 16:26, David Wolfskill пишет: On Thu, Aug 09, 2012 at 04:15:36PM +0400, Boris Samorodov wrote: Hi! The kernel build fails at fresh CURRENT... And then I get an error: - linking kernel.debug cam_periph.o: In function `cam_periph_error': /usr/src/sys/cam/cam_periph.c:1776:

Re: [clang] kernel build failure

On Thu, Aug 09, 2012 at 04:15:36PM +0400, Boris Samorodov wrote: Hi! The kernel build fails at fresh CURRENT... And then I get an error: - linking kernel.debug cam_periph.o: In function `cam_periph_error': /usr/src/sys/cam/cam_periph.c:1776: undefined reference to

Re: kernel build failure

On 15.04.2012 00:01 (UTC+1), AN wrote: On Fri, 13 Apr 2012, O. Hartmann wrote: Am 04/13/12 00:21, schrieb AN: At Thu Apr 12 17:52:05 EDT 2012: [root@FBSD10 /usr/src]# svn up Updating '.': At revision 234196. Trying to build the kernel I get the following failure: time make -j8

Re: kernel build failure

Am 04/15/12 00:01, schrieb AN: On Fri, 13 Apr 2012, O. Hartmann wrote: Am 04/13/12 00:21, schrieb AN: At Thu Apr 12 17:52:05 EDT 2012: [root@FBSD10 /usr/src]# svn up Updating '.': At revision 234196. Trying to build the kernel I get the following failure: time make -j8 buildkernel

Re: kernel build failure

On Sun, 15 Apr 2012 09:47:38 +0200 Rainer Hurling rhur...@gwdg.de wrote: On 15.04.2012 00:01 (UTC+1), AN wrote: I updated source with svn within the last hour, and rebuilt world and kernel. When I tried to boot to single-user mode to installworld the machine panicked and rebooted. I

Re: kernel build failure

On Fri, 13 Apr 2012, O. Hartmann wrote: Am 04/13/12 00:21, schrieb AN: At Thu Apr 12 17:52:05 EDT 2012: [root@FBSD10 /usr/src]# svn up Updating '.': At revision 234196. Trying to build the kernel I get the following failure: time make -j8 buildkernel KERNCONF=MYKERNEL snip === zlib

Re: kernel build failure

On 13 April 2012 02:21, AN a...@neu.net wrote: At Thu Apr 12 17:52:05 EDT 2012: [root@FBSD10 /usr/src]# svn up Updating '.': At revision 234196. [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes

Re: kernel build failure

Am 04/13/12 00:21, schrieb AN: At Thu Apr 12 17:52:05 EDT 2012: [root@FBSD10 /usr/src]# svn up Updating '.': At revision 234196. Trying to build the kernel I get the following failure: time make -j8 buildkernel KERNCONF=MYKERNEL snip === zlib (all) cc -O2 -pipe

kernel build failure

At Thu Apr 12 17:52:05 EDT 2012: [root@FBSD10 /usr/src]# svn up Updating '.': At revision 234196. Trying to build the kernel I get the following failure: time make -j8 buildkernel KERNCONF=MYKERNEL snip === zlib (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc

Re: kernel build failure without BPF

On 14 August 2011 06:01, deeptec...@gmail.com deeptec...@gmail.com wrote: in the following kernel configuration (notably without ``device bfp''), i get the following kernel build error. which is either a bug, or not; just posting in case it's in someone's interest. build log snippet

kernel build failure without BPF

in the following kernel configuration (notably without ``device bfp''), i get the following kernel build error. which is either a bug, or not; just posting in case it's in someone's interest. build log snippet begins === pfsync (all) cc -O2 -fno-strict-aliasing -pipe

Re: pcic device causes kernel build failure

M. Warner Losh wrote: Don't build pcic with newcard. It is broken, doesn't work and isn't supported. I have a rewrite in my p4 tree that I'm slugging through, but pcic is likely to coninue to not compile until that's committed. Will that eventually fix support for the following (dmesg

Re: pcic device causes kernel build failure

In message: [EMAIL PROTECTED] Ian Freislich [EMAIL PROTECTED] writes: : M. Warner Losh wrote: : Don't build pcic with newcard. It is broken, doesn't work and isn't : supported. I have a rewrite in my p4 tree that I'm slugging through, : but pcic is likely to coninue to not compile

Re: pcic device causes kernel build failure

In message: [EMAIL PROTECTED] Doug Barton [EMAIL PROTECTED] writes: : I found my problem, when I got this new laptop two weeks ago I : UN-commented the pcic cardbus bridge just in case. This worked fine up : till 8/27, my last build on that machine. Starting last night, with that :

pcic device causes kernel build failure

I found my problem, when I got this new laptop two weeks ago I UN-commented the pcic cardbus bridge just in case. This worked fine up till 8/27, my last build on that machine. Starting last night, with that device in my kernel config, kernel build fails with the error below. Commenting it again

kernel build failure: mga_state.c

cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica

Re: kernel build failure: mga_state.c

Have you not been reading the mailing list? Right now you are supposed to WERROR if you run into these. Kris pgp0.pgp Description: PGP signature

Another aic7xxx kernel build failure...

Another issue with 'aicasm': It breaks the following: * Vanilla install of 4.6-RELEASE (from CD-ROM) * Pull 5.0-CURRENT sources (as of 2 Sept 2002) * 'make buildworld' * 'make kernel' The kernel compile breaks when it tries to run aicasm, with a message about 'libc.so.5' not being

Re: aic7xxx kernel build failure...

Well, I ended up unlinking it from the build and am installing now. Once I get a fresh world installed, I'll try and rebuild world again to see if the problem persists. Would you like me to get a ktrace of aicasm running before I rebuild world? -sc That would have been interesting.

Re: aic7xxx kernel build failure...

cvsup earlier today. I just finished mergemaster'ing my upgrade from a May -CURRENT. I removed the offending line from sys/modules/Makefile, and set NOMOODULES=1. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

aic7xxx kernel build failure...

Is anyone else seeing something similar to the following? I'm able to build world, but can't get this kernel build to budge. I've not seen this error before so I'm a tad lost as to where to poke next. -sc === aic7xxx === aic7xxx/aicasm make -f

RE: aic7xxx kernel build failure...

Is anyone else seeing something similar to the following? I'm able to build world, but can't get this kernel build to budge. I've not seen this error before so I'm a tad lost as to where to poke next. -sc This is the third report of this that I've seen, and I'm completely baffled. How

Re: aic7xxx kernel build failure...

Is anyone else seeing something similar to the following? I'm able to build world, but can't get this kernel build to budge. I've not seen this error before so I'm a tad lost as to where to poke next. -sc This is the third report of this that I've seen, and I'm completely baffled.

Re: aic7xxx kernel build failure...

Is anyone else seeing something similar to the following? I'm able to build world, but can't get this kernel build to budge. I've not seen this error before so I'm a tad lost as to where to poke next. -sc This is the third report of this that I've seen, and I'm

Re: aic7xxx kernel build failure...

Well, I ended up unlinking it from the build and am installing now. Once I get a fresh world installed, I'll try and rebuild world again to see if the problem persists. Would you like me to get a ktrace of aicasm running before I rebuild world? -sc That would have been interesting. --

RE: aic7xxx kernel build failure...

I ran into this, and found that re-running config and make depend made it go away. Didn't have time to do any other follow-up. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Mon, 2 Sep 2002, Long, Scott wrote:

kernel build failure

Current source in ipfw was broken: cc -O -pipe -DIPFIREWALL -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -g

kernel build failure in amr

Hi, Without -DNO_WERROR, i sometimes get a build failure on CURRENT sources, as shown below. However, this does not always occur, maybe 30% of the compiles succeed. Why would it sometimes compile fine? I've deleted my /usr/obj and /usr/src, and even my cvs repositry, without success.# Gavin

kernel build failure

Hi all From sources cvsup'd about an hour ago, "make depend" complains: ../../dev/ed/if_ed_pccard.c:58: miibus_if.h: No such file or directory and fails. This is after deleting the old kernel build dir. Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in

Re: kernel build failure

Did you add "device miibus" to you kernel configuration? Jim Bloom [EMAIL PROTECTED] Paul Allenby wrote: Hi all From sources cvsup'd about an hour ago, "make depend" complains: ../../dev/ed/if_ed_pccard.c:58: miibus_if.h: No such file or directory and fails. This is after deleting

RE: Current kernel build failure -- cam_periph.c

On 07-Dec-00 Manfred Antar wrote: At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: On 07-Dec-00 John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My

Current kernel build failure -- cam_periph.c

I've been trying to build a current kernel from current sources for a day now and I keep getting this: cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g

RE: Current kernel build failure -- cam_periph.c

On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). --

RE: Current kernel build failure -- cam_periph.c

On Wed, 6 Dec 2000, John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other

RE: Current kernel build failure -- cam_periph.c

At 05:49 PM 12/6/2000 -0800, you wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just

Re: Current kernel build failure -- cam_periph.c

On Wed, Dec 06, 2000 at 06:13:50PM -0800, Manfred Antar wrote: # At 05:49 PM 12/6/2000 -0800, you wrote: # # I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() # compiles in dozens of other places just fine (and has for months now). # # Yes # It's a different kind of

RE: Current kernel build failure -- cam_periph.c

On 07-Dec-00 John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just

RE: Current kernel build failure -- cam_periph.c

At 06:28 PM 12/6/2000 -0800, John Baldwin wrote: On 07-Dec-00 John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as

Re: alpha kernel build failure (w/patch)

On Mon, 05 Jul 1999 00:33:57 CDT, Steve Price wrote: +#ifdef __i386__ sc-wb_btag = I386_BUS_SPACE_IO; +#endif +#ifdef __alpha__ + sc-wb_btag = ALPHA_BUS_SPACE_IO; +#endif Just curious, but is there a reason that these lines aren't simply sc-wb_btag = BUS_SPACE_IO; with this

Re: alpha kernel build failure (w/patch)

[trimmed -alpha from cc: list to keep the cross posting police from coming after me :)] On Mon, 5 Jul 1999, Parag Patel wrote: # On Mon, 05 Jul 1999 00:33:57 CDT, Steve Price wrote: # +#ifdef __i386__ # sc-wb_btag = I386_BUS_SPACE_IO; # +#endif # +#ifdef __alpha__ # +sc-wb_btag =

Re: alpha kernel build failure (w/patch)

Of all the gin joints in all the towns in all the world, Steve Price had to walk into mine and say: [trimmed -alpha from cc: list to keep the cross posting police from coming after me :)] On Mon, 5 Jul 1999, Parag Patel wrote: # On Mon, 05 Jul 1999 00:33:57 CDT, Steve Price wrote: #

Re: alpha kernel build failure (w/patch)

Parag Patel wrote: On Mon, 05 Jul 1999 00:33:57 CDT, Steve Price wrote: +#ifdef __i386__ sc-wb_btag = I386_BUS_SPACE_IO; +#endif +#ifdef __alpha__ +sc-wb_btag = ALPHA_BUS_SPACE_IO; +#endif Just curious, but is there a reason that these lines aren't simply sc-wb_btag =

Re: alpha kernel build failure (w/patch)

In message [EMAIL PROTECTED] Bill Paul writes: : If we're really lucky then some day this will get fixed correctly, : by somebody who is not me, as I have plenty of other things to keep : me busy. I'm working on moderizing the bus space implementation right now. It will make writing the

Re: alpha kernel build failure (w/patch)

Steve Price writes: } +#ifdef __i386__ sc-wb_btag = I386_BUS_SPACE_IO; +#endif +#ifdef __alpha__ + sc-wb_btag = ALPHA_BUS_SPACE_IO; +#endif #else if (!(command PCIM_CMD_MEMEN)) { Just a minor comment.. anytime you have something like this, it's always nice to do

alpha kernel build failure (w/patch)

Anyone object to me fixing the wb driver so kernel builds on the Alpha don't fall over anymore? The patch was gleened from the similar changes to the al driver. Thanks. -steve Index: if_wb.c === RCS file:

Re: kernel build failure at nfs_serv.c

On Wed, Feb 24, 1999 at 08:51:03AM +, Doug Rabson wrote: On Tue, 23 Feb 1999, Nicolas Souchu wrote: Hi folks, Updating at Mar 23 fév 1999 22:52:33 CET, cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual

Re: kernel build failure at nfs_serv.c

On Sat, 27 Feb 1999, Nicolas Souchu wrote: On Wed, Feb 24, 1999 at 08:51:03AM +, Doug Rabson wrote: On Tue, 23 Feb 1999, Nicolas Souchu wrote: Hi folks, Updating at Mar 23 f?v 1999 22:52:33 CET, cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes

Re: kernel build failure at nfs_serv.c

On Tue, 23 Feb 1999, Nicolas Souchu wrote: Hi folks, Updating at Mar 23 f?v 1999 22:52:33 CET, cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../..

kernel build failure at nfs_serv.c

Hi folks, Updating at Mar 23 fév 1999 22:52:33 CET, cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include