mcore-elf was Re: GNU/Cross Tools RPMs available
Thu Dec 12 06:39:00 GMT 2002
Nick, I am cc'ing you because you are the mcore maintainer
and probably have something to say.
Brian LaPonsey wrote:
> I have been working on building gnu-cross tools for mcore-elf, but I don't
> have an effective way to distribute them. Our company web site isn't really
> set up for this kind of thing, and I've had trouble getting the tools posted
> there with the right filenames, without licensing restrictions, etc.
Sometimes being small has its advantages. :) Most of the time, it means
that you are fighting limited resource problems though.
> I see you have binutils and gdb for mcore-elf, but not an mcore-elf-gcc. I
> have written a build script that builds all the tools and runs the test
> suite on the FSF's "plain vanilla" gcc source tree, and I have found that
> gcc-3.0.4 has far fewer unexpected failures than gcc-3.2.1 for the mcore-elf
> target (147 vs. 241). In contrast, the test results for powerpc-eabi are
> something like 19 unexpected failures. The test suite is run with the
> simulator as a target.
I intend to start running the test suite on the installed tools as the
step. Are you running it in the build tree or on installed images?
Comments on possible solutions below.
> Would it be possible for OARcorp to distribute a pre-built gcc-3.0.4 for
> mcore-elf, or are you committed to only distributing the latest versions?
> It would be a real help to have a web site where people could get free mcore
> tools, but I don't really want to distribute an mcore-elf-gcc-3.2.1 if it
> has problems.
First, I am not doing this as a paid venture. So please color my
OAR would be happy to put them up but I do not think it is anyone's long
best interests to distribute old tools. From my GCC and RTEMS
I can tell you for a fact that no one likes to pay attention to bug
on older versions. Recently an effort was made on GCC to verify a lot
older bug reports and close them if they could not be confirmed on the
current release or CVS tree.
One of my goals was to encourage the use of current tools and provide a
point for getting patches into the main gcc source tree. Releases are
much more frequent now and there is no reason the cross embedded
shouldn't take advantage of that. We just have to help and be
As an aside, I have worked on and off on these RPMs for over a year.
to gcc 3.2, I could not successfully build enough crosses to justify
releasing them. I know that for *-rtems targets we couldn't move the
primary targets to gcc 3.x until the 3.1 series and GNU/Cross has been
lower priority to me than the *-rtems targets.
> On the other hand, is it better to work with the gcc-3.2.1 release to get it
> fixed? This seems (to me) a daunting task, but hopefully there will be help
I think we are better off trying to help Nick fix them. Small test
and offering to test are usually the best one can offer the maintainer
you are lucky enough to be able to actually fix it. :)
If you have fixes for 3.0.4 that are not in the current source, then we
need to work with Nick to get them merged.
In the meantime, if you want want to use the specs and build a mcore-elf
3.0.4 RPM, we can talk offline about doing that and putting it on our
> Brian LaPonsey
> Motorola Semiconductor Products
> East Kilbride, Scotland
> ----- Original Message -----
> From: "Joel Sherrill" <joel.sherrill@OARcorp.com>
> To: <email@example.com>
> Sent: Monday, December 09, 2002 11:33 PM
> Subject: GNU/Cross Tools RPMs available
> > Hi,
> > Over the past few years, the RTEMS Project has provided pre-built
> > toolsets for our target. I have leveraged this experience and
> > the build scripts to provide a fairly large set of RPMs for
> > various cross targets. I am focusing on the targets that are
> > not OS dependent and usually have targets of the form CPU-OBJECT_FORMAT.
> > These are hosted on a GNU/Linux RedHat 7.3 x86.
> > The following sources were used with RTEMS Project approved patches:
> > + binutils 2.13.1
> > + gcc 3.2.1
> > + newlib 1.10.0
> > + gdb 5.2
> > We are provided at least binutils for the following 28 targets:
> > arc-elf arm-elf arm-wince avr-elf d10v-elf d30v-elf fr30-elf
> > h8300-coff hppa1.1-proelf i386-elf i960-coff i960-elf
> > m32r-elf m68hc11-elf m68k-coff m68k-elf mcore-elf
> > mips64orion-elf mips-elf mn10200-elf mn10300-elf powerpc-eabi
> > sh-coff sh-elf sh-hms sparc-elf v850-elf xscale-elf
> > and provide RPMs for everything that would build for
> > that target (17 gcc targets, and 26 gdb targets). We
> > filed PRs on the problems. The resulting RPMs
> > are available at ftp://ftp.oarcorp.com/pub/gnucross/.
> > The general instructions for installation are to install the
> > base packages which contain files that are target CPU indepedent
> > and then the target specific files. More specifically:
> > rpm -i gnucross-base-binutils-2.13.1-1.i386.rpm
> > rpm -i gnucross-base-gcc-gcc3.2.1newlib1.10.0-3.i386.rpm
> > rpm -i gnucross-base-gdb-5.2-1.i386.rpm
> > then for each target:
> > rpm -i TARGET-binutils-2.13.1-1.i386.rpm
> > rpm -i TARGET-gcc-gcc3.2.1newlib1.10.0-3.i386.rpm
> > rpm -i TARGET-c++-gcc3.2.1newlib1.10.0-3.i386.rpm
> > rpm -i TARGET-gdb-5.2-1.i386.rpm
> > When you are done, you should have a working toolset for
> > TARGET in /opt/gnucross. So just add /opt/gnucross/bin to
> > your PATH.
> > I am interested in hearing feedback. Please discuss things
> > on the crossgcc list. If things go well with these, we should
> > be able to provide the same things for Cygwin and Solaris.
> > Thanks.
> > --
> > Joel Sherrill, Ph.D. Director of Research & Development
> > joel@OARcorp.com On-Line Applications Research
> > Ask me about RTEMS: a free RTOS Huntsville AL 35805
> > Support Available (256) 722-9985
> > ------
> > Want more information? See the CrossGCC FAQ,
> > Want to unsubscribe? Send a note to
> Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to firstname.lastname@example.org
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to email@example.com
More information about the crossgcc