From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Cc: "Derick Swanepoel" <dswanepoel@gmail.com>
Subject: Re: [gentoo-embedded] binutils-config-1.9-r1 causes armeb-softfloat-linux-uclibc to miscompile packages
Date: Thu, 14 Sep 2006 11:39:29 -0400 [thread overview]
Message-ID: <200609141139.30793.vapier@gentoo.org> (raw)
In-Reply-To: <fdcd80670609140756q63dbc04g64c05e14ac6855af@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
On Thursday 14 September 2006 10:56, Derick Swanepoel wrote:
> I finally got my armeb-softfloat-linux-uclibc toolchain to compile
> busybox, etc. without the dreaded "can't resolve symbol '__udivsi3'"
> problems, but only with binutils-config-1.8-r7. Now that cross
> compiling forces at least binutils-config-1.9-r1, my toolchain once
> again produces broken binaries.
are you using gcc-4.1 ?
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2006-09-14 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 14:56 [gentoo-embedded] binutils-config-1.9-r1 causes armeb-softfloat-linux-uclibc to miscompile packages Derick Swanepoel
2006-09-14 15:39 ` Mike Frysinger [this message]
2006-09-18 8:20 ` Derick Swanepoel
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=200609141139.30793.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=dswanepoel@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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