From: Josh Kugelmann <joshk@y7mail.com>
To: crossgcc@sourceware.org
Subject: Re: [CT-NG] Static linking impossible on the host system 'x86_64-build_apple-darwin11.2.0'
Date: Fri, 06 Jan 2012 08:31:00 -0000 [thread overview]
Message-ID: <AD13FC1C-B51E-4E85-BC70-885D7DC91907@y7mail.com> (raw)
In-Reply-To: <7FA70F73-116A-4767-9438-08A74AEB122D@v9g.de>
Ah, that works. I had to manually set it in .config though, since selecting that option through menuconfig didn't work for some reason (It remained deselected after pressing Y).
On 06/01/2012, at 7:01 PM, Titus von Boxberg wrote:
> Am 06.01.2012 um 04:54 schrieb Josh Kugelmann:
>> Hi all,
>> I'm building a cross toolchain for the RS Media using crosstool-NG 1.13.2 on Mac OS X 10.7 (Lion). I followed the instructions under "Using crosstool-NG on MacOS-X" (docs/C - Misc. tutorials.txt), however when I try to build the toolchain I get the following error:
>>
>> [INFO ] Performing some trivial sanity checks
>> [INFO ] Build started 20120106.145119
>> [INFO ] Building environment variables
>> [ERROR] Static linking impossible on the host system 'x86_64-build_apple-darwin11.2.0'
>>
>> Is there a way to get around this?
>
> Josh,
>
> in the menuconfig you should not select
> "Build Static Toolchain (EXPERIMENTAL)" in the "Toolchain Options" menu.
> This should make sure that CT_WANTS_STATIC_LINK=y is *not* used in your .config
> which is what you want on OSX.
>
> Regards
> Titus
>
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-01-06 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 3:55 Josh Kugelmann
2012-01-06 8:01 ` Titus von Boxberg
2012-01-06 8:31 ` Josh Kugelmann [this message]
2012-01-06 10:16 ` Josh Kugelmann
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=AD13FC1C-B51E-4E85-BC70-885D7DC91907@y7mail.com \
--to=joshk@y7mail.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).