From: Jolyon Wright <jolyon.wright@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>, <crossgcc@sourceware.org>
Subject: Re: mac build woes : homebrew+iconvdata=big trouble
Date: Thu, 10 Jan 2013 21:22:00 -0000 [thread overview]
Message-ID: <CD14E09E.710D%jolyon.wright@gmail.com> (raw)
In-Reply-To: <201301102216.35863.yann.morin.1998@free.fr>
Really appreciate your help with this; I can confirm that your suggestion
*does* resolve the iconvdata problem - my build is way past this point now.
I have put some coffee on in anticipation of the next challenge :-)
I don't know the author of that piece but my guess is he will spot your
post,
Thanks again,
jolyon
On 10/01/2013 21:16, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
>Jolyon, All,
>
>On Thursday 10 January 2013 Jolyon Wright wrote:
>> I have been trying to build an arm cross compiler toolchain to run on
>> the mac using homebrew. I have been using these notes as a starting
>> point : http://www.benmont.com
>
>There are very bad suggestions in this /tutorial/:
>
> - manually editing the .config file
> This is a Bad Thing (TM).
> The configuration of crosstoll-Ng is done by running one of the
> configurators:
> ct-ng menuconfig
> or:
> ct-ng nconfig
>
> Options are set in the .config file because they've been set in the
> menuconfig. Manually overrding them is wrong. The configuration must
> be fixed from menuconfig.
>
> - Static linking impossible on the host system [...]
> The solution is wrong.
>
> This error is because something in crostool-NG wants to do some
> static linking. This should be disabled, using the menuconfig.
> In this case, the option wanting the static link is:
> CT_CC_STATIC_LIBSTDCXX
> which is selected in:
> C compiler --->
> [*] Link libstdc++ statically into the gcc binary
>
> If you disable this option, then static linking is no longer
> needed, and this error will vanish. Also, the '-Bstatic' issue will
> also disapear.
>
> We now have better code and error messages in the repository for this
> problem. It will be available in the next release.
>
> - gdb's 'readchar: Got EOF' error:
> Do not edit the .config file manually. Use 'ct-ng menuconfig' to
>change
> the config options.
>
>If you know how to contact the author, then please forward him/her this
>mail, and tell him/her to ask for help on the mailing list. We're usually
>trying to answer issues as much as we can (but being a volunteer endeavour
>for me, it's on a time-permit basis; others can/will help, too).
>
>Regards,
>Yann E. MORIN.
>
>--
>.-----------------.--------------------.------------------.---------------
>-----.
>| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
>conspiracy: |
>| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___
> |
>| +33 223 225 172 `------------.-------: X AGAINST | \e/ There
>is no |
>| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v
>conspiracy. |
>'------------------------------^-------^------------------^---------------
>-----'
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-01-10 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 20:04 Jolyon Wright
2013-01-10 20:12 ` Yann E. MORIN
2013-01-10 21:16 ` Yann E. MORIN
2013-01-10 21:22 ` Jolyon Wright [this message]
2013-05-15 21:15 ` Nathan Plesnicher
2013-01-10 21:28 Rūdolfs Bundulis
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=CD14E09E.710D%jolyon.wright@gmail.com \
--to=jolyon.wright@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@free.fr \
/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).