[gccsdk] GCC SVN reorganisation

John Tytgat John.Tytgat at aaug.net
Tue Oct 28 13:31:24 PDT 2014

In message <20141027104247.GG25262 at chiark.greenend.org.uk>
          Theo Markettos <theo at markettos.org.uk> wrote:

> I notice that GCC's SVN has been shuffled about so that there's
> a new directory gccsdk/trunk/tools in addition to gccsdk/trunk/gcc4.
> tools now contains asasm, decaof and elftoolchain.
> However, when I build GCCSDK via ./build-world it's still looking for asasm
> in gccsdk/trunk/gcc4/riscos/ and the build fails as it isn't there.  If I check
> out the tools directory there, ie
> svn co svn://svn.riscos.info/gccsdk/trunk/gcc4
> svn co svn://svn.riscos.info/gccsdk/trunk/tools
> mv tools/* gcc4/riscos/
> then I start to make some progress but the build rapidly falls over:

You shouldn't need to do that.  A checkout of trunk/gcc4 should
automatically pull asasm and its dependencies (decaof - only for testing,
and elftoolchain) from the right place via the svn:externals:

$ svn propget svn:externals svn://svn.riscos.info/gccsdk/trunk/gcc4/riscos
^/trunk/tools/asasm asasm

$ svn propget svn:externals svn://svn.riscos.info/gccsdk/trunk/tools/asasm
^/trunk/tools/decaof decaof
^/trunk/tools/elftoolchain/current-trunk elftoolchain

Any idea why the svn:externals didn't work for you ?

The reason for reshuffling is the recognition that most things under
riscos directory are standalone and not necessarily GCCSDK only tools.
Never went further than moving out asasm but we could equally do
the same for cmunge, drenderer, elf2aif, etc.

> cd /var/lib/jenkins/workspace/gcc-head/gcc4/riscos && ./build-it -f cross

Oh, is this an attempt for a ci build setup ? :-)

> [...]
> So that I can update the guide at:
> http://www.riscos.info/index.php/Using_GCCSDK
> what's the 'approved' way to check these out so the build completes?

$ svn co svn://svn.riscos.info/gccsdk/trunk/gcc4/

John Tytgat, in his comfy chair at home
John.Tytgat at aaug.net

More information about the gcc mailing list