Michael:
I suspect that you may have
options COMPAT_LINUX
defined in your kernel config file.
Re your problem with Linux not working. I had the same problem. It seems
to be related to the changes in the generation of the file
linux_assym.h. A new method for generating these kind of symbols was
introducted into the kernel build system today. The changes were not
promulgated to the generation of linux_assym.h.
The following change to /usr/src/modules/linux/Makefile will allow one
to at least build a workable linux module.
*** Makefile~ Sat May 27 10:04:09 2000
--- Makefile Sat Jun 3 00:11:05 2000
***************
*** 17,23 ****
CLEANFILES= linux_assym.h linux_genassym.o
linux_assym.h: linux_genassym.o
! genassym ${.ALLSRC} > ${.TARGET}
linux_locore.o: linux_locore.s linux_assym.h
${CC} -c -x assembler-with-cpp -DLOCORE ${CFLAGS} \
--- 17,23 ----
CLEANFILES= linux_assym.h linux_genassym.o
linux_assym.h: linux_genassym.o
! sh /usr/src/sys/kern/genassym.sh ${.ALLSRC} > ${.TARGET}
linux_locore.o: linux_locore.s linux_assym.h
${CC} -c -x assembler-with-cpp -DLOCORE ${CFLAGS} \
If you don't keep your srcs in /usr/src, you will have to modify the
fixes appropriately
I am sure that there is a much cleaner way of fixing this, but I will
leave it to the gurus to work that out. I think a similar fix to the
kernel Makefile would allow one to build a working kernel with
COMPAT_LINUX built in.
There may be other modules or pieces of the kernel which may be affected
by the new symbol generation facility. I have not been bitten by the
problem yet nor have I looked for them, so I can't speak first hand of
the issues.
Hope this helps.
Regards, George Dinolt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
