On Fri, 18 Jan 2008, John Baldwin wrote: > > Can anyone explain what the underlying problem is? (I am guessing > > some ordering issue where normally elf64_obj is called first so the > > other is normally never called..) > > amd64 uses link_elf_obj.c, all the other archs use link_elf.c, hence > the duplication. link_elf.c is used to load kld's that are ELF > shared objects (i.e. foo.so) where as link_elf_obj.c is used to load > kld's that are ELF objects (i.e. foo.o). I think you are going to > get this everytime you do a kldload on amd64 because it will always > try link_elf.c first due to compile order (MI files are ordered in > the makefile before MD ones), emit the warning, and then try > link_elf_obj.c.
OK, that was my guess - the thing is that the last release I made didn't do this and I don't have any special options in the release or anything. I guess one option would be to put #ifdef amd64 around the error message in link_elf.c. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
signature.asc
Description: This is a digitally signed message part.
