Friday, 3 February 2017

[gccsdk] GCCSDK buglist inaccessible

I'm unable to access the GCCSDK buglist page
http://www.riscos.info/bugzilla/ .

This is what I get:

Not Found
The requested URL /bugzilla/ was not found on this server.
Apache/2.2.16 (Debian) Server at www.riscos.info Port 80

Has it been moved?

Duncan


_______________________________________________
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 wrote on 01 February 2017 15:11

 

> On Wed, Feb 01, 2017 at 12:53:02PM +0000, alan buckley wrote:

> >

> > > There is a bit of a filetyping issue, !Boot,feb and gcc,elf etc.

> 

> You should bear in mind that the 'all files in zip' is an option offered by

> Jenkins, which knows nothing about RISC OS and doesn't preserve filetypes.

> The named zips are the ones generated by the autobuilder.

 

> > As you say the ci build needs to do the ./create-gcckit -pkg as well as that is used to produce

> > the non riscpkg packaged zip and tar files.

 

> Strangely that was present in the script but I commented it out last April.

> I don't remember why.

 

I think I know now – see below

 

> > Theo, do you want to fix your ci build to build the gcckit zips and then we can use that?

> > If you are not ready, or don't have time I have created new builds here and

> > can upload them instead.

 

> Fixed - new build #126 going through now.

 

This time the create-gcckit packages have been built OK, the riscpkg

packages haven't.

 

It may be that ./create-gcckit -pkg corrupts the directories so the packages

can't be built.

 

I hope you don't mind, I've rearranged the order of the calls of ./create-gcckit

and ./create-riscpkg in Jenkins and started build #127 to see if this fixes it.

 

Regards,

Alan

Wednesday, 1 February 2017

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

On Wed, Feb 01, 2017 at 12:53:02PM +0000, alan buckley wrote:
>
> > There is a bit of a filetyping issue, !Boot,feb and gcc,elf etc.

You should bear in mind that the 'all files in zip' is an option offered by
Jenkins, which knows nothing about RISC OS and doesn't preserve filetypes.
The named zips are the ones generated by the autobuilder.

> As you say the ci build needs to do the ./create-gcckit -pkg as well as that is used to produce
> the non riscpkg packaged zip and tar files.

Strangely that was present in the script but I commented it out last April.
I don't remember why.

> Theo, do you want to fix your ci build to build the gcckit zips and then we can use that?
> If you are not ready, or don't have time I have created new builds here and
> can upload them instead.

Fixed - new build #126 going through now.

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

alan buckley, on 1 Feb, wrote:

>
> David Pitt wrote on 01 February 2017 10:14
>
> > Theo Markettos, on 31 Jan, wrote:
>
> > > 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?
>
> The packaged version at the above address seem to be fine. I did a very
> brief test of checking the version and compiling the examples after
> installing with PackMan.

That looks OK.

> > There is a bit of a filetyping issue, !Boot,feb and gcc,elf etc.
>
> > Downloading on Ubuntu and copying to the RPi3 with LanMan98 proces a
> > working version.
>
> > The output from the autobuilder filetypes fully here and was ready to
> > run.
>
> > ./create-gcckit -pkg does that AIUI.
>
> > HTH.
>
> I saw this with the kits folder at:
>
http://ci.riscos.info/job/gcc-4.7-native/lastSuccessfulBuild/artifact/gcc4/release-area/kits/
>
> Is this what you were using David?

I managed to find the 'wrong' version first!

--
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

alan buckley, on 1 Feb, wrote:

>
> David Pitt wrote on 01 February 2017 10:14
>
> > Theo Markettos, on 31 Jan, wrote:
>
> > > 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?
>
> The packaged version at the above address seem to be fine. I did a very
> brief test of checking the version and compiling the examples after
> installing with PackMan.

That looks OK.

> > There is a bit of a filetyping issue, !Boot,feb and gcc,elf etc.
>
> > Downloading on Ubuntu and copying to the RPi3 with LanMan98 proces a
> > working version.
>
> > The output from the autobuilder filetypes fully here and was ready to
> > run.
>
> > ./create-gcckit -pkg does that AIUI.
>
> > HTH.
>
> I saw this with the kits folder at:
>
http://ci.riscos.info/job/gcc-4.7-native/lastSuccessfulBuild/artifact/gcc4/release-area/kits/
>
> Is this what you were using David?

Probably, I managed to find the 'wrong' version first.

--
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

 

David Pitt wrote on 01 February 2017 10:14

> Theo Markettos, on 31 Jan, wrote:

 

> > 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?

 

The packaged version at the above address seem to be fine. I did a very brief test of checking

the version and compiling the examples after installing with PackMan.

 

> There is a bit of a filetyping issue, !Boot,feb and gcc,elf etc.

 

> Downloading on Ubuntu and copying to the RPi3 with LanMan98 proces a working

> version.

 

> The output from the autobuilder filetypes fully here and was ready to run.

 

>./create-gcckit -pkg does that AIUI.

 

> HTH.

 

I saw this with the kits folder at:

http://ci.riscos.info/job/gcc-4.7-native/lastSuccessfulBuild/artifact/gcc4/release-area/kits/

 

Is this what you were using David?

 

As you say the ci build needs to do the ./create-gcckit -pkg as well as that is used to produce

the non riscpkg packaged zip and tar files.

 

Theo, do you want to fix your ci build to build the gcckit zips and then we can use that?

If you are not ready, or don't have time I have created new builds here and

can upload them instead.

 

Regards,

Alan

 

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

Theo Markettos, on 31 Jan, wrote:

> 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?

There is a bit of a filetyping issue, !Boot,feb and gcc,elf etc.

Downloading on Ubuntu and copying to the RPi3 with LanMan98 proces a working
version.

The output from the autobuilder filetypes fully here and was ready to run.

./create-gcckit -pkg does that AIUI.

HTH.

--
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