This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 03.12.2012 13:04, Ralf Corsepius wrote:Well, ... I certainly not my choice of preference.On 12/03/2012 12:51 PM, Matthias Goldhoorn wrote:I'm using debian testing, but our institute is using also ubuntu LTS.I just tried to compile an gcc with the newlib for the microblaze-rtems target.
What is your host OS? I am providing toolchains from a variety of host OS, which can be found below ftp://ftp.rtems.org/pub/rtems/{linux,cygwin,mingw32,ming64}/4.11
No. Just the latest ones.I'm tiring to the the whole tool chain setup in our build chain (autoproj) running. that's why i would prefer to do the tool chain setup on my own.
Alternatively, try the RTEMS GCC/newlib patches from ftp://ftp.rtems.org/pub/rtems/SOURCES/4.11/
I currently triing the default setup of the newlib..., don't know about the patches. I'm new to rtems. Should i apply all patches of the given path, or only the latest one?
Are the gcc's/binutils/newlibs prepatched?No. These are vanilla source tarballs.
Maybe you can give me and short howto setup the tool chain hint/page...Building the toolchains isn't trivial. It's a rolling process which pretty frequently changes and comes with many tiny pitfalls.
The whole procedure is lurking inside of the rpm-specs. E.g. this file is what is being used to build the microblaze-toolchains: http://git.rtems.org/rtems-crossrpms.git/tree/rtems4.11/microblaze/rtems-4.11-microblaze-rtems4.11-gcc.spec
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |