Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jan 2014 19:43:29 +0100
From:      Hans Petter Selasky <hps@bitfrost.no>
To:        gljennjohn@gmail.com, Martin Alt <mnalt@gmx.de>
Cc:        freebsd-isdn@freebsd.org
Subject:   Re: Problems compiling and using isdn4bsd-kmod on FreeBSD 10.0-RELEASE
Message-ID:  <52E6A8D1.20503@bitfrost.no>
In-Reply-To: <20140127185152.4b13632f@ernst.home>
References:  <20140126163918.GA35814@zeus.home.anwaltskanzlei-alt.de> <20140127185152.4b13632f@ernst.home>

next in thread | previous in thread | raw e-mail | index | archive | help
On 01/27/14 18:51, Gary Jennejohn wrote:
> On Sun, 26 Jan 2014 17:39:18 +0100
> Martin Alt <mnalt@gmx.de> wrote:
>
>> I have been using the i4b kld module with FreeBSD9.1 and have now upgraded to
>> 10.0-RELEASE using freebsd-update.
>>
>> I have rebuilt the kernel module using the comms/isdn4bsd-kmod port (from
>> svn://svn.turbocat.net/i4b/trunk/ports/comms/isdn4bsd-kmod, rev 2974) and
>> installed them, but unfortunately I get the following error message when trying
>> to kldload i4b:
>>
>> kldload: can't load i4b: Exec format error
>>
>> Dmesg output is as follows:
>>
>> link_elf_obj: symbol ihfc_filter_info_start undefined
>> linker_load_file: Unsupported file type
>>
>
> This error is almost guaranteed to be caused by the kernel you're
> running having been generated from other (e.g. older) sources
> than the module.  The remedy is to make usre that the sources
> are the same for both the kernel and the module.

Hi,

It turns out I should use "sys/linker_set.h" instead of my own 
hand-rolled linker sets. I've updated the port and it should now load on 
FreeBSD-10 and FreeBSD-11.

Thanks to everyone using and supporting ISDN4BSD.

--HPS




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E6A8D1.20503>