Monday, 27 February 2017

Atari builds

Hi guys,

although I don't use Netsurf and have no time to dig in, just out of curiosity, what do you mean by this:
On 06/02/2017 12:25, Vincent Sanders wrote:
> atari - The atari frontend is built for m68k and coldfire variants  >          using a variant of the netsurf cross compliation  >          toolchain/sdk. No serious updates have been made to this  >          toolchain in some time and it has become a burden.  >  >         Unless this is addressed before the next developer weekend the  >          frontend will be disabled in the CI and subsequently code  >          removed.
There's nothing wrong with our gcc, it's still 4.6.4 and every other Atari software developer uses it. It's old, yes, but there are some technical obstacles to move beyond that version (although this may be no longer the case, see http://d-bug.mooo.com/beyondbrown/post/gcc-6/).

So what exactly burdens you? Is your new code failing to compile on 4.6.4?

Regards,
Miro

Saturday, 25 February 2017

Re: Congratulations!

Congratulations also from Atari user replying from Gmail using #4000 build!
I really hope Atari wont be removed from daily build as you see it
just works great!

Keep it goin doing great job!

Vido


2017-02-25 10:59 GMT+01.00, Richard Porter <ricp@minijem.plus.com>:
> On 25 Feb 2017 John Williams wrote:
>
>> Congratulations to the NetSurf team for all the hard work it took to get
>> to
>> #4000!
>
> Hear, hear!
> --
> Richard Porter http://www.minijem.plus.com/
> Skype: minijem2 mailto:ricp@minijem.plus.com
> I don't want a "user experience" - I just want stuff that works.
>
>

Re: Congratulations!

On 25 Feb 2017 John Williams wrote:

> Congratulations to the NetSurf team for all the hard work it took to get to
> #4000!

Hear, hear!
--
Richard Porter http://www.minijem.plus.com/
Skype: minijem2 mailto:ricp@minijem.plus.com
I don't want a "user experience" - I just want stuff that works.

Congratulations!

Congratulations to the NetSurf team for all the hard work it took to get to
#4000!

Best wishes,

John

--
| John Williams
| johnrw@ukgateway.net

I think, therefore I am unsure - I think! *

Monday, 20 February 2017

Re: [gccsdk] Raspberry Pi 3 builds of apps/libraries for the Autobuilder package site

On Mon, Feb 20, 2017 at 01:31:08PM +0000, alan buckley wrote:
> I've a virtual machine set up so I can rebuild and then upload anything
> else required. However there are a lot of packages, so it would make
> sense (to me anyway) if we could have a list of the things people would
> like built sooner rather than later. When I say a list, just using this
> thread would be enough for me.
>
> I will use the Jenkins builder to test if an app/library is likely to build
> and if it is, then do a build on my machine as that will force new
> builds of any dependent libraries. I will update package numbers if
> necessary.

Just to note that the 'build-all-packages' job in Jenkins will build
everything, sorted by dependency order - in other words if program A depends
on library B which depends on library C, it'll build C, then B, then A. The
'build-all-packages_generator' calculates those dependencies from the
'depends' files in SVN, so you just need to run that to update the
relationships.

It does, however, try to build everything - last time I did this it took
about 10 hours (likely to be longer if we have more builds that make
progress). So not so great if you're trying to debug build dependencies -
probably makes sense to fix problems on your machine.

(Oh, I notice it's run out of disc again. I'll try and fix that tomorrow)

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

[gccsdk] Raspberry Pi 3 builds of apps/libraries for the Autobuilder package site

 

I've just rebuilt and uploaded wget and the ssl libraries to the autobuilder

package site using the RPi3 compatible version of the GCCSDK.

They should appear in the index and on the website tomorrow.

 

I've a virtual machine set up so I can rebuild and then upload anything

else required. However there are a lot of packages, so it would make

sense (to me anyway) if we could have a list of the things people would

like built sooner rather than later. When I say a list, just using this

thread would be enough for me.

 

I will use the Jenkins builder to test if an app/library is likely to build

and if it is, then do a build on my machine as that will force new

builds of any dependent libraries. I will update package numbers if

necessary.

 

If you suggest something that needs building, it would be ideal if

you could test it once the new version get's uploaded as I will

have little time to do any testing myself and don't have a RPi 3.

 

If a package doesn't build, I'll have a look if there is a quick fix,

otherwise I'll move on so that we can get more stuff up to date.

 

From attempts over the last couple of years, I know that there is quite

a lot of things that no longer build, but this will at least give us a

starting point.

 

Please don't just point me to the other threads/forums where some

programs have been mentioned as the idea is to get the list here

where I could work from it.

 

I'm trying to make this quick and easy, but if someone else wants

to manage this in a better way, please go ahead. I'll still be happy

to run whatever builds are requested.

 

Regards,

Alan

Monday, 13 February 2017

Re: [Rpcemu] RPCEmu and Sibelius

>
> Op 13 feb. 2017, om 10:51 heeft Jim Lesurf <jcgl@audiomisc.co.uk> het volgende geschreven:
>
> In article <C90FD608-A990-467C-944C-A665E7AB0914@carlanieuwenhuis.nl>,
> Carla Nieuwenhuis <piano@carlanieuwenhuis.nl> wrote:
>> Hi Jim,
>
>> I tried this a long time ago but Sibelius is protected. You need the key
>> floppy to bind the software to your harddisc or something like that. I
>> couldn't get it to work.
>
>> Peter v.d. Vos
>
> Did you try making an image file of your original HD on which Sibelius was
> installed and using that as a HD with RPCEmu?
>
> I can see that having to use a floppy disc to enable an install would be
> problematic! But I'm thinking of when you start with a HD which has
> Sibelius installed and working and clone that to a file with a tool like
> 'dd' or suitable equivalent that captures every detail of the HD. Then use
> that image as a RPCEmu 'hard disc'.
>
> Am I correct in understanding that:
>
> A) Once you have installed onto a HD Sibelius *doesn't* require you to keep
> using the key floppy? i.e. That the install then runs having found the
> relevant 'installed' pattern on the HD.
>
> B) That you could make a backup of the HD in case it failed. Then the
> backup would work?

It is coming back again, it was a long time ago.

What I found was that it had something to do with timestamps of some files. If you 'Stamped' the !Boot directory your Sibelius copy became corrupt (but could be restored using the floppy).

If you make a backup of your !Boot directory you could restore the installation yourself.

I don't know for sure but my RPCEmulator was not very stable in the beginning (on my Mac when I was testing) and rewriting the !Boot directory did give all kind of problems.

An other thing is that Sibelius needs a 16 colour display and that didn't work very well in the beginning.

But, times changes. Maybe it could work now.


Peter


_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Re: [Rpcemu] Rpcemu Digest, Vol 110, Issue 2 - floppies

Hullo chaps,
                 I imaged my key floppies and mount those images using !ADFFS for install and update.  I'll happily document the steps if needed.

Cheerio!

Mike

On 13 February 2017 at 20:00, <rpcemu-request@riscos.info> wrote:
Send Rpcemu mailing list submissions to
        rpcemu@riscos.info

To subscribe or unsubscribe via the World Wide Web, visit
        http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
or, via email, send a message with subject or body 'help' to
        rpcemu-request@riscos.info

You can reach the person managing the list at
        rpcemu-owner@riscos.info

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Rpcemu digest..."


Today's Topics:

   1. Re: RPCEmu and Sibelius (Jim Lesurf)


----------------------------------------------------------------------

Message: 1
Date: Mon, 13 Feb 2017 09:51:40 +0000 (GMT)
From: Jim Lesurf <jcgl@audiomisc.co.uk>
To: rpcemu@riscos.info
Subject: Re: [Rpcemu] RPCEmu and Sibelius
Message-ID: <560db0117ejcgl@audiomisc.co.uk>
Content-Type: text/plain

In article <C90FD608-A990-467C-944C-A665E7AB0914@carlanieuwenhuis.nl>,
   Carla Nieuwenhuis <piano@carlanieuwenhuis.nl> wrote:
> Hi Jim,

> I tried this a long time ago but Sibelius is protected. You need the key
> floppy to bind the software to your harddisc or something like that. I
> couldn't get it to work.

> Peter v.d. Vos

Did you try making an image file of your original HD on which Sibelius was
installed and using that as a HD with RPCEmu?

I can see that having to use a floppy disc to enable an install would be
problematic! But I'm thinking of when you start with a HD which has
Sibelius installed and working and clone that to a file with a tool like
'dd' or suitable equivalent that captures every detail of the HD. Then use
that image as a RPCEmu 'hard disc'.

Am I correct in understanding that:

A) Once you have installed onto a HD Sibelius *doesn't* require you to keep
using the key floppy? i.e. That the install then runs having found the
relevant 'installed' pattern on the HD.

B) That you could make a backup of the HD in case it failed. Then the
backup would work?

Jim

--
Electronics  http://www.st-and.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
Armstrong Audio  http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc  http://www.audiomisc.co.uk/index.html




------------------------------

_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu


End of Rpcemu Digest, Vol 110, Issue 2
**************************************

Re: [Rpcemu] RPCEmu and Sibelius

In article <C90FD608-A990-467C-944C-A665E7AB0914@carlanieuwenhuis.nl>,
Carla Nieuwenhuis <piano@carlanieuwenhuis.nl> wrote:
> Hi Jim,

> I tried this a long time ago but Sibelius is protected. You need the key
> floppy to bind the software to your harddisc or something like that. I
> couldn't get it to work.

> Peter v.d. Vos

Did you try making an image file of your original HD on which Sibelius was
installed and using that as a HD with RPCEmu?

I can see that having to use a floppy disc to enable an install would be
problematic! But I'm thinking of when you start with a HD which has
Sibelius installed and working and clone that to a file with a tool like
'dd' or suitable equivalent that captures every detail of the HD. Then use
that image as a RPCEmu 'hard disc'.

Am I correct in understanding that:

A) Once you have installed onto a HD Sibelius *doesn't* require you to keep
using the key floppy? i.e. That the install then runs having found the
relevant 'installed' pattern on the HD.

B) That you could make a backup of the HD in case it failed. Then the
backup would work?

Jim

--
Electronics http://www.st-and.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc http://www.audiomisc.co.uk/index.html


_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Sunday, 12 February 2017

Re: github crash

In message <83ea410d56.DaveMeUK@my.inbox.com>
Dave Higton <dave@davehigton.me.uk> wrote:

>In message <000646be.01f994909daa@smtp.freeola.net>
> Peter Slegg <p.slegg@scubadivers.co.uk> wrote:
>
>>The Atari Freemint OS moved to github and they posted this link to
>>an Issue:
>>
>>https://github.com/freemint/freemint/pull/20
>>
>>When I open it with NS, it downloads about 14k in about 3-4mins but
>>then shows the error below and crashes out.
>>
>>Failure when receiving data from the peer
>>render/html_object.c:127: html_object_callback: Assertion
>>`c->base.status != CONTENT_STATUS_ERROR' failed.
>
>I just tried it on CI#3984 on RISC OS. The page loads reasonably
>quickly and there's no crash. The only problem I see is that the
>text within <code></code> tags is rendered as black rectangles,
>with no visible or selectable text.

Sorry, I must correct my report. If I select text including the
black rectangles, the text becomes inverted to white, while the
rectangle's background remains black. This makes the text legible.
So the rectangles must normally be black text on a black background.

I ought to report this as a separate bug.

Dave

Re: github crash

On Sun, 12 Feb 2017 13:48:31 GMT, Dave Higton wrote:

> In message <000646be.01f994909daa@smtp.freeola.net>
> Peter Slegg <p.slegg@scubadivers.co.uk> wrote:
>
> >The Atari Freemint OS moved to github and they posted this link to
> >an Issue:
> >
> >https://github.com/freemint/freemint/pull/20
> >
> >When I open it with NS, it downloads about 14k in about 3-4mins but
> >then shows the error below and crashes out.

This is an odd one. I suspect that error is due to NetSurf processing
an incomplete file, as the slow speed suggests it may not have
downloaded fully (NetSurf should recognise this and you'd get a
timeout error, so not sure why that isn't happening)

I tested here on the closest thing I have to the Atari build - the
Amiga version built for OS3/68k. This also has problems, it gets as
far as fetching, processing and then the entire computer locks up.
The Amiga build for OS4/PPC works fine. This suggests that there may
be some 68k-specific problem in NetSurf or one of the libraries we
use.

I've been playing around with a 68k optimised version of OpenSSL
and I get slightly different behaviour with the non-optimised version.
This may point to OpenSSL being the problem, or it could be an
illegal memory access somewhere where the slight change in where code
is located is enough to make it crash rather than freeze. I don't know
how to go about debugging this.

> I just tried it on CI#3984 on RISC OS. The page loads reasonably
> quickly and there's no crash. The only problem I see is that the
> text within <code></code> tags is rendered as black rectangles,
> with no visible or selectable text.

On OS4 I'm getting dark grey text (probably a quirk of the font
engine) on a black background, so the text is there but the background
is the wrong colour. Looking at Firefox the background should be
light grey - my suspicion is that the light grey is being created by
using the alpha channel, which I believe NetSurf ignores for
rendering.

Chris

Re: netsurf: branch master updated. release/3.6-238-g703fd10

In message <E1ccrGZ-0006En-9B@platypus.pepperfish.net>
NetSurf Browser Project (Commit Mailer)
<no-reply@netsurf-browser.org> wrote:

> Gitweb links:
>
> ...log
> http://git.netsurf-browser.org/netsurf.git/shortlog/703fd10400f83bd136acf46162fe109f87d5e538
> ...commit
> http://git.netsurf-browser.org/netsurf.git/commit/703fd10400f83bd136acf46162fe109f87d5e538
> ...tree
> http://git.netsurf-browser.org/netsurf.git/tree/703fd10400f83bd136acf46162fe109f87d5e538
>
> The branch, master has been updated
> via 703fd10400f83bd136acf46162fe109f87d5e538 (commit)
> from 11a83a951cf8e757a3a06dfe762cda41349bbd49 (commit)
>
> Those revisions listed above that are new to this repository have not
> appeared on any other notification email; so we list those revisions in
> full, below.
>
>- Log -----------------------------------------------------------------
>commitdiff http://git.netsurf-browser.org/netsurf.git/commit/?id=703fd10400f83bd136acf46162fe109f87d5e538
>commit 703fd10400f83bd136acf46162fe109f87d5e538
>Author: Michael Drake <tlsa@netsurf-browser.org>
>Commit: Michael Drake <tlsa@netsurf-browser.org>
>
> RISC OS: Initialise nsfont before hotlist.
>
> This should allow the treeview to measure the width of label text.

This appears to fix bug 2520, thank you, Michael.

I was close, but I don't think I would have found the root of the
problem.

Dave

Re: github crash

In message <000646be.01f994909daa@smtp.freeola.net>
Peter Slegg <p.slegg@scubadivers.co.uk> wrote:

>The Atari Freemint OS moved to github and they posted this link to
>an Issue:
>
>https://github.com/freemint/freemint/pull/20
>
>When I open it with NS, it downloads about 14k in about 3-4mins but
>then shows the error below and crashes out.
>
>Failure when receiving data from the peer
>render/html_object.c:127: html_object_callback: Assertion
>`c->base.status != CONTENT_STATUS_ERROR' failed.

I just tried it on CI#3984 on RISC OS. The page loads reasonably
quickly and there's no crash. The only problem I see is that the
text within <code></code> tags is rendered as black rectangles,
with no visible or selectable text.

Sorry if this isn't as helpful as we'd like, but maybe reporting
that the RO version doesn't have the problem may help in some way.

Dave

cocoa frontend

As previously stated the cocoa frontend has been disabled in the CI
and any build errors in this frontend are no longer considered to
"break the build"

Unless a maintainer for cocoa comes forward and fixes it so it
compiles and runs before the next developer weekend in June this
frontend will be removed from the source at that time.


--
Regards Vincent
http://www.kyllikki.org/

Re: [Rpcemu] RPCEmu and Sibelius

Very interested to know.

--
http://rrt.sc3d.org


On Feb 12, 2017 11:59 AM, "Jim Lesurf" <jcgl@audiomisc.co.uk> wrote:
I *think* I'm still subscribed to this list, but haven't used it or seen
anything in ages, so maybe things have changed.

However if this works...

My main questions are: Is anyone successfully using RPCEmu to run the old
RO version of Sibelius? If not, has anyone given this a try?

Worth asking as it might help some people get beyond the inevitable decline
of available working 26bit hardware.

Jim

--
Electronics  http://www.st-and.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
Armstrong Audio  http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc  http://www.audiomisc.co.uk/index.html


_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

github crash

The Atari Freemint OS moved to github and they posted this link to
an Issue:

https://github.com/freemint/freemint/pull/20

When I open it with NS, it downloads about 14k in about 3-4mins but
then shows the error below and crashes out.

Failure when receiving data from the peer
render/html_object.c:127: html_object_callback: Assertion `c->base.status != CONTENT_STATUS_ERROR' failed.


Peter

[Rpcemu] RPCEmu and Sibelius

I *think* I'm still subscribed to this list, but haven't used it or seen
anything in ages, so maybe things have changed.

However if this works...

My main questions are: Is anyone successfully using RPCEmu to run the old
RO version of Sibelius? If not, has anyone given this a try?

Worth asking as it might help some people get beyond the inevitable decline
of available working 26bit hardware.

Jim

--
Electronics http://www.st-and.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc http://www.audiomisc.co.uk/index.html


_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu

Friday, 10 February 2017

Making playlists play

I'm sure I raised a feature request for this a long time ago but I
can't see it. Anyway, is it possible to get .m3u style playlists to
play automatically on NetSurf? Oregano does this but with NS you have
to save the playlist and then launch it. I have the following MimeMap
entries for m3u:

audio/m3u MPEGURL aa7
audio/x-mpegurl MPEGURL aa7 .m3u

--
Richard Porter http://www.minijem.plus.com/
Skype: minijem2 mailto:ricp@minijem.plus.com
I don't want a "user experience" - I just want stuff that works.

Thursday, 9 February 2017

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

On Thu, Feb 09, 2017 at 04:57:20PM +0000, Lee Noar wrote:
> Thanks Alan, for taking the time to pull it all together and
> making a release.

Indeed, thanks Alan for pushing it out the door - the process always ends up
more time consuming than expected.

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

On 09/02/17 12:45, alan buckley wrote:
> Everything is uploaded and announcements to comp.sys.acorn.announce
>
> and the ROOL forum have been posted.
>
>
> I've also updated the wiki page at:
>
> http://www.riscos.info/index.php/GCCSDK_Releases
>
>
> and included details on 4.7.4 release 2 on the wiki page as it seemed to
> be missing.
>
>
> Thanks again to the GCCSDK developers for their time and effort on GCC
> for RISC OS.

Thanks Alan, for taking the time to pull it all together and
making a release.

Lee.


_______________________________________________
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

Everything is uploaded and announcements to comp.sys.acorn.announce

and the ROOL forum have been posted.

 

I've also updated the wiki page at:

http://www.riscos.info/index.php/GCCSDK_Releases

 

and included details on 4.7.4 release 2 on the wiki page as it seemed to be missing.

 

Thanks again to the GCCSDK developers for their time and effort on GCC

for RISC OS.

Alan

Wednesday, 8 February 2017

Re: Frontend maintainership

Hi,

As a frequent user of the Atari NS build I passed on your comments
to the Freemint (OS) mailing list.

I don't pretend to know much about the toolchain but they have asked
for some more details about what the issues are ?


My hope is that they may be able to investigate and improve things.

The Freemint OS recently moved onto Github.


Regards,

Peter


> Date: Mon, 6 Feb 2017 11:25:25 +0000
> From: Vincent Sanders <vince@netsurf-browser.org>
> Subject: Frontend maintainership
> To: netsurf-dev@netsurf-browser.org, netsurf-users@netsurf-browser.org
>
> At the recent NetSurf developer weekend[1] we discussed many topics
> one of which was our regular review of the frontends.
>
>
> atari - The atari frontend is built for m68k and coldfire variants
> using a variant of the netsurf cross compliation
> toolchain/sdk. No serious updates have been made to this
> toolchain in some time and it has become a burden.
>
> Unless this is addressed before the next developer weekend the
> frontend will be disabled in the CI and subsequently code
> removed.
>

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

I've now uploaded the latest GCC 4.7.4 release 3 using the files create using the

Jenkins build:

http://ci.riscos.info/job/gcc-4.7-native/128/

 

The packaging indices will not get updated until tonight so there is likely to be

a problem downloading the packages until tomorrow.

 

I'll check the packages again from the uploads tomorrow.

 

Also note that package versions haven't been updated, so you will

need to uninstall the current GCC, clear the PackMan cache and

update the lists before trying to reinstall if you have already downloaded

release 3.

 

The only difference between the last version and this should be that

gcc –version gives the correct release number.

 

If all goes well I'll look to update the wiki and post an announcement

later this week.

 

Regards,

Alan

Tuesday, 7 February 2017

Re: [gccsdk] Problem with autobuilder (newbie questions)

In article <0ffe5f0a56.Matthew@sinenomine.freeserve.co.uk>,
Matthew Phillips <spam2011m@yahoo.co.uk> wrote:

> I then managed to update my autobuilder installation to pick up your new
> commits relating to gpsbabel

> I tried running

> cd ~/gccsdk/build
> ../autobuilder/build -v gpsbabel

> It starts by trying Qt5Base, but this fails, and if I grep the last-failure
> file for "error" case insensitively I get these lines at the end:

> /home/matthew/gccsdk/cross/lib/gcc/arm-unknown-riscos/4.7.4/../../../../arm-unknown-riscos/bin/ld: error: /home/matthew/gccsdk/env/lib/libQt5PlatformSupport.a(qgenericunixeventdispatcher.o) uses FPA instructions, whereas libqminimal.so does not
> /home/matthew/gccsdk/cross/lib/gcc/arm-unknown-riscos/4.7.4/../../../../arm-unknown-riscos/bin/ld: error: /home/matthew/gccsdk/env/lib/libQt5PlatformSupport.a(qunixeventdispatcher.o) uses FPA instructions, whereas libqminimal.so does not
> collect2: error: ld returned 1 exit status
> make[4]: *** [../../../../plugins/platforms/libqminimal.so] Error 1
> make[3]: *** [sub-minimal-make_first] Error 2
> make[2]: *** [sub-platforms-make_first] Error 2
> make[1]: *** [sub-plugins-make_first] Error 2
> make: *** [sub-src-make_first] Error 2

> Do you have any further suggestions? It looks like a build incompatibility
> between a couple of components to do with the floating point.

I'm not sure what the problem could be but if you haven't done so already
change the setvars file for Qt5Base from.

BUILD_NORMAL=yes
BUILD_VFP=yes

to

BUILD_NORMAL=yes
BUILD_VFP=no

At the moment gpsbabel only needs the normal build of Qt5Base. Also ensure
that RO_SHAREDLIBS=yes is set in build-setvars.


_______________________________________________
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: Frontend maintainership

Hi,

On 06/02/2017 12:25, Vincent Sanders wrote:
> atari - The atari frontend is built for m68k and coldfire variants
> using a variant of the netsurf cross compliation
> toolchain/sdk. No serious updates have been made to this
> toolchain in some time and it has become a burden.
>
> Unless this is addressed before the next developer weekend the
> frontend will be disabled in the CI and subsequently code
> removed.

I'll forward to the atari forums I know.

> windows - Lacks a full maintainer but has been fixed up to be at least
> useful. A maintainer for this frontend would be welcome.

I'd ask the ReactOS devs, maybe someone would be interested.
I just asked on their IRC channel.

> beos - The Beos port is generally only tested on Haiku at this
> point. The frontend is kept useful by mmu man and
> pulkomandy. Main issues revolve around the CI slave and its
> crashy java port.

FWIW, I was probably one of the last 10 BeOS users and I moved to Haiku
some years ago already. We should just rename the folder.


> gtk - Vince looks after this and despite gtk+ changing API a lot it
> remains useful.

Move to Qt? :D

François.

Monday, 6 February 2017

Re: [gccsdk] Problem with autobuilder (newbie questions)

In message <5605f55f4echrisg@care4free.net>
on 29 Jan 2017 Chris Gransden wrote:

> In article <399fb40556.Matthew@sinenomine.freeserve.co.uk>,
> Matthew Phillips <spam2011m@yahoo.co.uk> wrote:
>
> > $ cd build
> > $ ../autobuilder/build -v wget
>
> > as instructed. As with gpsbabel the first thing it tries to do is fetch
> > and compile native-zip. Again, after doing the patching, make starts and
> > we get the same errors as before:

[snip]

> native-zip should be getting built by the host compiler but instead it
> looks like the autobuilder installed compiler is being used.
> Have you set any envionment variables? Does echo $CC output anything.
> Are any of the autobuilder folders in your PATH? e.g.
> /home/matthew/gccsdk/env.

Again, it was a result of my being stupid. I had been reading a posting on
the ROOL forum in which someone sought advice on getting started with GCCSDK
(see https://www.riscosopen.org/forum/forums/11/topics/6289 ) and the fifth
posting, from Jeffrey Lee, suggested doing:

cd path/to/gccsdk
source env/ro-path

The second time I was vaguely aware this was not necessary but had run it to
check what needed to go in build-setvars and stupidly used the same shell for
the next steps.

Anyway, with a fresh shell I have now tried:

cd ~/gccsdk/build
../autobuilder/build -v wget

I get a report which concludes with:

Package wget: Success

This looks quite promising. I tried to locate the compiled wget, but when I
looked in ./gccsdk/autobuilder/network/wget there was a !Wget but nothing
executable in it. Using the Unix find command did not locate it.

I have now found in ./gccsdk/autobuilder/autobuilder_packages/Network that a
new wget_1.18-2.zip had been created and inside Apps.Network.!Wget there is a
wget executable. So I think everything is OK.

I then managed to update my autobuilder installation to pick up your new
commits relating to gpsbabel

I tried running

cd ~/gccsdk/build
../autobuilder/build -v gpsbabel

It starts by trying Qt5Base, but this fails, and if I grep the last-failure
file for "error" case insensitively I get these lines at the end:

/home/matthew/gccsdk/cross/lib/gcc/arm-unknown-riscos/4.7.4/../../../../arm-unknown-riscos/bin/ld: error: /home/matthew/gccsdk/env/lib/libQt5PlatformSupport.a(qgenericunixeventdispatcher.o) uses FPA instructions, whereas libqminimal.so does not
/home/matthew/gccsdk/cross/lib/gcc/arm-unknown-riscos/4.7.4/../../../../arm-unknown-riscos/bin/ld: error: /home/matthew/gccsdk/env/lib/libQt5PlatformSupport.a(qunixeventdispatcher.o) uses FPA instructions, whereas libqminimal.so does not
collect2: error: ld returned 1 exit status
make[4]: *** [../../../../plugins/platforms/libqminimal.so] Error 1
make[3]: *** [sub-minimal-make_first] Error 2
make[2]: *** [sub-platforms-make_first] Error 2
make[1]: *** [sub-plugins-make_first] Error 2
make: *** [sub-src-make_first] Error 2


Do you have any further suggestions? It looks like a build incompatibility
between a couple of components to do with the floating point.

> You can download gpsbabel from
> http://www.riscosports.co.uk/gpsbabel_1.5.3-1.zip. It also depends on
> Qt5Base being installed. If you use PackMan to install it the rest of the
> dependencies will be installed as well.

I've installed this successfully and tried converting a file. It seems to
work, but one of the points ended up with a latitude of "nan" rather than a
number, and that caused RiscOSM to crash when loading it. (Obviously we need
to make RiscOSM more robust in case this happens.)

Not sure why this happened: a version of the file supplied to us converted by
the online gpsbabel web site was identical for all the other 4213 lines in
the file, but has a sensible number for the latitude for this point.

So, almost perfect!

--
Matthew Phillips
Durham

_______________________________________________
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

Frontend maintainership

At the recent NetSurf developer weekend[1] we discussed many topics
one of which was our regular review of the frontends.

Except for Amiga and GTK none of the frontends have a active maintainer.

The cocoa and atari frontends are however causing a great deal of concern.

cocoa - Unless a maintainer can be found (or at least someone willing
to fix it) before 11th Febuarary 2017 the CI for this target
will be disabled. The code will be removed during the next
developer weekend on the 10th June.

This decision has been made because the effort to keep this
frontend building is large and we have many reports that the
resulting binary simply crashes when started.

atari - The atari frontend is built for m68k and coldfire variants
using a variant of the netsurf cross compliation
toolchain/sdk. No serious updates have been made to this
toolchain in some time and it has become a burden.

Unless this is addressed before the next developer weekend the
frontend will be disabled in the CI and subsequently code
removed.

riscos - Still lacks a full time maintainer but due to its userbase
the team keeps it working. Gets a reprieve again and will be
reconsidered next time.

windows - Lacks a full maintainer but has been fixed up to be at least
useful. A maintainer for this frontend would be welcome.

amiga - Chris Young continues to provide excellent maintainership no
problems noted.

monkey - test frontend is useful and we envisage expanding the scope
of its usage.

beos - The Beos port is generally only tested on Haiku at this
point. The frontend is kept useful by mmu man and
pulkomandy. Main issues revolve around the CI slave and its
crashy java port.

gtk - Vince looks after this and despite gtk+ changing API a lot it
remains useful.

framebuffer - generally good shape but the Linux framebuffer and input
need attention. It has been agreed we will look into
using libinput to improve this area.

[1] http://wiki.netsurf-browser.org/developer-weekend/feb-2017/

--
Regards Vincent
http://www.kyllikki.org/

Sunday, 5 February 2017

w3 schools

I just had a quick look at w3 schools and noticed that the
left-hand code pane is rendered too small.

The right-hand pane isn't shown at all, it's an iframecontainer.

http://www.w3schools.com/jsref/tryit.asp?filename=try_dom_event_target

This is in the Atari build 3978.

Is it the same for other builds ?

Peter

Saturday, 4 February 2017

Re: [gccsdk] abi-1/0 and abi-2/0

On 04/02/17 11:55, Gavin Wraith wrote:
> In $.!Boot.Resources.!SharedLibs.lib I have directories
> abi-1/0 and abi-2/0. Am I right in suspecting that the
> latter replaces the former and that only applications compiled
> before a certain date will be need what is in abi-1/0?
>
> I have not dared to try renaming abi-1/0 to see what fails.
> If nothing does, can I safely delete it?

abi-1/0 is for libraries compiled with GCC 4.1.2. When we changed
to a newer version of GCC (then 4.6, now 4.7), I came up with a
better PIC layout that was incompatible with the previous version.
So GCC 4.7 uses abi-2/0. If you don't use GCC 4.1.2 or any programs
compiled with it, then you don't need abi-1/0.

I think it best to think of GCC 4.1.2 as obsolete.

Lee.


_______________________________________________
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

[gccsdk] abi-1/0 and abi-2/0

In $.!Boot.Resources.!SharedLibs.lib I have directories
abi-1/0 and abi-2/0. Am I right in suspecting that the
latter replaces the former and that only applications compiled
before a certain date will be need what is in abi-1/0?

I have not dared to try renaming abi-1/0 to see what fails.
If nothing does, can I safely delete it?

--
Gavin Wraith (gavin@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/

_______________________________________________
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

Friday, 3 February 2017

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

On Fri, Feb 03, 2017 at 08:54:38AM +0000, alan buckley wrote:
> 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.

No problem, that's what it's for. I'm happy to give access to anyone else
who wants to push or tweak builds too.

(slightly annoyingly it's decided to run on 'bivalve', which is a slow Atom,
while ab-slave-1 is a fast Xeon - evidently the load balancing needs
tweaking)

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] GCCSDK buglist inaccessible

On 03/02/17 09:23, Duncan Moore wrote:
> 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?

Theo had to disable it temporarily due to spam.

Lee.


_______________________________________________
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

[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