Re: [ptxdist] Not reproducable bugs on compiling OSELAS Toolchain

2012-02-26 Thread Bernhard Walle
Hi,

* Andreas Bießmann andr...@biessmann.de [2012-02-25 09:21]:
 
 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.

flex and bison can be used from Apple (at least I have /usr/bin/flex and
/usr/bin/bison in my $PATH). You also need 'md5sum' (macports has the
'md5sha1sum' package). And also GNU ar because of the 'f' option, but I
want to check if it's really needed before sending a patch to check for
GNU ar.

 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.

I'm not sure if the ncurses from Apple is sufficient, but at least
/usr/lib/libncuses.dylib is there. Apart from building kconfig, ptxdist
uses its own host-ncurses, though.

 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.

I would have called it 'playground'. :) I just checked that it builds
with ptxdist-2012.02 without any additional patches.

The only remaining patch that is in the queue of Michael is the
localedef stuff. If you need it now, you can take it from
https://bitbucket.org/bwalle/localedef/overview (darwin-fixes branch)
or as patch from
https://bitbucket.org/bwalle/ptxdist-vetero/src/770a9a83af73/patches/localedef-eglibc-2.11.90-ptx1.

Please note that the ptxdist-vetero project doesn't build currently on
Mac OS because of the mtd tools. I need to fix that when I have time.
('ptxdist go' works but 'ptxdist images' will fail.)



Regards,
Bernhard

-- 
ptxdist mailing list
ptxdist@pengutronix.de


Re: [ptxdist] Not reproducable bugs on compiling OSELAS Toolchain

2012-02-24 Thread Martin Breidung
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.

Thank you!

Martin



Am 23.02.2012 um 14:43 schrieb Andreas Bießmann:

 Hi Martin,
 
 On 23.02.2012 13:39, Martin Breidung wrote:
 I got errors on compiling the toolchain OSELAS.Toolchain-2011.11.1.
 
 System: Ubuntu 11.10
 
 On Ubuntu 10.4 LTS i got errors too withe OSELAS.Toolchain-2011.11.0.
 
 Ubuntu is running under VMware Fusion on a MacBookPro i7 Early 2011.
 
 so why don't use your host system if you already run OS X?
 
 Which OS is recommended for compiling the toolchain or what can I do to
 make it work?
 
 Lion as host with OSELAS.Toolchain-2011.11.1 works for me with
 arm-v4t-linux-gnueabi, arm-v5te-linux-gnueabi and
 arm-cortexa8-linux-gnueabi.
 It would be great to have more testers for ptxdist stuff on OS X host.
 So if you do not insist on Linux host feel free to try it.
 But keep in mind: OS X support is something alpha, not all functions
 tested on Linux host already tested on OS X host and there may be some
 issues.
 
 regards
 
 Andreas Bießmann
 
 -- 
 ptxdist mailing list
 ptxdist@pengutronix.de


-- 
ptxdist mailing list
ptxdist@pengutronix.de


Re: [ptxdist] Not reproducable bugs on compiling OSELAS Toolchain

2012-02-23 Thread Alexander Dahl
Hei Martin, 

Am 2012-02-23 13:39, schrieb Martin Breidung:
 I got errors on compiling the toolchain OSELAS.Toolchain-2011.11.1.
 
 System: Ubuntu 11.10

Which architecture? `uname -m`?

 On Ubuntu 10.4 LTS i got errors too withe OSELAS.Toolchain-2011.11.0.

Same question, i686, x86_64, … ??

 Which OS is recommended for compiling the toolchain or what can I do
 to make it work?

I have compiled OSELAS Toolchain 2011.03.[01] and 2011.11.[01] on all
Ubuntu Releases since 10.04 both under i686 and x86_64 and had no single
problem. How do you build the toolchains, so what are the commands you
invoke? Did you set some special environment variables before?

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de