Mailing Lists

Tuesday, 31 January 2017

Re: [gccsdk] GCC for RISC OS 4.7.4 release 3

On Tue, Jan 31, 2017 at 01:01:50PM +0000, alan buckley wrote:
> I see there has been a check in to fix this. I'll rebuild the compilers and upload them again.

There's a build #125 here:
http://ci.riscos.info/job/gcc-4.7-native/lastSuccessfulBuild/artifact/gcc4/release-area/riscpkg/autobuilder_website/

It might be better to use that since we track what it was built with.
Are you able to test and confirm functionality?

Theo

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] GCC for RISC OS 4.7.4 release 3

Chris Gransden wrote on 28 January 2017 13:00

> In article

<LOXP123MB13184E8FA8FCF8721E824C77F0760@LOXP123MB1318.GBRP123.PROD.OUTLOOK.COM>,

alan buckley <alan_baa@hotmail.com> wrote:

> > I've uploaded release 3 of GCC 4.7.4 for RISC OS today. It should appear in the PackMan package list and the riscos info packages website tomorrow. The direct download should be available now.

> > I'll do a proper release announcement early next week and also update the GCC Releases page at riscos info. Is there anything else that needs updating?

> gcc -v and g++ -v are still showing as release 2.

I see there has been a check in to fix this. I'll rebuild the compilers and upload them again.

Regards,

Alan

Monday, 30 January 2017

Re: [gccsdk] GCC for RISC OS 4.7.4 release 3

Theo Markettos, on 30 Jan, wrote:

> On Mon, Jan 30, 2017 at 12:30:57PM +0000, David Pitt wrote:
> > Some time ago I could do commits, for !Thump. There is a bit of a C
> > expertise deficit here, I only tried this commit as it was simple stuff.
[
snip]

> What does 'svn commit' do?

nano opens.

I wrote a log entry, exited nano and confirmed the commit.

--
David Pitt

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] GCC for RISC OS 4.7.4 release 3

On Mon, Jan 30, 2017 at 12:30:57PM +0000, David Pitt wrote:
> Some time ago I could do commits, for !Thump. There is a bit of a C
> expertise deficit here, I only tried this commit as it was simple stuff.
>
> Something may have got fouled up, I now see this repeatedly.
>
> pittdj@Ubuntu1604box:/media/pittdj/GCCSDK$ svn co
> svn://svn.riscos.info/gccsdk/trunk/gcc4/ gcc4
>
> Fetching external item into 'gcc4/riscos/asasm':
>
> Fetching external item into 'gcc4/riscos/asasm/decaof':
> Checked out external at revision 7129.
>
>
> Fetching external item into 'gcc4/riscos/asasm/elftoolchain':
> Checked out external at revision 7129.
>
> Checked out external at revision 7129.
>
> Checked out revision 7129.
> pittdj@Ubuntu1604box:/media/pittdj/GCCSDK$
>
> If that is my fault then my apologies.

That's normal - GCCSDK uses svn externals, in other words there are child
repos that also get checked out when you check out the top level.

What does 'svn commit' do?

> > I've committed a variant as r7129 - it's now a Makefile variable so is
> > easier to spot at the top of the file.
>
> A much better idea.

On the subject of curl, it looks like it's breaking in Jenkins because it
depends on cacertificates producing a library tarball for the curl job,
which it doesn't. I'm not sure what the build dependency on cacertificates
is meant to mean, given the certs are not compiled into the binary (AIUI).
(is this an install-time dependency?)

Theo

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] GCC for RISC OS 4.7.4 release 3

Theo Markettos, on 30 Jan, wrote:

[snip]
>
> The list of things we can't build is a bit long:
> http://ci.riscos.info/job/packages/ click on Last Failure for a full list.
> I suspect some of the failures are simple - any help in fixing them up is
> appreciated.

curl has just built here.

https://www.riscosopen.org/forum/forums/11/topics/8983
--
David Pitt

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] GCC for RISC OS 4.7.4 release 3

Theo Markettos, on 30 Jan, wrote:

> On Mon, Jan 30, 2017 at 10:48:19AM +0000, David Pitt wrote:
> > This info is baked into gcc4/Makefile. The following fixed it.
> >
> > GCC_CONFIG_ARGS += --with-pkgversion='GCCSDK GCC $(GCC_VERSION) Release
> > 3' \ --with-bugurl=http://gccsdk.riscos.info/ BINUTILS_CONFIG_ARGS +=
> > --with-pkgversion='GCCSDK GCC $(GCC_VERSION) Release 3' \
> > --with-bugurl=http://gccsdk.riscos.info/ GDB_CONFIG_ARGS +=
> > --with-pkgversion='GCCSDK GCC $(GCC_VERSION) Release 3' \
> > --with-bugurl=http://gccsdk.riscos.info/
> >
> > I tried to commit that but it does not appear to have worked.
>
> You probably don't have commit rights - if you're going to be making more
> changes I can make you an account.

Some time ago I could do commits, for !Thump. There is a bit of a C
expertise deficit here, I only tried this commit as it was simple stuff.

Something may have got fouled up, I now see this repeatedly.

pittdj@Ubuntu1604box:/media/pittdj/GCCSDK$ svn co
svn://svn.riscos.info/gccsdk/trunk/gcc4/ gcc4

Fetching external item into 'gcc4/riscos/asasm':

Fetching external item into 'gcc4/riscos/asasm/decaof':
Checked out external at revision 7129.

Fetching external item into 'gcc4/riscos/asasm/elftoolchain':
Checked out external at revision 7129.

Checked out external at revision 7129.

Checked out revision 7129.
pittdj@Ubuntu1604box:/media/pittdj/GCCSDK$

If that is my fault then my apologies.

> I've committed a variant as r7129 - it's now a Makefile variable so is
> easier to spot at the top of the file.

A much better idea.

--
David Pitt

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] GCC for RISC OS 4.7.4 release 3

On Mon, Jan 30, 2017 at 10:48:19AM +0000, David Pitt wrote:
> This info is baked into gcc4/Makefile. The following fixed it.
>
> GCC_CONFIG_ARGS += --with-pkgversion='GCCSDK GCC $(GCC_VERSION) Release 3' \
> --with-bugurl=http://gccsdk.riscos.info/
> BINUTILS_CONFIG_ARGS += --with-pkgversion='GCCSDK GCC $(GCC_VERSION) Release
> 3' \
> --with-bugurl=http://gccsdk.riscos.info/
> GDB_CONFIG_ARGS += --with-pkgversion='GCCSDK GCC $(GCC_VERSION) Release 3' \
> --with-bugurl=http://gccsdk.riscos.info/
>
> I tried to commit that but it does not appear to have worked.

You probably don't have commit rights - if you're going to be making more
changes I can make you an account.

I've committed a variant as r7129 - it's now a Makefile variable so is
easier to spot at the top of the file.

That's running through Jenkins (ci.riscos.info) now.
http://ci.riscos.info/job/gcc-4.7-native/124/

Yesterday I gave various of the CI machines a cleanout - Jenkins eats disc
for breakfast and several had tied themselves in knots (eg wouldn't boot).
Things should be back to normal now.

I started a full build of all the packages in the interests of cleaning the
cobwebs out of the infrastructure. Do we know how new packages need to be
to have ARMv8 support? Should we aim to do a full release of everything we
can build?

The list of things we can't build is a bit long:
http://ci.riscos.info/job/packages/
click on Last Failure for a full list.
I suspect some of the failures are simple - any help in fixing them up is
appreciated.

Theo

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK