Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] problem generating c++ compiler for target arch
Date: Wed, 22 Nov 2006 21:02:13 +0100	[thread overview]
Message-ID: <20061122200213.GB1863@aon.at> (raw)
In-Reply-To: <33335.80.176.236.13.1164224678.squirrel@mail.primefarm.co.uk>

On Wed, Nov 22, 2006 at 07:44:38PM -0000, lists at primefarm.co.uk wrote:
>On Wed, November 22, 2006 6:52 pm, Bernhard Fischer wrote:

>OK, I tried again with 3.4.6, those errors do indeed go away. I now have a
>differnt set of problems (hooray!).
>
>The error seems to center around fakeroot, although I'm no expert at
>reading these error dumps.
>
>Here is the whole lot:
>
>CONFIG_FILES= CONFIG_HEADERS= /bin/sh ./config.status
>config.status: executing depfiles commands
>config.status: executing libtool commands
>/bin/sh ./libtool --tag=CC --mode=link gcc  -g -O2   -o faked  faked.o
>libcommunicate.la -ldl
>libtool: link: gcc -g -O2 -o faked faked.o  ./.libs/libcommunicate.a -ldl
>/usr/lib/libc_nonshared.a(elf-init.oS)(.gnu.linkonce.t.__i686.get_pc_thunk.bx+0x0):
>In function `__i686.get_pc_thunk.bx':
>: multiple definition of `__i686.get_pc_thunk.bx'

>
>Any ideas?

Not sure, but it sounds like your host's toolchain is too old.
binutils-2.16.1 work for me..

  reply	other threads:[~2006-11-22 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 19:44 [Buildroot] problem generating c++ compiler for target arch lists at primefarm.co.uk
2006-11-22 20:02 ` Bernhard Fischer [this message]
2006-11-22 20:09   ` lists at primefarm.co.uk
2006-11-22 20:18     ` Bernhard Fischer
2006-11-22 20:21       ` lists at primefarm.co.uk
2006-11-29 17:45         ` MikeW
2006-11-29 17:52           ` David Prime
  -- strict thread matches above, loose matches on Subject: below --
2006-11-22 18:06 lists at primefarm.co.uk
2006-11-22 18:52 ` Bernhard Fischer

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=20061122200213.GB1863@aon.at \
    --to=rep.nop@aon.at \
    --cc=buildroot@busybox.net \
    /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