From: Michael Eager <eager@eagercon.com>
To: crossgcc@sourceware.org
Subject: Problems running CT-NG
Date: Sat, 31 Mar 2012 18:52:00 -0000 [thread overview]
Message-ID: <4F77526B.1080908@eagercon.com> (raw)
I've been having problems using the repository version
of crosstools-ng, so I downloaded the latest release,
crosstools-ng-1.14.1. I'm having similar problems.
I've tried to build the samples armeb-unknown-linux-uclibcgnueabi
and armeb-unknown-linux-gnueabi. I made two small changes to the
config: point to a tarball directory and eliminate building debugging
tools.
I get the same build failure that I'm seeing with the repo version.
[ALL ] /usr/bin/ld: cannot find -lstdc++
...
[ERROR] >> Build failed in step 'Installing static core C compiler'
This is clearly the result of the link being done with this option:
-Wl,-Bstatic,-lstdc++,-Bdynamic
Can someone tell me what, if anything, I'm doing incorrectly?
I expected that the samples would build, but that does not seem
to be the case.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2012-03-31 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 18:52 Michael Eager [this message]
2012-03-31 20:29 ` Yann E. MORIN
2012-03-31 21:24 ` Michael Eager
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=4F77526B.1080908@eagercon.com \
--to=eager@eagercon.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).