public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Wallance Lee" <halyx@126.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] What do you recommend to build cross-compiling toolchain?
Date: Sun, 11 Oct 2015 18:42:44 +0800 (CST)	[thread overview]
Message-ID: <2088852b.55a6.150567ed64c.Coremail.halyx@126.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 544 bytes --]

Hi, every one!
I am going to build a cross-compiling toolchain using  crossdev like following:
    #crossdev -t arm-unknown-linux-gnueabi -S
but everytime I got this error on building gcc-stage1:
"cannot compute suffix of object files" just during building libgcc
What can I avoid this error?
I like gentoo's emerge-arm-*  to build things on arm platform.
What do you recommend to build cross-compiling toolchain?
I can see a similar problem gentoo fourm: https://forums.gentoo.org/viewtopic-t-831862-start-0.html
Any suggestions will be help.

[-- Attachment #2: Type: text/html, Size: 886 bytes --]

                 reply	other threads:[~2015-10-11 10:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2088852b.55a6.150567ed64c.Coremail.halyx@126.com \
    --to=halyx@126.com \
    --cc=gentoo-user@lists.gentoo.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