public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Ben Peters <powderskier@gmail.com>
To: Titus von Boxberg <titus@v9g.de>
Cc: crossgcc@sourceware.org
Subject: Re: Problem building ARM Linux cross toolchain on OS X
Date: Thu, 17 Nov 2011 15:19:00 -0000	[thread overview]
Message-ID: <CAPigshCscn5Y5XWKq-ELJcHHAHi_+7cjtyMeMnPLoeqa8d2Z1g@mail.gmail.com> (raw)
In-Reply-To: <10DDAD99-62D1-42FE-BA2E-89940E8990CC@v9g.de>

Sorry, here are all the version numbers:
OS X 10.6.8
XCode 3.2.6
CT-ng 1.9.3

For the configuration I used ./ct-ng menuconfig and set the options
mostly as specified at:
http://homepage.mac.com/macg3/TS7390-OSX-crosstool-instructions.txt.
I'm using newer versions of the libraries though:

binutils 2.20.1
gcc 4.3.5
glibc 2.9

For the host triplet, it's arm-unknown-linux-gnu. The machine I'm
attempting to build to is a Technologic Systems TS7500, which has a
250 mhz Cavium ARM9 CPU (Faraday 526). I specified the architecture
level as armv4 in the menuconfig, based on what uname -a gives me on
the ARM board.

On Thu, Nov 17, 2011 at 00:09, Titus von Boxberg <titus@v9g.de> wrote:
> Am 17.11.2011 um 01:24 schrieb Ben Peters:
>> Hi all,
>> I'm attempting to build a cross toolchain for a Debian embedded ARM
>> chip on OS X. I've tried several configurations, and gotten close, but
>
>
> please be more specific:
> - what is your osx version
> - what is your xcode version
> - what version of ct-ng are you using
> - specify the cmd line for ct-ng configuration
> - what is your intended host triple
>
> regards
> titus
>
>

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-11-17 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  0:25 Ben Peters
2011-11-17  7:10 ` Titus von Boxberg
2011-11-17 15:19   ` Ben Peters [this message]
2011-11-18 11:28     ` Titus von Boxberg

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=CAPigshCscn5Y5XWKq-ELJcHHAHi_+7cjtyMeMnPLoeqa8d2Z1g@mail.gmail.com \
    --to=powderskier@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=titus@v9g.de \
    /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).