Re: Kernel build broken without "options KTRACE"
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 > needed. I've fixed this in the main branch. Thanks for the report.
Kernel build broken without "options KTRACE"
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: Current kernel build broken with linuxkpi?
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_MODULES; things on
that
list get built _after_ buildkernel (installkernel??) for
reasons I
thought I understood.
You are telling me I need to update this _before_ buildkernel?
Perplexedly,
He telling you to update the port itself -- e.g.,
/usr/ports/graphics/drm-kmod, as the port was recently updated:
r561457 | manu | 2021-01-13 03:22:25 -0800 (Wed, 13 Jan 2021) |
6 lines
graphics/drm-{current,devel}-kmod: Update to latest source
This fix a compilation problem with a pre 1300135 source tree.
Reported by:Filippo Moretti
So you need to update the "ports files" to get that update, then
rebuild
the port (in concert with rebuilding the kernel, as you are
doing).
Peace,
david
Just as a curiosity because I was hit by this and the thread was
helpful:
I was unable to build the kernel with an up to date
drm-current-kmod, but as soon as I switched to drm-devel-kmod, I
was able to.
The running kernel was uname -K: 1300133.
Thanks everyone for having added their input here.
--
Evilham
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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; built successfully; built the kernel - successfully; and installed kernel then world with no hiccups. Thanks to everyone for their help. Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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, Robert "ENOBRAIN" Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 out-of-date. > When I try to upgrade drm-current-kmod (r561457) I get: > > ===> drm-current-kmod-5.4.62.g20210113 not supported on older > CURRENT, no > kernel support. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/graphics/drm-current-kmod > > Huh? > What is my path forward? (That does not involve reinstalling the > OS.) Either upgrade the kernel without the drm PORTS_ whatever thing h upgrade drm-current-kmod h add back the PORTS_thing if you really want it upgrade kernel again If I understand things correctly: things in the PORTS_MODULES list are upgraded _after_ the kernel is completely rebuilt. I am hitting this _during_ the rebuild. I'm not sure if they will be upgraded after it's installed.. also, did you upgrade the world? The version stuff that ports checks comes from /usr/include. So the question becomes: _will_ removing the IGNORE line work? Why wouldn't it? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 (r561457) I get: > > > > ===> drm-current-kmod-5.4.62.g20210113 not supported on older > > CURRENT, no > > kernel support. > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/graphics/drm-current-kmod > > > > Huh? > > What is my path forward? (That does not involve reinstalling the > > OS.) > > Either > > upgrade the kernel without the drm PORTS_ whatever thing �� > upgrade drm-current-kmod �� add back the PORTS_thing if you > really want it upgrade kernel again If I understand things correctly: things in the PORTS_MODULES list are upgraded _after_ the kernel is completely rebuilt. I am hitting this _during_ the rebuild. So the question becomes: _will_ removing the IGNORE line work? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 the kernel because drm-current-kmod is out-of-date. When I try to upgrade drm-current-kmod (r561457) I get: ===> drm-current-kmod-5.4.62.g20210113 not supported on older CURRENT, no kernel support. *** Error code 1 Stop. make: stopped in /usr/ports/graphics/drm-current-kmod Huh? What is my path forward? (That does not involve reinstalling the OS.) Either upgrade the kernel without the drm PORTS_ whatever thing → upgrade drm-current-kmod → add back the PORTS_thing if you really want it → upgrade kernel again or remove the IGNORE line in the port's Makefile → upgrade drm-current-kmod → upgrade the kernel. You have discovered precisely why this (building kmods from ports when building the kernel itself) is not a very good feature :) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
"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. When I try to upgrade drm-current-kmod (r561457) I get: ===> drm-current-kmod-5.4.62.g20210113 not supported on older CURRENT, no kernel support. *** Error code 1 Stop. make: stopped in /usr/ports/graphics/drm-current-kmod Huh? What is my path forward? (That does not involve reinstalling the OS.) Anxiously, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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). Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 make buildkernel > those sources are getting built too. That would be the SOURCE option? Yes 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). (And I assume a note about this will appear in UPDATING?) A note about what ? Cheers, Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 sources are getting built too. > > That would be the SOURCE option? Yes > Further: if I have that set ... does that mean I can remove it > from PORTS_MODULES? I don't know what that is > (And I assume a note about this will appear in UPDATING?) A note about what ? Cheers, > > Respectfully, > > > Robert Huff > > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Emmanuel Vadot ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 option? Further: if I have that set ... does that mean I can remove it from PORTS_MODULES? (And I assume a note about this will appear in UPDATING?) Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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_ buildkernel (installkernel??) for reasons I > thought I understood. > You are telling me I need to update this _before_ buildkernel? > > > Perplexedly, > > > Robert Huff > 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. One problem is that when, like with the latest update to linuxkpi that I did, we introduce changes that breaks external kmods, you first need to upgrade your ports/package (not your ports tree) so the new sources are updated too and then do a make buildkernel. That really sucks but still helps a bit when there isn't conflicted changes in the source tree but you still need to rebuild your kernel module. -- Emmanuel Vadot ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 _after_ buildkernel (installkernel??) for reasons I
> thought I understood.
> You are telling me I need to update this _before_ buildkernel?
>
>
> Perplexedly,
>
He telling you to update the port itself -- e.g.,
/usr/ports/graphics/drm-kmod, as the port was recently updated:
r561457 | manu | 2021-01-13 03:22:25 -0800 (Wed, 13 Jan 2021) | 6 lines
graphics/drm-{current,devel}-kmod: Update to latest source
This fix a compilation problem with a pre 1300135 source tree.
Reported by:Filippo Moretti
So you need to update the "ports files" to get that update, then rebuild
the port (in concert with rebuilding the kernel, as you are doing).
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
"What happened at the Capitol last Wednesday, then, wasn't the first
time Trump's base took him literally. It was the culmination of having
taken him literally the entire duration of his presidency." - Chris Cillizza
See https://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
Re: Current kernel build broken with linuxkpi?
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. You are telling me I need to update this _before_ buildkernel? Perplexedly, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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@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 DRM port you are using before the issue will > be fixed. > > --HPS > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" OpenPGP_signature Description: OpenPGP digital signature
Re: Current kernel build broken with linuxkpi?
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 DRM port you are using before the issue will be fixed. --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Current kernel build broken with linuxkpi?
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 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 update your ports tree. I believe manu@ just fixed this. > > --HPS > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscr...@freebsd.org" OpenPGP_signature Description: OpenPGP digital signature
Re: Current kernel build broken with linuxkpi?
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 update your ports tree. I believe manu@ just fixed this. --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Current kernel build broken with linuxkpi?
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 digital signature
Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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 process for the aicasm tool so that it gets built as I> > I> > I> part of the toolchain rather than as part of the kernel now. I> > I> > I> > I> > Before this change, the toolchain was not required for kernel build if you I> > I> > aren't cross building. And now it is. This breaks the kernel build procedure I> > I> > documented in handbook for years, and brings a lot of discomfort to I> > I> > developers. I> > I> > I> > I> > Now to test a trivial change to kernel I need first to compile clang. I> > I> > I> > I> I> > I> I didn't realize the change would have that effect. Building aicasm I> > I> using the kernel build machinery just isn't an option anymore, it builds I> > I> in the wrong environment with the wrong header files and sometimes the I> > I> wrong toolchain when cross-building. But there should be a solution I> > I> that doesn't require building clang, I'll see what can be done. I> > I> > Thanks, Ian. While you are seekign solution we can sustain with depending I> > on toolchain build. I> > I> I> Okay, I think I've got a potential solution, please try the attached I> patch. Now the "make buildkernel" when the objdir is empty should build I> just the aicasm tool. (In retrospect, WTF was I thinking adding it to I> the cross-build tools? I guess cross-building is just too central to my I> world these days.) I> I> Maybe for testing you should rename your existing objdir rather than I> cleaning it out, just in case this doesn't work you can rename it back I> instead of building clang all over again. :) That worked for me. Thanks! -- Totus tuus, Glebius. ___ 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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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 toolchain rather than as part of the kernel now.
> I> >
> I> > Before this change, the toolchain was not required for kernel build if
> you
> I> > aren't cross building. And now it is. This breaks the kernel build
> procedure
> I> > documented in handbook for years, and brings a lot of discomfort to
> I> > developers.
> I> >
> I> > Now to test a trivial change to kernel I need first to compile clang.
> I> >
> I>
> I> I didn't realize the change would have that effect. Building aicasm
> I> using the kernel build machinery just isn't an option anymore, it builds
> I> in the wrong environment with the wrong header files and sometimes the
> I> wrong toolchain when cross-building. But there should be a solution
> I> that doesn't require building clang, I'll see what can be done.
>
> Thanks, Ian. While you are seekign solution we can sustain with depending
> on toolchain build.
>
Okay, I think I've got a potential solution, please try the attached
patch. Now the "make buildkernel" when the objdir is empty should build
just the aicasm tool. (In retrospect, WTF was I thinking adding it to
the cross-build tools? I guess cross-building is just too central to my
world these days.)
Maybe for testing you should rename your existing objdir rather than
cleaning it out, just in case this doesn't work you can rename it back
instead of building clang all over again. :)
-- Ian
Index: Makefile.inc1
===
--- Makefile.inc1 (revision 257712)
+++ Makefile.inc1 (working copy)
@@ -439,6 +439,16 @@ IMAKE_MTREE= MTREE_CMD="nmtree ${MTREEFLAGS}"
KMAKEENV= ${WMAKEENV}
KMAKE= ${KMAKEENV} ${MAKE} ${.MAKEFLAGS} ${KERNEL_FLAGS} KERNEL=${INSTKERNNAME}
+# kernel build-tools stage
+KTMAKE= MAKEOBJDIRPREFIX=${WORLDTMP} \
+ ${WMAKEENV} ${MAKE} -f Makefile.inc1 \
+ TARGET=${TARGET} TARGET_ARCH=${TARGET_ARCH} \
+ DESTDIR= \
+ BOOTSTRAPPING=${OSRELDATE} \
+ SSP_CFLAGS= \
+ -DNO_LINT \
+ -DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF -DEARLY_BUILD
+
#
# buildworld
#
@@ -1019,7 +1029,7 @@ buildkernel:
@echo "--"
@echo ">>> stage 2.3: build tools"
@echo "--"
- @# Currently no special kernel tools to build.
+ ${_+_}cd ${.CURDIR}; ${KTMAKE} kernel-tools
.if !defined(NO_KERNELDEPEND)
@echo
@echo "--"
@@ -1347,6 +1357,23 @@ build-tools: .MAKE
.endfor
#
+# kernel-tools: Build kernel-building tools
+#
+kernel-tools: .MAKE
+ mkdir -p ${WORLDTMP}/usr
+ mtree -deU -f ${.CURDIR}/etc/mtree/BSD.usr.dist \
+ -p ${WORLDTMP}/usr >/dev/null
+.for _tool in \
+sys/dev/aic7xxx/aicasm
+ ${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all,install)"; \
+ cd ${.CURDIR}/${_tool} && \
+ ${MAKE} DIRPRFX=${_tool}/ obj && \
+ ${MAKE} DIRPRFX=${_tool}/ depend && \
+ ${MAKE} DIRPRFX=${_tool}/ all && \
+ ${MAKE} DIRPRFX=${_tool}/ DESTDIR=${WORLDTMP} install
+.endfor
+
+#
# cross-tools: Build cross-building tools
#
.if ${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING} < 800035
@@ -1393,7 +1420,6 @@ cross-tools: .MAKE
${_btxld} \
${_crunchide} \
${_kgzip} \
-sys/dev/aic7xxx/aicasm
${_+_}@${ECHODIR} "===> ${_tool} (obj,depend,all,install)"; \
cd ${.CURDIR}/${_tool} && \
${MAKE} DIRPRFX=${_tool}/ obj && \
___
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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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) > > I> > > > *** Error code 1 > > I> > > > > > I> > > > Stop. > > I> > > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > > I> > > > *** Error code 1 > > I> > > > > > I> > > > Stop. > > I> > > > make[1]: stopped in /usr/src > > I> > > > > I> > > Did you update your source and then "make buildkernel" without > > I> > > buildworld? If so, a "make kernel-toolchain" should create the > > aicasm > > I> > > tool and get you back on track. > > I> > > > > I> > > > I> > really odd as i built a kernel this morning no problem, then updated > > the > > I> > tree and went to build another kernel and got that. > > I> > working through it, thanks for the input.. > > I> > > > I> > > I> You were just unlucky that your updates bracketed my checkin that > > I> changed the build process for the aicasm tool so that it gets built as > > I> part of the toolchain rather than as part of the kernel now. > > > > Before this change, the toolchain was not required for kernel build if you > > aren't cross building. And now it is. This breaks the kernel build procedure > > documented in handbook for years, and brings a lot of discomfort to > > developers. > > > > Now to test a trivial change to kernel I need first to compile clang. > > > > I didn't realize the change would have that effect. Building aicasm > using the kernel build machinery just isn't an option anymore, it builds > in the wrong environment with the wrong header files and sometimes the > wrong toolchain when cross-building. But there should be a solution > that doesn't require building clang, I'll see what can be done. We should probalby just install it in /usr/bin. The last functional change was in 2010 and the last before that was 2003. -- Brooks pgpsw5aA7QNIC.pgp Description: PGP signature
Re: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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 this change, the toolchain was not required for kernel build if you I> > aren't cross building. And now it is. This breaks the kernel build procedure I> > documented in handbook for years, and brings a lot of discomfort to I> > developers. I> > I> > Now to test a trivial change to kernel I need first to compile clang. I> > I> I> I didn't realize the change would have that effect. Building aicasm I> using the kernel build machinery just isn't an option anymore, it builds I> in the wrong environment with the wrong header files and sometimes the I> wrong toolchain when cross-building. But there should be a solution I> that doesn't require building clang, I'll see what can be done. Thanks, Ian. While you are seekign solution we can sustain with depending on toolchain build. -- Totus tuus, Glebius. ___ 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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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> > > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > I> > > > *** Error code 1 > I> > > > > I> > > > Stop. > I> > > > make[1]: stopped in /usr/src > I> > > > I> > > Did you update your source and then "make buildkernel" without > I> > > buildworld? If so, a "make kernel-toolchain" should create the aicasm > I> > > tool and get you back on track. > I> > > > I> > > I> > really odd as i built a kernel this morning no problem, then updated the > I> > tree and went to build another kernel and got that. > I> > working through it, thanks for the input.. > I> > > I> > I> You were just unlucky that your updates bracketed my checkin that > I> changed the build process for the aicasm tool so that it gets built as > I> part of the toolchain rather than as part of the kernel now. > > Before this change, the toolchain was not required for kernel build if you > aren't cross building. And now it is. This breaks the kernel build procedure > documented in handbook for years, and brings a lot of discomfort to > developers. > > Now to test a trivial change to kernel I need first to compile clang. > I didn't realize the change would have that effect. Building aicasm using the kernel build machinery just isn't an option anymore, it builds in the wrong environment with the wrong header files and sometimes the wrong toolchain when cross-building. But there should be a solution that doesn't require building clang, I'll see what can be done. -- Ian ___ 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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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> > > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > I> > > > *** Error code 1 > I> > > > > I> > > > Stop. > I> > > > make[1]: stopped in /usr/src > I> > > > I> > > Did you update your source and then "make buildkernel" without > I> > > buildworld? If so, a "make kernel-toolchain" should create the > aicasm > I> > > tool and get you back on track. > I> > > > I> > > I> > really odd as i built a kernel this morning no problem, then updated > the > I> > tree and went to build another kernel and got that. > I> > working through it, thanks for the input.. > I> > > I> > I> You were just unlucky that your updates bracketed my checkin that > I> changed the build process for the aicasm tool so that it gets built as > I> part of the toolchain rather than as part of the kernel now. > > Before this change, the toolchain was not required for kernel build if you > aren't cross building. And now it is. This breaks the kernel build > procedure > documented in handbook for years, and brings a lot of discomfort to > developers. > > Now to test a trivial change to kernel I need first to compile clang. > > I concur, I feel this is a bit invasive and unneccesary, as custom build scripts now also fail, what has worked for years without issue is now completely broken, it makes no sense to me to have to build a toolchain just to build a kernel everytime. > -- > Totus tuus, Glebius. > ___ 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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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 code 1 I> > > > I> > > > Stop. I> > > > make[1]: stopped in /usr/src I> > > I> > > Did you update your source and then "make buildkernel" without I> > > buildworld? If so, a "make kernel-toolchain" should create the aicasm I> > > tool and get you back on track. I> > > I> > I> > really odd as i built a kernel this morning no problem, then updated the I> > tree and went to build another kernel and got that. I> > working through it, thanks for the input.. I> > I> I> You were just unlucky that your updates bracketed my checkin that I> changed the build process for the aicasm tool so that it gets built as I> part of the toolchain rather than as part of the kernel now. Before this change, the toolchain was not required for kernel build if you aren't cross building. And now it is. This breaks the kernel build procedure documented in handbook for years, and brings a lot of discomfort to developers. Now to test a trivial change to kernel I need first to compile clang. -- Totus tuus, Glebius. ___ 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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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 -Wmissing-prototypes -Wpointer-arith > > > -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > > > -Wmissing-include-dirs -fdiagnostics-show-option > > > -Wno-error-tautological-compare -Wno-error-empty-body > > > -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys > > > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > > > -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal > > > -I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm > > > -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe > > > -I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > > > -include opt_global.h -fno-omit-frame-pointer > > -mno-omit-leaf-frame-pointer > > > -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > > > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > > > -fstack-protector /usr/src/sys/amd64/amd64/genassym.c > > > NM='nm' sh /usr/src/sys/kern/genassym.sh genassym.o > assym.s > > > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -p > > > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -q > > > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -h > > > awk -f /usr/src/sys/tools/acpi_quirks2h.awk > > > /usr/src/sys/dev/acpica/acpi_quirks > > > aicasm -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq > > > -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath > > > -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal > > > -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa > > -I/usr/src/sys/dev/cxgb > > > -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt > > > -I/usr/src/sys/cam/scsi -I/usr/src/sys/dev/aic7xxx -o aic7xxx_seq.h -r > > > aic7xxx_reg.h -p aic7xxx_reg_print.c -i > > > /usr/src/sys/dev/aic7xxx/aic7xxx_osm.h > > /usr/src/sys/dev/aic7xxx/aic7xxx.seq > > > make[2]: exec(aicasm) failed (No such file or directory) > > > *** Error code 1 > > > > > > Stop. > > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > > > *** Error code 1 > > > > > > Stop. > > > make[1]: stopped in /usr/src > > > > Did you update your source and then "make buildkernel" without > > buildworld? If so, a "make kernel-toolchain" should create the aicasm > > tool and get you back on track. > > > > really odd as i built a kernel this morning no problem, then updated the > tree and went to build another kernel and got that. > working through it, thanks for the input.. > You were just unlucky that your updates bracketed my checkin that changed the build process for the aicasm tool so that it gets built as part of the toolchain rather than as part of the kernel now. -- Ian ___ 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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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 -Wno-pointer-sign -fformat-extensions > > -Wmissing-include-dirs -fdiagnostics-show-option > > -Wno-error-tautological-compare -Wno-error-empty-body > > -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys > > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > > -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal > > -I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm > > -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe > > -I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > > -include opt_global.h -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer > > -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > > -fstack-protector /usr/src/sys/amd64/amd64/genassym.c > > NM='nm' sh /usr/src/sys/kern/genassym.sh genassym.o > assym.s > > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -p > > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -q > > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -h > > awk -f /usr/src/sys/tools/acpi_quirks2h.awk > > /usr/src/sys/dev/acpica/acpi_quirks > > aicasm -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq > > -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath > > -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal > > -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa > -I/usr/src/sys/dev/cxgb > > -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt > > -I/usr/src/sys/cam/scsi -I/usr/src/sys/dev/aic7xxx -o aic7xxx_seq.h -r > > aic7xxx_reg.h -p aic7xxx_reg_print.c -i > > /usr/src/sys/dev/aic7xxx/aic7xxx_osm.h > /usr/src/sys/dev/aic7xxx/aic7xxx.seq > > make[2]: exec(aicasm) failed (No such file or directory) > > *** Error code 1 > > > > Stop. > > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > > *** Error code 1 > > > > Stop. > > make[1]: stopped in /usr/src > > Did you update your source and then "make buildkernel" without > buildworld? If so, a "make kernel-toolchain" should create the aicasm > tool and get you back on track. > really odd as i built a kernel this morning no problem, then updated the tree and went to build another kernel and got that. working through it, thanks for the input.. > > -- Ian > > > ___ 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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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-dirs -fdiagnostics-show-option > -Wno-error-tautological-compare -Wno-error-empty-body > -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal > -I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm > -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe > -I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer > -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > -fstack-protector /usr/src/sys/amd64/amd64/genassym.c > NM='nm' sh /usr/src/sys/kern/genassym.sh genassym.o > assym.s > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -p > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -q > awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -h > awk -f /usr/src/sys/tools/acpi_quirks2h.awk > /usr/src/sys/dev/acpica/acpi_quirks > aicasm -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq > -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath > -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal > -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb > -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt > -I/usr/src/sys/cam/scsi -I/usr/src/sys/dev/aic7xxx -o aic7xxx_seq.h -r > aic7xxx_reg.h -p aic7xxx_reg_print.c -i > /usr/src/sys/dev/aic7xxx/aic7xxx_osm.h /usr/src/sys/dev/aic7xxx/aic7xxx.seq > make[2]: exec(aicasm) failed (No such file or directory) > *** Error code 1 > > Stop. > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src Did you update your source and then "make buildkernel" without buildworld? If so, a "make kernel-toolchain" should create the aicasm tool and get you back on track. -- Ian ___ 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"
CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)
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 -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector /usr/src/sys/amd64/amd64/genassym.c NM='nm' sh /usr/src/sys/kern/genassym.sh genassym.o > assym.s awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -p awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -q awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -h awk -f /usr/src/sys/tools/acpi_quirks2h.awk /usr/src/sys/dev/acpica/acpi_quirks aicasm -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt -I/usr/src/sys/cam/scsi -I/usr/src/sys/dev/aic7xxx -o aic7xxx_seq.h -r aic7xxx_reg.h -p aic7xxx_reg_print.c -i /usr/src/sys/dev/aic7xxx/aic7xxx_osm.h /usr/src/sys/dev/aic7xxx/aic7xxx.seq make[2]: exec(aicasm) failed (No such file or directory) *** Error code 1 Stop. make[2]: stopped in /usr/obj/usr/src/sys/GENERIC *** Error code 1 Stop. make[1]: stopped in /usr/src ___ 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: CUURENT kernel build broken - /usr/src/sys/dev/xen/netback/netback.c
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, Glebius.
___
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"
CUURENT kernel build broken - /usr/src/sys/dev/xen/netback/netback.c
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 -Wno-error-empty-body
-Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
/usr/src/sys/dev/xen/control/control.c
ctfconvert -L VERSION -g control.o
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 -Wno-error-empty-body
-Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
/usr/src/sys/dev/xen/netback/netback.c
/usr/src/sys/dev/xen/netback/netback.c:588:7: error: incomplete definition
of type 'struct mbuf'
if (m->m_flags & M_PKTHDR) {
~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
^
/usr/src/sys/dev/xen/netback/netback.c:588:19: error: use of undeclared
identifier 'M_PKTHDR'
if (m->m_flags & M_PKTHDR) {
^
/usr/src/sys/dev/xen/netback/netback.c:591:11: error: incomplete definition
of type 'struct mbuf'
m->m_pkthdr.flowid, (int)m->m_pkthdr.csum_flags,
~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
^
/usr/src/sys/dev/xen/netback/netback.c:594:11: error: incomplete definition
of type 'struct mbuf'
m->m_pkthdr.rcvif, m->m_pkthdr.len);
~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
^
/usr/src/sys/dev/xen/netback/netback.c:597:10: error: incomplete definition
of type 'struct mbuf'
m->m_next, m->m_nextpkt, m->m_data);
~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
^
/usr/src/sys/dev/xen/netback/netback.c:599:10: error: incomplete definition
of type 'struct mbuf'
m->m_len, m->m_flags, m->m_type);
~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
^
/usr/src/sys/dev/xen/netback/netback.c:601:9: error: incomplete definition
of type 'struct mbuf'
len = m->m_len;
~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
^
/usr/src/sys/dev/xen/netback/netback.c:602:6: error: implicit declaration
of function 'mtod' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
d = mtod(m, uint8_t*);
^
/usr/src/sys/dev/xen/netback/netback.c:602:14: error: unexpected type name
'uint8_t': expected expression
d = mtod(m, uint8_t*);
^
/usr/src/sys/dev/xen/netback/netback.c:602:22: error: expected expression
d = mtod(m, uint8_t*);
^
/usr/src/sys/dev/xen/netback/netback.c:1071:3: error: implicit declaration
of function 'if_free' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if_free(xnb->xnb_ifp);
^
/usr/src/sys/dev/xen/netback/netback.c:1213:24: error: implicit declaration
of function 'if_alloc' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
ifp = xnb->xnb_ifp = if_alloc(IFT_ETHER);
^
/usr/src/sys/dev/xen/netback/netback.c:1213:22: error: incompatible integer
to pointer conversion assigning to 'struct ifnet *' from 'int'
[-Werror,-Wint-conversion]
ifp = xnb->xnb_ifp = if_alloc(IFT_ETHER);
^ ~~~
/usr/src/sys/dev/xen/netback/netback.c:1214:6: error: incomplete definition
of type 'struct ifnet'
ifp->if_softc = xnb;
~~~^
/usr/src/sys/net/if_arp.h:106:10: note: forward declaration of 'struct
ifnet'
struct ifnet *ac_ifp; /* network-visible interface */
^
/usr/src/sys/dev/xen/netback/netback.c:1215:3: error: implicit declaration
of function 'if_initname' is invalid in C99
[-Werror,-Wim
Re: stable/8 kernel build broken on head without WITH_CTF
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"
Re: -STABLE kernel build broken?
>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 MFC of some changes to mbuf.h also needed some
>> corresponding changes elsewhere (such as netncp/ncp_rq.c).
>> /usr/src/sys/sys/mbuf.h is:
>> * $FreeBSD: src/sys/sys/mbuf.h,v 1.44.2.9 2001/05/21 07:01:44 bp Exp $
>> and /usr/src/sys/netncp/ncp_rq.c is:
>> * $FreeBSD: src/sys/netncp/ncp_rq.c,v 1.1 1999/10/02 04:06:17 bp Exp $
>> (The latter is up to 1.7 in -CURRENT.)
>1.3 without M_WAIT -> M_TRYWAIT should work.
OK; I extracted 1.3 & tried it, when that broke, I figured out what you
meant by "without M_WAIT -> M_TRYWAIT", and did a global change
("%s/M_TRYWAIT/M_WAIT/g", for other vi-speakers). And that worked;
kernel built & installed, and I'm installing the world at the moment.
Thanks,
david
--
David H. Wolfskill [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -STABLE kernel build broken?
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 #20: Sun May 20 >06:23:46 PDT 2001 >[EMAIL PROTECTED]:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 > > Tail end of the log: > > >>> Kernel build for LAPTOP_30W started on Mon May 21 06:25:33 PDT 2001 > ... > ===> msdos > ... > ===> ncp > ... > cc -O -pipe -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@/../include -mpreferred-stack-boundary=2 -c >/usr/src/sys/modules/ncp/../../netncp/ncp_rq.c > /usr/src/sys/modules/ncp/../../netncp/ncp_rq.c:49: conflicting types for `m_getm' > @/sys/mbuf.h:572: previous declaration of `m_getm' > /usr/src/sys/modules/ncp/../../netncp/ncp_rq.c:49: warning: redundant redeclaration >of `m_getm' in same scope > @/sys/mbuf.h:572: warning: previous declaration of `m_getm' > *** Error code 1 > > Stop in /usr/src/sys/modules/ncp. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /common/S2/obj/usr/src/sys/LAPTOP_30W. > *** Error code 1 > > > /usr/src/sys/sys/mbuf.h is: > * $FreeBSD: src/sys/sys/mbuf.h,v 1.44.2.9 2001/05/21 07:01:44 bp Exp $ > > and /usr/src/sys/netncp/ncp_rq.c is: > * $FreeBSD: src/sys/netncp/ncp_rq.c,v 1.1 1999/10/02 04:06:17 bp Exp $ > > (The latter is up to 1.7 in -CURRENT.) > 1.3 without M_WAIT -> M_TRYWAIT should work. -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-STABLE kernel build broken?
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/src/sys/LAPTOP_30W i386 Tail end of the log: >>> Kernel build for LAPTOP_30W started on Mon May 21 06:25:33 PDT 2001 ... ===> msdos ... ===> ncp ... cc -O -pipe -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@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/ncp/../../netncp/ncp_rq.c /usr/src/sys/modules/ncp/../../netncp/ncp_rq.c:49: conflicting types for `m_getm' @/sys/mbuf.h:572: previous declaration of `m_getm' /usr/src/sys/modules/ncp/../../netncp/ncp_rq.c:49: warning: redundant redeclaration of `m_getm' in same scope @/sys/mbuf.h:572: warning: previous declaration of `m_getm' *** Error code 1 Stop in /usr/src/sys/modules/ncp. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /common/S2/obj/usr/src/sys/LAPTOP_30W. *** Error code 1 /usr/src/sys/sys/mbuf.h is: * $FreeBSD: src/sys/sys/mbuf.h,v 1.44.2.9 2001/05/21 07:01:44 bp Exp $ and /usr/src/sys/netncp/ncp_rq.c is: * $FreeBSD: src/sys/netncp/ncp_rq.c,v 1.1 1999/10/02 04:06:17 bp Exp $ (The latter is up to 1.7 in -CURRENT.) Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current kernel build broken in sc0
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_CONS_REV_ATTR=(FG_BLACK|BG_RED) | | [snip make depend] | genassym.c | /kern/link_aout.c /usr/src/sys/kern/subr_diskmbr.c /usr/src/sys/libkern/divdi3.c |/usr/src/sys/libkern/moddi3.c /usr/src/sys/libkern/qdivrem.c |/usr/src/sys/libkern/ucmpdi2.c /usr/src/sys/libkern/udivdi3.c |/usr/src/sys/libkern/umoddi3.c param.c vnode_if.c hints.c config.c |/usr/src/sys/i386/i386/genassym.c | In file included from /usr/src/sys/dev/fb/vga.c:34: | opt_syscons.h:2: unterminated string or character constant | opt_syscons.h:2: possible real start of unterminated constant | In file included from /usr/src/sys/dev/syscons/schistory.c:33: | opt_syscons.h:2: unterminated string or character constant | opt_syscons.h:2: possible real start of unterminated constant | In file included from /usr/src/sys/dev/syscons/scmouse.c:29: | opt_syscons.h:2: unterminated string or character constant | opt_syscons.h:2: possible real start of unterminated constant | Sorry, forgot to mention that it was fresh src/ cvsupped three hours ago. -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current kernel build broken in sc0
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_CONS_REV_ATTR=(FG_BLACK|BG_RED) [snip make depend] genassym.c /kern/link_aout.c /usr/src/sys/kern/subr_diskmbr.c /usr/src/sys/libkern/divdi3.c /usr/src/sys/libkern/moddi3.c /usr/src/sys/libkern/qdivrem.c /usr/src/sys/libkern/ucmpdi2.c /usr/src/sys/libkern/udivdi3.c /usr/src/sys/libkern/umoddi3.c param.c vnode_if.c hints.c config.c /usr/src/sys/i386/i386/genassym.c In file included from /usr/src/sys/dev/fb/vga.c:34: opt_syscons.h:2: unterminated string or character constant opt_syscons.h:2: possible real start of unterminated constant In file included from /usr/src/sys/dev/syscons/schistory.c:33: opt_syscons.h:2: unterminated string or character constant opt_syscons.h:2: possible real start of unterminated constant In file included from /usr/src/sys/dev/syscons/scmouse.c:29: opt_syscons.h:2: unterminated string or character constant opt_syscons.h:2: possible real start of unterminated constant -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current Kernel build broken
On Sun, 29 Oct 2000, Manfred Antar wrote:
> From latest sources:
> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
>-g -nostdinc -I- -I. -I../.. -I../../../include
>-I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf
>-mpreferred-stack-boundary=2 ../../ufs/ufs/ufs_vfsops.c
> ../../ufs/ufs/ufs_vfsops.c: In function `ufs_quotactl':
> ../../ufs/ufs/ufs_vfsops.c:119: warning: implicit declaration of function `suser_xxx'
> ../../ufs/ufs/ufs_vfsops.c:119: `PRISON_ROOT' undeclared (first use in this function)
> ../../ufs/ufs/ufs_vfsops.c:119: (Each undeclared identifier is reported only once
> ../../ufs/ufs/ufs_vfsops.c:119: for each function it appears in.)
> *** Error code 1
Poul-henning recently committed changes to make suser{,_xxx}() be defined
in system.h instead of proc.h. If ufs_vfsops.c doesn't include systm.h,
it may now be broken. However, it's probably more likely that you cvsup'd
during his commit, and need to update your source tree to make sure all
files are properly in synch.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Current Kernel build broken
From latest sources: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../ufs/ufs/ufs_vfsops.c ../../ufs/ufs/ufs_vfsops.c: In function `ufs_quotactl': ../../ufs/ufs/ufs_vfsops.c:119: warning: implicit declaration of function `suser_xxx' ../../ufs/ufs/ufs_vfsops.c:119: `PRISON_ROOT' undeclared (first use in this function) ../../ufs/ufs/ufs_vfsops.c:119: (Each undeclared identifier is reported only once ../../ufs/ufs/ufs_vfsops.c:119: for each function it appears in.) *** Error code 1 == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel build broken...
> during the mkdep, I get: > > ../../kern/kern_linker.c:49: linker_if.h: No such file or directory > ../../kern/link_aout.c:45: linker_if.h: No such file or directory > ../../kern/link_elf.c:55: linker_if.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/sys/compile/MONITOR. > > > And the compile fails. I can't find linker_if.h anywhere. Hi, Eric. I noticed that too, but it's fixed now (for me anyway). I see this in the commit logs: obrien 2000/04/24 16:08:25 PDT Modified files: sys/conf files Log: Add linker_if.m to the mix. Revision ChangesPath 1.359 +2 -1 src/sys/conf/files -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel build broken...
during the mkdep, I get: ../../kern/kern_linker.c:49: linker_if.h: No such file or directory ../../kern/link_aout.c:45: linker_if.h: No such file or directory ../../kern/link_elf.c:55: linker_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/compile/MONITOR. And the compile fails. I can't find linker_if.h anywhere. -eric To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel build broken without INET6
> Patch included... Sorry for it and thanks for the patch. I'll committ the fix. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel build broken without INET6
Patch included... Index: in_pcb.c === RCS file: /home/ncvs/src/sys/netinet/in_pcb.c,v retrieving revision 1.61 diff -u -r1.61 in_pcb.c --- in_pcb.c2000/04/01 22:35:43 1.61 +++ in_pcb.c2000/04/02 03:14:15 @@ -153,10 +153,12 @@ inp->inp_gencnt = ++pcbinfo->ipi_gencnt; inp->inp_pcbinfo = pcbinfo; inp->inp_socket = so; +#ifdef INET6 if (ip6_mapped_addr_on) inp->inp_flags &= ~IN6P_BINDV6ONLY; else inp->inp_flags |= IN6P_BINDV6ONLY; +#endif LIST_INSERT_HEAD(pcbinfo->listhead, inp, inp_list); pcbinfo->ipi_count++; so->so_pcb = (caddr_t)inp; -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current Kernel build broken
> With current source tree as of 9 am pacific, I can no longer build a kernel : My mistake; should be fixed now. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current Kernel build broken
With current source tree as of 9 am pacific, I can no longer build a kernel : cc -c -O2 -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_glob al.h -elf ../../dev/dpt/dpt_scsi.c ../../dev/dpt/dpt_scsi.c: In function `dpt_get_conf': ../../dev/dpt/dpt_scsi.c:389: warning: cast discards `volatile' from pointer tar get type ../../dev/dpt/dpt_scsi.c: In function `dpt_detect_cache': ../../dev/dpt/dpt_scsi.c:496: warning: cast discards `volatile' from pointer tar get type ../../dev/dpt/dpt_scsi.c: In function `dpt_init': ../../dev/dpt/dpt_scsi.c:1187: warning: cast discards `volatile' from pointer ta rget type ../../dev/dpt/dpt_scsi.c: In function `dpt_attach': ../../dev/dpt/dpt_scsi.c:1410: warning: implicit declaration of function `EVENTH ANDLER_REGISTER' ../../dev/dpt/dpt_scsi.c:1410: `shutdown_final' undeclared (first use in this fu nction) ../../dev/dpt/dpt_scsi.c:1410: (Each undeclared identifier is reported only once ../../dev/dpt/dpt_scsi.c:1410: for each function it appears in.) ../../dev/dpt/dpt_scsi.c:1411: `SHUTDOWN_PRI_DEFAULT' undeclared (first use in t his function) *** Error code 1 Stop in /usr/src/sys/compile/pro2. = ||[EMAIL PROTECTED] || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
