Re: problem building linux kernel module in current
On Fri, 06 Apr 2001, John Carlson wrote:
Hi,
I cvsupped today to -CURRENT, thinking to upgrade my -STABLE installation
(4.3-BETA). I followed the instructions in the UPDATING file, but ran into
a persistent problem when trying to compile the kernel after a successful
buildworld. The kernel compilation dies while making the modules at this
point:
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@/dev -I@/../include -mpreferred-stack-boundary=2 -c linux_sysent.c
linux_sysent.c:21: sizeof applied to an incomplete type
linux_sysent.c:21: warning: built-in function `exit' used without
declaration
linux_sysent.c:21: warning: cast discards qualifiers from pointer target
type
*** Error code 1
Anyone else noticed this problem or is it just me doing something wrong?
Any help would be appreciated.
Hmm... I also noticed this problem, after following the UPDATING
instructions to get from 4.3-RC - 5.0-CURRENT...
I managed to get the kernel to build successfully by hacking at the
linux_sysent.c file...
For some reason, the sys_exit line in linux_sysent.c in /usr/src gets
changed to something which breaks when it gets copied into /usr/obj...
(IIRC, I don't have both copies of the file available any more)
{ AS(sys_exit_args), (sy_call_t *)sys_exit }, /* 1 = exit */
was changed to something like
{ AS(rexit), (sy_call_t *)exit }, /* 1 = exit */
^
The 'underlined' (^^^) bits are definately right, I'm not sure about the
cast...
Any one have any ideas what would cause that?
(presumably linux_sysent.c is getting regenerated, incorrectly, somewhere?)
--
David Taylor
[EMAIL PROTECTED]
PGP signature
Re: perl broken?
On Sat, Apr 07, 2001 at 10:41:30PM -0500, Michael Harnois wrote:
Different ports, similar problem:
/usr/bin/perl5 -I/usr/libdata/perl/5.6.0/mach -I/usr/libdata/perl/BSDPANIMAP.xs
IMAP.xsc mv IMAP.xsc IMAP.c
Arrrhgh. Thanks for the report.
Please try the following patch:
--- /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Thu Apr 5 22:21:44 2001
+++ /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Sun Apr 8 14:22:21 2001
@@ -102,6 +102,7 @@
eval "*\$name = sub {
\\\$repsub2-(
\\\$real_addr, \\\@_) };";
+ \@r;
}, \@_)
};
EOF
Cheers,
+Anton.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: perl broken?
On Sun, Apr 08, 2001 at 02:26:38PM +0200, Anton Berezin wrote:
On Sat, Apr 07, 2001 at 10:41:30PM -0500, Michael Harnois wrote:
Different ports, similar problem:
/usr/bin/perl5 -I/usr/libdata/perl/5.6.0/mach -I/usr/libdata/perl/BSDPAN
IMAP.xs IMAP.xsc mv IMAP.xsc IMAP.c
Arrrhgh. Thanks for the report.
Please try the following patch:
--- /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Thu Apr 5 22:21:44 2001
+++ /usr/libdata/perl/BSDPAN/BSDPAN/Override.pm Sun Apr 8 14:22:21 2001
@@ -102,6 +102,7 @@
eval "*\$name = sub {
\\\$repsub2-(
\\\$real_addr, \\\@_) };";
+ \@r;
}, \@_)
};
EOF
Forgot to add: you will need to make clean your port(s) to unbroke the
generated Makefile.
--
May the tuna salad be with you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: perl broken?
Much better, thanks! -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa One of the symptoms of an approaching nervous breakdown is the belief that one's work is terribly important. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
loader question
How do you make the loader _NOT_ load a kernel until after the countdown? On slow media (like NFS boots or VMware, or old AlphaServers) its really painful to wait for the kernel to unload just so you can unload it and then load an alternate kernel. Thanks, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: loader question
Andrew Gallatin wrote: How do you make the loader _NOT_ load a kernel until after the countdown? On slow media (like NFS boots or VMware, or old AlphaServers) its really painful to wait for the kernel to unload just so you can unload it and then load an alternate kernel. This initial load is done by the 4th code. I suspect it is configurable to not do this, but if you want to do it by brute force, nuke loader.rc and do it all by hand. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: loader question
Peter Wemm writes: Andrew Gallatin wrote: How do you make the loader _NOT_ load a kernel until after the countdown? On slow media (like NFS boots or VMware, or old AlphaServers) its really painful to wait for the kernel to unload just so you can unload it and then load an alternate kernel. This initial load is done by the 4th code. I suspect it is configurable to not do this, but if you want to do it by brute force, nuke loader.rc and do it all by hand. Actually, that doens't seem to work. (at least for a loader from last November). Given that the machine is 3K miles away, I think I'll just deal with the slowness for now not risk crippling it. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: loader question
Andrew Gallatin wrote: How do you make the loader _NOT_ load a kernel until after the countdown? On slow media (like NFS boots or VMware, or old AlphaServers) its really painful to wait for the kernel to unload just so you can unload it and then load an alternate kernel. Actually, it requires some work to do that. Previously, autoboot only loaded the kernel after the countdown, but that resulted in the small problem in the user _not_ knowing exactly what kernel was being loaded until after the countdown had finished. The stuff in examples/bootforth does something similar with the menu. The menu waits until you type a key or up to a certain amount of time, and then go do whatever it is that was selected/is default. You can look there for an example and adapt it to suit your needs, but Forth code is not particularly easy to understand, even something as simples as that. Of course, since you _are_ that far from the machine, I'd recommend testing anything locally first. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] all your kernels arpanic: blockable sleep lock (sleep mutex) Giant @ ../../kern/kern_sig.c:153 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
