From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: l l <happyarch@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.21 and __udivid3
Date: Thu, 26 Apr 2007 17:32:39 +0200 [thread overview]
Message-ID: <1177601559.24664.3.camel@twins> (raw)
In-Reply-To: <768a59a70704260824s584bb20fs8d4554dcca2d4c27@mail.gmail.com>
On Fri, 2007-04-27 at 00:24 +0900, l l wrote:
> Hi,
>
> How to link libgcc.a with linux-2.6.21?
you don't, in kernel one is supposed to used do_div() for 64/32.
> LD .tmp_vmlinux1
> kernel/built-in.o: In function `timespec_add_ns':
> /usr/src/linux-2.6.21/kernel/timer.c:828: undefined reference to `__udivdi3'
> /usr/src/linux-2.6.21/kernel/timer.c:841: undefined reference to `__udivdi3'
> /usr/src/linux-2.6.21/kernel/timer.c:1311: undefined reference to `__udivdi3'
> make[1]: *** [.tmp_vmlinux1] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.6.21'
> make: *** [debian/stamp-build-kernel] Error 2
I'm not seeing any /s there about. Is this a pristine tree?
> cc -v
> Using built-in specs.
> Target: i686-pc-linux-gnu
> Configured with: ../gcc/configure --prefix=/usr --libexecdir=/usr/lib
> --enable-shared --enable-threads=posix --enable-__cxa_atexit
> --enable-clocale=gnu --enable-languages=c,c++,treelang
> --with-system-zlib --with-gmp --enable-mpfr
> --enable-libstdcxx-allocator=mt
> Thread model: posix
> gcc version 4.3.0 20070420 (experimental)
>
> TIA
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-04-26 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 15:24 linux-2.6.21 and __udivid3 l l
2007-04-26 15:32 ` Peter Zijlstra [this message]
2007-04-26 17:55 ` Adrian Bunk
2007-04-26 19:57 ` Stephen Hemminger
2007-04-27 0:30 ` l l
2007-04-27 0:56 ` l l
2007-04-27 9:11 ` Andrew Morton
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=1177601559.24664.3.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=happyarch@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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