[gccsdk] ctorrent port for the autobuilder

alan buckley alan_baa at hotmail.com
Wed Apr 4 13:30:18 BST 2007


>John Tytgat <John.Tytgat at aaug.net> wrote on Mon, 02 Apr 2007 21:25:41 +0100
>
>In message <BAY101-F18A9DA431F7016E4EB3B93F0600 at phx.gbl>
>           "alan buckley" <alan_baa at hotmail.com> wrote:
>
> > >John Tytgat <John.Tytgat at aaug.net> wrote on Sat, 31 Mar 2007 14:02:16
> > >

[snip bits I've commented on already in a seperate email]

>Could that be desklib because its trunk is now ELF support only ?
>If so, does this patch
><URL:http://www.riscos.info/pipermail/gcc/2007-February/003722.html> help ?
>If so, feel free to apply that.

I believe it was. The patch did help.


> > What compiler should the autobuilder projects be built against? Is it 
>the
> > case I should alway be using the latest bleeding edge version?
>
>Assuming you're asking if GCCSDK 3.4.6 and/or the current development
>GCCSDK 4 version should be used for Autobuilder then IMHO:
>
>1. During a transition period GCCSDK 3.4.6 is be the supported version
>    for Autobuilder.
>2. During that transition period we bring all projects in Autobuiler
>    up-to-date with GCCSDK 3.4.6 and at some point in time in a parallel
>    track someone can do builds using the development GCCSDK 4.  I'm
>    volunteering to do the latter as soon as a large set of projects are
>    buildable with GCCSDK 3.4.6 again.
>    With a little bit of effort and coordination, I think this could be 
>done
>    in a short time (one a two months ?).
>    When Lee has the biggest issues worked out concerning the shareble 
>libs,
>    we can do an additional shareble lib build as well and we can check how
>    those work out in RISC OS.  Having an immediate availability of a large
>    set of well known shared libraries is key factor to:
>    2.1. get this of the ground
>    2.2. and to get it well debugged and proven as working solution
>3. The transition period finishes when we have our first GCCSDK 4 release.
>
>And as you can see, having those Autobuilder projects in shape again, is
>the crutial aspect in this plan.  How does that sound ?

This sounds good to me.

>
> > And if so
> > how do we get things like the Shared unix library and elfloader to match
> > it distributed?
>
>Currently there are no changes made to SharedUnixLibrary module in GCCSDK 4
>and I don't think there are any pending ones.  Concerning JMB's ELFLoader,
>I don't think we're going to use it for static ELF binaries (or advocate
>to use it).  It works only for static ELF binaries and personally I believe
>the GCCSDK user, i.e. developer, is better of using elf2aif instead as it
>doesn't impose the need of an extra module on his users (a module which
>will become obsolete over time when the full shared library support gets
>deployed as this will cover the static ELF case as well).
>

OK, this seems sensible to me. For the time being it appears I can just
ignore GCCSDK 4.0 and ELF.

Regards,
Alan

_________________________________________________________________
Get Hotmail, News, Sport and Entertainment from MSN on your mobile.  
http://www.msn.txt4content.com/




More information about the gcc mailing list