From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stuart Anderson <sba@srl.caltech.edu>
Subject: Re: sk98lin driver in 2.5.47
Date: 13 Nov 2002 22:43:01 +0000 [thread overview]
Message-ID: <1037227381.11979.197.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <200211132231.18870.m.c.p@wolk-project.de>
On Wed, 2002-11-13 at 21:31, Marc-Christian Petersen wrote:
> Hi Stuart,
>
> > I have been unable to compile the SysKonnect sk98lin GigE driver
> > under linux-2.5.x. Is there a patch for the following linker
> > problem of built-in.o? The following is from 2.5.47-ac2.
> > drivers/built-in.o: In function `SkPnmiInit':
> > drivers/built-in.o(.text+0x3a346): undefined reference to `__udivdi3'
> > drivers/built-in.o: In function `SkPnmiEvent':
> > drivers/built-in.o(.text+0x3ae97): undefined reference to `__udivdi3'
> > drivers/built-in.o: In function `SensorStat':
> > drivers/built-in.o(.text+0x3c0fd): undefined reference to `__udivdi3'
> > drivers/built-in.o(.text+0x3c16d): undefined reference to `__udivdi3'
> > drivers/built-in.o: In function `General':
> > drivers/built-in.o(.text+0x3de99): undefined reference to `__udivdi3'
> I have the same problems with any patch|driver in any kernel (2.4 and 2.5).
> I've talked to a technician at SysKonnect and he told me that my linker is
> broken and he also mentioned that Debian is known to have a broken linker (I
> cannot confirm this in any way!)
Its a bug in their driver.
next prev parent reply other threads:[~2002-11-13 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 21:31 Marc-Christian Petersen
2002-11-13 22:43 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 19:12 Stuart Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1037227381.11979.197.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=sba@srl.caltech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®