Re: 5.3 Building Kernel/World
On 2005-01-17 14:30, Doug Poland [EMAIL PROTECTED] wrote: On Jan 17, 2005, at 11:07, Kris Kennaway wrote: cd /usr/src make cleandir make cleandir make buildworld Kris Interesting, what does make cleandir do? Is it different than running # cd /usr/obj # chflags -R noschg * # rm -rf * as documented in the handbook? The first 'cleandir' run is pretty much equivalent to the instructions in the Handbook. If there are stale objects or libraries under /usr/src, the second cleandir run cleans those too. Normally, there shouldn't be any stale objects under /usr/src, because the recommended buildworld/buildkernel cycle uses /usr/obj for that. If there are left-overs under /usr/src, they are usually the result of manual builds run in one of the subdirectories of /usr/src. - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Building Kernel/World
On Sun, Jan 16, 2005 at 11:32:31PM -0800, Doug Hardie wrote: The only way I can think for this to happen is if your source tree was inconsistent (i.e. not completely updated), or you updated your sources after you did the installworld, and the kernel depends on the newer version of config than the one you have built (in this case the 'safe' buildworld/buildkernel/installkernel method you used to begin with should still work). Kris Well, I tried makeworld again. Dies in Step 3. Reloaded all source from the distribution CD. makeworld dies in exactly the same place: Really, this all points to something else having changed on your system in the meantime. Try cd /usr/src make cleandir make cleandir make buildworld Kris Wish I had seen that earlier. I just tried a cvs from RELENG_5_3. I thought that would only have security fixes. Its downloading a ton of stuff. Obviously I can't stop it. Seems like just about all the userland source files are being changed. Lots of deletes too. I'll give the above a try when this finishes. Why so many files from cvs? The number of changes between RELENG_5_3_0_RELEASE and RELENG_5_3 is very small. If you're seeing lots of changes, it means that you didn't actually have a 5.3-RELEASE source tree installed before now, which explains the problems you were seeing in compiling it. Kris pgpHEFIceREyD.pgp Description: PGP signature
Re: 5.3 Building Kernel/World
On Jan 17, 2005, at 11:07, Kris Kennaway wrote: On Sun, Jan 16, 2005 at 11:32:31PM -0800, Doug Hardie wrote: The only way I can think for this to happen is if your source tree was inconsistent (i.e. not completely updated), or you updated your sources after you did the installworld, and the kernel depends on the newer version of config than the one you have built (in this case the 'safe' buildworld/buildkernel/installkernel method you used to begin with should still work). Kris Well, I tried makeworld again. Dies in Step 3. Reloaded all source from the distribution CD. makeworld dies in exactly the same place: Really, this all points to something else having changed on your system in the meantime. Try cd /usr/src make cleandir make cleandir make buildworld Kris Wish I had seen that earlier. I just tried a cvs from RELENG_5_3. I thought that would only have security fixes. Its downloading a ton of stuff. Obviously I can't stop it. Seems like just about all the userland source files are being changed. Lots of deletes too. I'll give the above a try when this finishes. Why so many files from cvs? The number of changes between RELENG_5_3_0_RELEASE and RELENG_5_3 is very small. If you're seeing lots of changes, it means that you didn't actually have a 5.3-RELEASE source tree installed before now, which explains the problems you were seeing in compiling it. Kris Thats interesting. I was using the 5.3 release CD. The checksums match those listed. It was installed onto a re-formatted drive as I wanted the UFS-2. The source was installed as part of the original installation. Anyway, either the cvsup or the cleandirs worked. I was able to buildworld and a new kernel. Installation of both appears to have gone correctly. uname gives the new kernel and strings of /boot/kernel/kernel also shows the new name. uname before said 5.3-RELEASE. It would appear that when I build the production systems I will immediately after instalation cvsup to RELENG_5_3 and then run make cleandir before anything else. Fortunately right now I am playing with test systems. It it at all possible to not have to buildworld when building a new kernel? For example, I was trying to add option atapicam. It would seem that buildworld would not be necessary in that situation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Building Kernel/World
On Jan 17, 2005, at 11:07, Kris Kennaway wrote: cd /usr/src make cleandir make cleandir make buildworld Kris Interesting, what does make cleandir do? Is it different than running # cd /usr/obj # chflags -R noschg * # rm -rf * as documented in the handbook? -- Regards, Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Building Kernel/World
Doug Hardie wrote: [ ... ] It it at all possible to not have to buildworld when building a new kernel? For example, I was trying to add option atapicam. It would seem that buildworld would not be necessary in that situation. Yes, if the kernel sources and the world sources are in sync with each other, *and* with the binaries which are installed, you can rebuild the kernel without changing or reinstalling the world. If you simply want to try compiling the kernel several times over using different options, that's fine. If you run cvsup and it changes /usr/src, and you do not know that those changes are not significant enough to make a difference, *that's* when you need to rebuild world as well. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Building Kernel/World
On Mon, Jan 17, 2005 at 12:25:55PM -0800, Doug Hardie wrote: The number of changes between RELENG_5_3_0_RELEASE and RELENG_5_3 is very small. If you're seeing lots of changes, it means that you didn't actually have a 5.3-RELEASE source tree installed before now, which explains the problems you were seeing in compiling it. Kris Thats interesting. I was using the 5.3 release CD. The checksums match those listed. It was installed onto a re-formatted drive as I wanted the UFS-2. The source was installed as part of the original installation. Anyway, either the cvsup or the cleandirs worked. I was able to buildworld and a new kernel. Installation of both appears to have gone correctly. uname gives the new kernel and strings of /boot/kernel/kernel also shows the new name. uname before said 5.3-RELEASE. It would appear that when I build the production systems I will immediately after instalation cvsup to RELENG_5_3 and then run make cleandir before anything else. Fortunately right now I am playing with test systems. It it at all possible to not have to buildworld when building a new kernel? For example, I was trying to add option atapicam. It would seem that buildworld would not be necessary in that situation. If you're modifying the kernel configuration and you have not updated your sources you can use the 'config' method to build your kernels. If you update your sources then you must use buildworld/buildkernel, or you will occasionally encounter errors. This is described in the handbook in greater detail. Kris pgpeE9YSSHLlb.pgp Description: PGP signature
5.3 Building Kernel/World
The instructions for building world/kernel for 4.x are straight forward and work fine. However, I seem to have munged two 5.3 installations now. I have been through all the UPDATING notes and the handbook and something is obviously not clear. The approach I used is: Clean install from 5.3 distribution. make buildworld create new config file LAFN make buildkernel KERNCONF=LAFN make installkernel KERNCONF=LAFN reboot make installworld reboot At that point It appeared I was using the LAFN kernel rather than generic. However, tonight I tried to make a new kernel. NO go: ERROR: version of config(8) does not match kernel! config version = 500012, version required = 500013 So I tried to reinstall the kernel: make installkernel KERNCONF=LAFN install -o root -g wheel -m 555 acpi.ko /boot/kernel install: acpi.ko: No such file or directory How are you supposed to build a new kernel that works? How do I recover this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Building Kernel/World
On Sun, Jan 16, 2005 at 09:51:13PM -0800, Doug Hardie wrote: The instructions for building world/kernel for 4.x are straight forward and work fine. However, I seem to have munged two 5.3 installations now. I have been through all the UPDATING notes and the handbook and something is obviously not clear. The approach I used is: Clean install from 5.3 distribution. make buildworld create new config file LAFN make buildkernel KERNCONF=LAFN make installkernel KERNCONF=LAFN reboot make installworld reboot At that point It appeared I was using the LAFN kernel rather than generic. However, tonight I tried to make a new kernel. NO go: ERROR: version of config(8) does not match kernel! config version = 500012, version required = 500013 So I tried to reinstall the kernel: make installkernel KERNCONF=LAFN install -o root -g wheel -m 555 acpi.ko /boot/kernel install: acpi.ko: No such file or directory How are you supposed to build a new kernel that works? How do I recover this? The only way I can think for this to happen is if your source tree was inconsistent (i.e. not completely updated), or you updated your sources after you did the installworld, and the kernel depends on the newer version of config than the one you have built (in this case the 'safe' buildworld/buildkernel/installkernel method you used to begin with should still work). Kris pgpKrBQHaxFwq.pgp Description: PGP signature
Re: 5.3 Building Kernel/World
On Jan 16, 2005, at 22:05, Kris Kennaway wrote: On Sun, Jan 16, 2005 at 09:51:13PM -0800, Doug Hardie wrote: The instructions for building world/kernel for 4.x are straight forward and work fine. However, I seem to have munged two 5.3 installations now. I have been through all the UPDATING notes and the handbook and something is obviously not clear. The approach I used is: Clean install from 5.3 distribution. make buildworld create new config file LAFN make buildkernel KERNCONF=LAFN make installkernel KERNCONF=LAFN reboot make installworld reboot At that point It appeared I was using the LAFN kernel rather than generic. However, tonight I tried to make a new kernel. NO go: ERROR: version of config(8) does not match kernel! config version = 500012, version required = 500013 So I tried to reinstall the kernel: make installkernel KERNCONF=LAFN install -o root -g wheel -m 555 acpi.ko /boot/kernel install: acpi.ko: No such file or directory How are you supposed to build a new kernel that works? How do I recover this? The only way I can think for this to happen is if your source tree was inconsistent (i.e. not completely updated), or you updated your sources after you did the installworld, and the kernel depends on the newer version of config than the one you have built (in this case the 'safe' buildworld/buildkernel/installkernel method you used to begin with should still work). Kris those instructions were typed just as noted with nothing inbetween. I have replaced kernel with kernel.old so the system will boot. But now I have an old kernel and new world (possibly). Nothing for reconstruction seems to work. buildkernel continues to give the above error. I guess I'll try a buildworld again tomorrow. Don't know what else to do. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 Building Kernel/World
On Jan 16, 2005, at 22:05, Kris Kennaway wrote: On Sun, Jan 16, 2005 at 09:51:13PM -0800, Doug Hardie wrote: The instructions for building world/kernel for 4.x are straight forward and work fine. However, I seem to have munged two 5.3 installations now. I have been through all the UPDATING notes and the handbook and something is obviously not clear. The approach I used is: Clean install from 5.3 distribution. make buildworld create new config file LAFN make buildkernel KERNCONF=LAFN make installkernel KERNCONF=LAFN reboot make installworld reboot At that point It appeared I was using the LAFN kernel rather than generic. However, tonight I tried to make a new kernel. NO go: ERROR: version of config(8) does not match kernel! config version = 500012, version required = 500013 So I tried to reinstall the kernel: make installkernel KERNCONF=LAFN install -o root -g wheel -m 555 acpi.ko /boot/kernel install: acpi.ko: No such file or directory How are you supposed to build a new kernel that works? How do I recover this? The only way I can think for this to happen is if your source tree was inconsistent (i.e. not completely updated), or you updated your sources after you did the installworld, and the kernel depends on the newer version of config than the one you have built (in this case the 'safe' buildworld/buildkernel/installkernel method you used to begin with should still work). Kris Well, I tried makeworld again. Dies in Step 3. Reloaded all source from the distribution CD. makeworld dies in exactly the same place: === gnu/usr.bin/binutils/libbfd cc -O -pipe -I. -I/usr/src/gnu/usr.bin/binutils/libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/libbfd -I/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/binutils/libbfd/../libbfd -I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/ include -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd -DSELECT_ARCHITECTURES= bfd_i386_arch -DHAVE_bfd_elf32_i386_freebsd_vec -DHAVE_bfd_elf32_i386_vec -DSELECT_VECS= bfd_elf32_i386_freebsd_vec ,bfd_elf32_i386_vec -DDEFAULT_VECTOR=bfd_elf32_i386_freebsd_vec -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ cpu-i386.c In file included from /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ cpu-i386.c:23: /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:114: error: syntax error before _bfd_add_bfd_to_archive_cache /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:115: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:116: error: syntax error before _bfd_generic_mkarchive /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:117: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:120: error: syntax error before bfd_slurp_armap /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:121: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:122: error: syntax error before bfd_slurp_bsd_armap_f2 /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:123: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:126: error: syntax error before _bfd_slurp_extended_name_table /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:127: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:128: error: syntax error before _bfd_construct_extended_name_table /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:129: error: syntax error before bfd_boolean /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:129: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:130: error: syntax error before _bfd_write_archive_contents /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:131: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:132: error: syntax error before _bfd_compute_and_write_armap /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:133: warning: data definition has no type or storage class /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/ libbfd.h:143: error: syntax error before bfd_false /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/
Re: 5.3 Building Kernel/World
On Sun, Jan 16, 2005 at 11:15:23PM -0800, Doug Hardie wrote: On Jan 16, 2005, at 22:05, Kris Kennaway wrote: On Sun, Jan 16, 2005 at 09:51:13PM -0800, Doug Hardie wrote: The instructions for building world/kernel for 4.x are straight forward and work fine. However, I seem to have munged two 5.3 installations now. I have been through all the UPDATING notes and the handbook and something is obviously not clear. The approach I used is: Clean install from 5.3 distribution. make buildworld create new config file LAFN make buildkernel KERNCONF=LAFN make installkernel KERNCONF=LAFN reboot make installworld reboot At that point It appeared I was using the LAFN kernel rather than generic. However, tonight I tried to make a new kernel. NO go: ERROR: version of config(8) does not match kernel! config version = 500012, version required = 500013 So I tried to reinstall the kernel: make installkernel KERNCONF=LAFN install -o root -g wheel -m 555 acpi.ko /boot/kernel install: acpi.ko: No such file or directory How are you supposed to build a new kernel that works? How do I recover this? The only way I can think for this to happen is if your source tree was inconsistent (i.e. not completely updated), or you updated your sources after you did the installworld, and the kernel depends on the newer version of config than the one you have built (in this case the 'safe' buildworld/buildkernel/installkernel method you used to begin with should still work). Kris Well, I tried makeworld again. Dies in Step 3. Reloaded all source from the distribution CD. makeworld dies in exactly the same place: Really, this all points to something else having changed on your system in the meantime. Try cd /usr/src make cleandir make cleandir make buildworld Kris pgpHBQtiiu7ua.pgp Description: PGP signature
Re: 5.3 Building Kernel/World
On Jan 16, 2005, at 23:19, Kris Kennaway wrote: On Sun, Jan 16, 2005 at 11:15:23PM -0800, Doug Hardie wrote: On Jan 16, 2005, at 22:05, Kris Kennaway wrote: On Sun, Jan 16, 2005 at 09:51:13PM -0800, Doug Hardie wrote: The instructions for building world/kernel for 4.x are straight forward and work fine. However, I seem to have munged two 5.3 installations now. I have been through all the UPDATING notes and the handbook and something is obviously not clear. The approach I used is: Clean install from 5.3 distribution. make buildworld create new config file LAFN make buildkernel KERNCONF=LAFN make installkernel KERNCONF=LAFN reboot make installworld reboot At that point It appeared I was using the LAFN kernel rather than generic. However, tonight I tried to make a new kernel. NO go: ERROR: version of config(8) does not match kernel! config version = 500012, version required = 500013 So I tried to reinstall the kernel: make installkernel KERNCONF=LAFN install -o root -g wheel -m 555 acpi.ko /boot/kernel install: acpi.ko: No such file or directory How are you supposed to build a new kernel that works? How do I recover this? The only way I can think for this to happen is if your source tree was inconsistent (i.e. not completely updated), or you updated your sources after you did the installworld, and the kernel depends on the newer version of config than the one you have built (in this case the 'safe' buildworld/buildkernel/installkernel method you used to begin with should still work). Kris Well, I tried makeworld again. Dies in Step 3. Reloaded all source from the distribution CD. makeworld dies in exactly the same place: Really, this all points to something else having changed on your system in the meantime. Try cd /usr/src make cleandir make cleandir make buildworld Kris Wish I had seen that earlier. I just tried a cvs from RELENG_5_3. I thought that would only have security fixes. Its downloading a ton of stuff. Obviously I can't stop it. Seems like just about all the userland source files are being changed. Lots of deletes too. I'll give the above a try when this finishes. Why so many files from cvs? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 building kernel
hi everybody. I have some troble building kernel on 5.3, I get some error messages about psm.o . . output (tail -n10) and error messages are attached, kernel config too.. pleaz help. ../aicasm/aicasm: 880 instructions used ../aicasm/aicasm: 826 instructions used atkbd.o(.text+0x16f): In function `atkbd_configure': : undefined reference to `atkbdc_configure' atkbd.o(.text+0x251): In function `atkbd_probe': : undefined reference to `atkbdc_open' atkbd.o(.text+0x43d): In function `atkbd_init': : undefined reference to `atkbdc_open' atkbd.o(.text+0x685): In function `atkbd_test_if': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x692): In function `atkbd_test_if': : undefined reference to `test_controller' atkbd.o(.text+0x6aa): In function `atkbd_test_if': : undefined reference to `test_kbd_port' atkbd.o(.text+0x6fb): In function `atkbd_read': : undefined reference to `read_kbd_data' atkbd.o(.text+0x70a): In function `atkbd_read': : undefined reference to `read_kbd_data_no_wait' atkbd.o(.text+0x743): In function `atkbd_check': : undefined reference to `kbdc_data_ready' atkbd.o(.text+0x793): In function `atkbd_read_char': : undefined reference to `read_kbd_data' atkbd.o(.text+0x7a7): In function `atkbd_read_char': : undefined reference to `read_kbd_data_no_wait' atkbd.o(.text+0xb94): In function `atkbd_check_char': : undefined reference to `kbdc_data_ready' atkbd.o(.text+0xe2b): In function `atkbd_lock': : undefined reference to `kbdc_lock' atkbd.o(.text+0xfc0): In function `setup_kbd_port': : undefined reference to `set_controller_command_byte' atkbd.o(.text+0xff8): In function `get_kbd_echo': : undefined reference to `write_kbd_command' atkbd.o(.text+0xffe): In function `get_kbd_echo': : undefined reference to `read_kbd_data' atkbd.o(.text+0x1010): In function `get_kbd_echo': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x1016): In function `get_kbd_echo': : undefined reference to `test_controller' atkbd.o(.text+0x101c): In function `get_kbd_echo': : undefined reference to `test_kbd_port' atkbd.o(.text+0x1055): In function `probe_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x106c): In function `probe_keyboard': : undefined reference to `write_controller_command' atkbd.o(.text+0x1074): In function `probe_keyboard': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x107a): In function `probe_keyboard': : undefined reference to `kbdc_get_device_mask' atkbd.o(.text+0x1085): In function `probe_keyboard': : undefined reference to `get_controller_command_byte' atkbd.o(.text+0x1094): In function `probe_keyboard': : undefined reference to `kbdc_set_device_mask' atkbd.o(.text+0x109c): In function `probe_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x10aa): In function `probe_keyboard': : undefined reference to `test_controller' atkbd.o(.text+0x10b0): In function `probe_keyboard': : undefined reference to `test_kbd_port' atkbd.o(.text+0x10c4): In function `probe_keyboard': : undefined reference to `kbdc_set_device_mask' atkbd.o(.text+0x10d9): In function `probe_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x10ff): In function `init_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x111a): In function `init_keyboard': : undefined reference to `write_controller_command' atkbd.o(.text+0x1125): In function `init_keyboard': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x112b): In function `init_keyboard': : undefined reference to `get_controller_command_byte' atkbd.o(.text+0x113d): In function `init_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x118f): In function `init_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x1224): In function `init_keyboard': : undefined reference to `reset_kbd' atkbd.o(.text+0x1233): In function `init_keyboard': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x1239): In function `init_keyboard': : undefined reference to `test_controller' atkbd.o(.text+0x123f): In function `init_keyboard': : undefined reference to `test_kbd_port' atkbd.o(.text+0x124b): In function `init_keyboard': : undefined reference to `set_controller_command_byte' atkbd.o(.text+0x1253): In function `init_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x128b): In function `init_keyboard': : undefined reference to `send_kbd_command_and_data' atkbd.o(.text+0x12a6): In function `init_keyboard': : undefined reference to `set_controller_command_byte' atkbd.o(.text+0x12ae): In function `init_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x12d1): In function `init_keyboard': : undefined reference to `set_controller_command_byte' atkbd.o(.text+0x12e4): In function `init_keyboard': : undefined reference to `set_controller_command_byte' atkbd.o(.text+0x12ec): In function `init_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x1308): In function `init_keyboard': : undefined reference to `kbdc_lock' atkbd.o(.text+0x1327): In
5.3 building kernel
another error. when I disable psm device in configuration I get another error: atkbd.o(.text+0x137c): In function `get_kbd_id': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x1387): In function `get_kbd_id': : undefined reference to `send_kbd_command' atkbd.o(.text+0x13a6): In function `get_kbd_id': : undefined reference to `read_kbd_data' atkbd.o(.text+0x13b6): In function `get_kbd_id': : undefined reference to `read_kbd_data' atkbd.o(.text+0x13c6): In function `get_kbd_id': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x13cc): In function `get_kbd_id': : undefined reference to `test_controller' atkbd.o(.text+0x13d2): In function `get_kbd_id': : undefined reference to `test_kbd_port' *** Error code 1 Stop in /usr/obj/usr/src/sys/FJ_S6120. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 building kernel
dusan wrote: hi everybody. I have some troble building kernel on 5.3, I get some error messages about psm.o . . output (tail -n10) and error messages are attached, kernel config too.. pleaz help. I don't see device atkbdc in your kernel config, but this is required by psm (and also by atkbd) atkbd.o(.text+0x16f): In function `atkbd_configure': : undefined reference to `atkbdc_configure' snip -- Toomas Aas |arvutivõrgu peaspetsialist | head specialist on computer networks| |Tartu Linnakantselei | Tartu City Office | - +372 736 1274 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 building kernel
You are missing # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller As already replied to you yet you seem to have reposted the error. If you are unsure on how kernels are built use GENERIC and hash out what you dont need instead of emptying unwanted stuff which maybe required by you in the future. Its a safer practice cuz the options are right there whether you use them or not. You have gotten into a fine mess this way * dusan ([EMAIL PROTECTED]) wrote: another error. when I disable psm device in configuration I get another error: atkbd.o(.text+0x137c): In function `get_kbd_id': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x1387): In function `get_kbd_id': : undefined reference to `send_kbd_command' atkbd.o(.text+0x13a6): In function `get_kbd_id': : undefined reference to `read_kbd_data' atkbd.o(.text+0x13b6): In function `get_kbd_id': : undefined reference to `read_kbd_data' atkbd.o(.text+0x13c6): In function `get_kbd_id': : undefined reference to `empty_both_buffers' atkbd.o(.text+0x13cc): In function `get_kbd_id': : undefined reference to `test_controller' atkbd.o(.text+0x13d2): In function `get_kbd_id': : undefined reference to `test_kbd_port' *** Error code 1 Stop in /usr/obj/usr/src/sys/FJ_S6120. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] +--==/\/\==--+ (__) FreeBSD | [EMAIL PROTECTED] |\\\'',) The |Kernel ESCAFLOWNE | \/ \ ^Power | Web http://unixdaemon.org | .\._/_)To +--==\/\/==--+ Serve [ We've switched the bath sponge with a tribble. ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
