Re: make world stops during i4b compilation
On Sunday 25 March 2001 00:11, Marc van Woerkom wrote: Ok, I did an ediff against NOTES. Perhaps it was the "1" argument to device loop1 #Network loopback device that was missing. I'll try again. Hmmm Seems odd. If you get a recurrence, you might want to share a diff between GENERIC and what you're using. Now it compiles. I had to put in a "device ether" line into my config to compile a kernel with i4b (IDSN) drivers. And this on box without ethernet card. Is this a bug or a feature? i4b is an ethernet interface, how do you think PPP/HDLC works ? The interface is registered with the networking stack, just like a "real" networking card is. This make the ether device mandatory. -- Gary Jennejohn [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world stops during i4b compilation
i4b is an ethernet interface, how do you think PPP/HDLC works ? The interface is registered with the networking stack, just like a "real" networking card is. This make the ether device mandatory. Hi Gary! I simply lack knowledge of how network devices are organized. It might have been possible that network devices exist, that don't belong to that class of ethernet interfaces. I believed that i4b might be such a device, as I can't remember pulling in "ether" in my older kernel configs. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world stops during i4b compilation
On Sunday 25 March 2001 13:53, Marc van Woerkom wrote: i4b is an ethernet interface, how do you think PPP/HDLC works ? The interface is registered with the networking stack, just like a "real" networking card is. This make the ether device mandatory. Hi Gary! I simply lack knowledge of how network devices are organized. It might have been possible that network devices exist, that don't belong to that class of ethernet interfaces. I believed that i4b might be such a device, as I can't remember pulling in "ether" in my older kernel configs. well, it seems that I'm wrong. Hellmuth Michaelis tells me that it _should_ be possible to use i4b without ether. Looks like this is a bug. -- Gary Jennejohn [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world stops during i4b compilation
Hi, anyone has this problem too? (..) cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c sh /usr/src/sys/conf/newvers.sh ORANJE cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/../include -I/usr/src/sys/contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 vers.c linking kernel i4b_ipr.o: In function `i4biprattach': i4b_ipr.o(.text+0x1d2): undefined reference to `ether_ifattach' i4b_isppp.o: In function `i4bispppattach': i4b_isppp.o(.text+0x179): undefined reference to `ether_ifattach' *** Error code 1 Stop in /usr3/obj/usr/src/sys/ORANJE. *** Error code 1 Compiling the GENERIC kernel however works fine.. hmmm. Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world stops during i4b compilation
Ok, I did an ediff against NOTES. Perhaps it was the "1" argument to device loop1 #Network loopback device that was missing. I'll try again. Hmmm Seems odd. If you get a recurrence, you might want to share a diff between GENERIC and what you're using. Now it compiles. I had to put in a "device ether" line into my config to compile a kernel with i4b (IDSN) drivers. And this on box without ethernet card. Is this a bug or a feature? Regards, Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
