Building GNU Cross Compiler Toolset (v4.7.0)
joel.sherrill at oarcorp.com
Mon Mar 12 16:12:20 UTC 2007
Ralf Corsepius wrote:
> On Mon, 2007-03-12 at 10:50 -0500, Joel Sherrill wrote:
>> Ralf Corsepius wrote:
>>> On Mon, 2007-03-12 at 11:42 +0000, Karevaara, Teemu wrote:
>>>> Does anyone know where the files are or are they needed at all?
>>> The diffs being mention in the docs are those versions which had been
>>> current when the docs had been updated and don't necessarily match with
>>> those actually being used.
>> I built the 4.7.0 documentation last week. So it shouldn't be horribly
>> out of date.
> It is, because the version numbers are hard-coded into docs/ and are not
> automatically generated.
> Also, note: The toolchains and their versions are decoupled from a
> particulare RTEMS release. There is no strict and constant binding
> between toolchain patches/toolchain version and RTEMS release.
Right and this is a change from previous release branches and why this
part of the documentation is in question,
>> If those are not the current diffs, what step do you think I
>> missed in
>> making the documentation?
> Editing the docs (I presume the OP was referring to docs/)
Yes. The OP was to the docs.
>> I went ahead and cut 4.7.0 primarily to catch
>> these type of procedural errors. :)
> The only way I can think of to remedy this situation is to put the
> patches into a directory and let the docs point to this.
That is probably the only solution that will work and be correct long
The downside is that the user will still have to pick the patches. The
of the Getting Started was to be correct at the time of the release tarball.
But how does the user know which tool version and patch to build with?
> I have no idea where you pushed the toolchain sources to nor do I have
> write access to this directory.
I think you should have write access. My personal account works so
More information about the users