From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Peica <peica@qq.com>
Subject: Re: cross build for OS lion
Date: Mon, 10 Oct 2011 20:48:00 -0000 [thread overview]
Message-ID: <201110102247.40823.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <A0F79F3C-11AF-4BE5-8368-300089035962@qq.com>
Peica, All,
On Thursday 06 October 2011 19:09:15 Peica wrote:
> I have make a patch for crosstool-NG cross building from OS Lion via
> MacPort GCC. If I use the default one, it could stop the building
> because the script set the Xcode gcc as C_HOST and it would make a
> internal compiler error when calling my target compiler.
The patch is almost unreadable. Please provide a unified patch:
diff -u
It also seems the patch is reversed.
Anyway, the patch seems really wrong. Setting the HOST and build prefix to
be the same breaks on canadian-crosses. With a canadian-cross toolchain,
the build machine is where the compiler is _built_, while the host machine
is where the compiler _runs_. And those two machines may be different.
Care to explain what breaks for you? For example, put your entire build.log
file on some website (or a pastebin) where we can get it to analyse the
issue.
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:[~2011-10-10 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 17:09 Peica
2011-10-10 20:48 ` Yann E. MORIN [this message]
2011-10-11 2:11 ` Peica
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=201110102247.40823.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=peica@qq.com \
/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).