mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas@biessmann.de>
To: ptxdist@pengutronix.de
Cc: Martin Breidung <titus@complab.de>
Subject: Re: [ptxdist] Not reproducable bugs on compiling OSELAS Toolchain
Date: Sat, 25 Feb 2012 09:21:46 +0100	[thread overview]
Message-ID: <4F489A1A.7050100@biessmann.de> (raw)
In-Reply-To: <BFCF1901-D205-4269-8B7F-C27232726A75@complab.de>

Hi Martin,

On 24.02.12 19:51, Martin Breidung wrote:
> Hi Andreas,
> 
> hmm… sounds interesting. I did not know that it can be used under OS X.
> 
> But i have to install a lot of other stuff under Lion first, right?

> Where can i get the necessary informations on setting up Lion for PDXdist? I would try it under Lion in a VM to protect my running system.

sorry, there is no documentation yet. I will sum it up if I have some
time and provide it to ptxdist.

Here are some step by step instructions (written down from memory ...
may lack some important steps).

You will first require the X-Code application from 'App Store'. It comes
with OS X headers, llvm-gcc, binutils for your mac a.s.o.

Next you will need some GNU tools like coreutils [1], gawk [2], sed [3],
tar [4], flex [5] and bison/yacc [6]. Remaining requirements of ptxdist
should be sufficient by OS X delivered software.

That sounds hard, but you do not need to install that tools by hand. You
may know either fink [7] or macports [8], just install your favorite
distribution and use it to install mentioned tools.
I can tell you that I use fink and one of my colleagues uses macports.
So questions targeted ptxdist regarding one of these distributions may
get an answer on this list. Beside that both distributions are actively
developed, you will get support from their mailing lists regarding
installing the distribution a.s.o.

If you got the required tools you can start using ptxdist source to
build it for your host. There comes another requirement to mind while
writing this. You will need ncurses[9] for building the kconf tools in
ptxdist. Ptxdists configure will search the required tools and complain
about missing ones.

Next get OSELAS.Toolchain source, extract, select target, ptxdist
migrate and go to build your favorite toolchain. As mentioned before I
tested arm-v4t, arm-v5te and arm-cortexa8 (all linux-gnueabi) toolchains
here.

Another important step is to build a rootfs. Here are some more
stumbling blocks, cause some target tools will require specific host
tools which are not yet tested on OS X.
Bernhard Walle started a generic arm bsp [10] (targeted on beagle-board
and clones). He uses ptxdist with OS X too, therefore this is a good
place to go for OS X adoptions of ptxdist bsp.
Beside that get git [11], read this list and react on patches regarding
OS X.

best regards

Andreas Bießmann

[1] http://www.gnu.org/software/coreutils/
[2] http://www.gnu.org/software/gawk/
[3] http://www.gnu.org/software/sed/
[4] http://www.gnu.org/software/tar/
[5] http://www.gnu.org/software/flex/
[6] http://www.gnu.org/software/bison/
[7] http://finkproject.org/
[8] http://www.macports.org/
[9] http://www.gnu.org/software/ncurses/
[10] https://bitbucket.org/bwalle/ptxdist-arm-boards
[11] http://gitscm.org/

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-02-25  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 12:39 Martin Breidung
2012-02-23 13:01 ` Alexander Dahl
2012-02-24 18:48   ` Martin Breidung
2012-02-25  0:31   ` [ptxdist] [SOLVED] " Martin Breidung
2012-02-23 13:43 ` [ptxdist] " Andreas Bießmann
2012-02-24 18:51   ` Martin Breidung
2012-02-25  8:21     ` Andreas Bießmann [this message]
2012-02-26 17:55       ` Bernhard Walle

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=4F489A1A.7050100@biessmann.de \
    --to=andreas@biessmann.de \
    --cc=ptxdist@pengutronix.de \
    --cc=titus@complab.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