On Friday 18 January 2008 12:57:54 am Peter Jeremy wrote:
> On Fri, Jan 18, 2008 at 08:17:40AM +1030, Daniel O'Connor wrote:
> >On Fri, 18 Jan 2008, John Baldwin wrote:
> >> amd64 uses link_elf_obj.c, all the other archs use link_elf.c, hence
> >> the duplication.
>
> Then why does amd64 need link
On Fri, 18 Jan 2008, Peter Jeremy wrote:
> On Fri, Jan 18, 2008 at 08:17:40AM +1030, Daniel O'Connor wrote:
> >On Fri, 18 Jan 2008, John Baldwin wrote:
> >> amd64 uses link_elf_obj.c, all the other archs use link_elf.c,
> >> hence the duplication.
>
> Then why does amd64 need link_elf.c at all?
I
On Fri, Jan 18, 2008 at 08:17:40AM +1030, Daniel O'Connor wrote:
>On Fri, 18 Jan 2008, John Baldwin wrote:
>> amd64 uses link_elf_obj.c, all the other archs use link_elf.c, hence
>> the duplication.
Then why does amd64 need link_elf.c at all?
>I guess one option would be to put #ifdef amd64 aroun
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
On Wednesday 16 January 2008 10:40:25 pm Daniel O'Connor wrote:
> Hi,
> I have built my own release of 6.3 (slightly older than 6.3 as tagged)
> and I am seeing an odd cosmetic problem. Whenever I kldload a module
> (stuff loaded by the loader doesn't do it) I get this in dmesg..
> kldload: Unsup
Hi,
I have built my own release of 6.3 (slightly older than 6.3 as tagged)
and I am seeing an odd cosmetic problem. Whenever I kldload a module
(stuff loaded by the loader doesn't do it) I get this in dmesg..
kldload: Unsupported file type
The actual module works fine though (shows up in kldstat
