Error compiling mpc8260ads
joel.sherrill at oarcorp.com
Wed Feb 14 16:53:44 UTC 2007
Ralf Corsepius wrote:
> On Wed, 2007-02-14 at 15:29 +0200, Leon Pollak wrote:
>> On Wednesday 14 February 2007 15:24, Ralf Corsepius wrote:
>>>> I use 220.127.116.11 source. Is it not good enough?
>>> If you mean the tarball, no ... development has progressed quite a lot
>>> since then.
>> OK, then, please, what will you recommend to take for the new project with my
>> own BSP? CVS sounds too dangerous, no?
> Absolutely not.
> Though there are still patches going in, it currently is supposed to be
> buildable at any time.
I regularly build CVS for the 4.7 branch and CVS head for all BSPs and
Any time I notice CVS commits or there are new tools, everything gets a
Tests are at least spot checked on one or more simulator BSPs (psim, any
pc386 on qemu, jmr3904).
So even if a patch breaks something, it doesn't stay broken for long. :-)
>>>> /usr/bin/m4: unrecognized option `--debugfile=autom4te.cache/traces.0t'
>>>> Try `/usr/bin/m4 --help' for more information.
>>> Which OS is this?
>> Linux FC6
> The least troublesome of all possible choices!!!
> Add the rtems-yum repo to your yum setup.
> rpm -U \
> Install the rpms you need
> yum install rtems-4.7-automake
> yum install rtems-4.7-<cpu>-rtems4.7-gcc
> yum install rtems-4.7-<cpu>-rtems4.7-gcc-c++
> Set PATH=/opt/rtems-4.7/bin:$PATH
> and you should be finished with all toolchain issues.
> Afterwards your environment will be the same I am using (and you will
> automatically receive updates with each "yum update")
>>> Which m4 is this?
>> [root at leonp rtems-src.18.104.22.168]# m4 --version
>> GNU M4 1.4.5
>> Written by Rene' Seindal.
> The same version I am using.
> rtems-users mailing list
> rtems-users at rtems.com
More information about the users