Hi all,
Note that I will make a presentation on the Linux Framebuffer
(Graphics devroom) in which NetSurf will be mentionned (mainly on
libnsfb part).
For sure, a dedicated presentation about NetSurf would be really interesting!
Nicolas Caramelli
Le mar. 26 nov. 2019 à 16:28, François Revol <revol@free.fr> a écrit :
>
> Hi,
>
> it would be cool to have a NS talk this year at FOSDEM…
>
> François.
>
>
> -------- Message transféré --------
> Sujet : [retrocomputing devroom] FOSDEM 2020 - Retrocomputing DevRoom
> Call for Participation
> Date : Sun, 27 Oct 2019 23:48:33 +0100
> De : Pau Garcia Quiles <pgquiles@elpauer.org>
> Pour : retrocomputing-devroom@lists.fosdem.org
>
> Hello,
>
> FOSDEM is a free software event that offers open source communities a
> place to meet, share ideas and collaborate. It is renowned for being
> highly developer-oriented and brings together 8000+ participants from
> all over the world. It is held in the city of Brussels (Belgium).
>
> FOSDEM 2020 will take place during the weekend of February 1st-2nd
> 2020. More details about the event can be found at
> http://www.fosdem.org.
>
>
> CALL FOR PARTICIPATION
>
> After success in the past two years, the Retrocomputing DevRoom will
> be back in 2020, with talks about usage of older computing hardware
> and software in modern times.
>
> Presentation topics could include but are not limited to:
> - Emulation of old systems to run videogames, legacy software, etc
> - New software, hardware or related to be used with classic systems
> - Open source software emulation/simulation
> - Open hardware
> - Operating systems/executives for retrocomputers/retrosystems
> - Uses of retrocomputing today
> - Other retrosystems topics
> - Opportunities in retrocomputing
>
> You are not limited to slide presentations, of course. Be creative.
>
> However, FOSDEM is an open source conference, therefore we ask you to
> stay clear of marketing presentations. We are not afraid of technical
> stuff: devrooms are a place for development teams to meet, discuss,
> hack and publicly present their project's latest improvements and
> future directions.
>
> If you will have special needs for your talk (e. g. because you will
> need to plug some sort of a system, you need sound, etc), please note
> that clearly in your proposal so that we can provide it.
>
> You can use the Wikipedia definition of retrocomputing as a reference
> definition to see if you talk qualifies, although it is not exclusive:
> https://en.wikipedia.org/wiki/Retrocomputing
>
>
> IMPORTANT DATES
> - 30 November 2019: submission deadline for talk proposals
> - 14 December 2019: announcement of the final schedule
> - 1 February 2020: Retrocomputing DevRoom
>
>
> USEFUL INFORMATION
>
> Use the FOSDEM Pentabarf tool to submit your proposal:
> https://penta.fosdem.org/submission/FOSDEM20
>
> - If necessary, create a Pentabarf account and activate it. Please
> reuse your account from previous years if you have already created it.
> - In the "Person" section, provide First name, Last name (in the
> "General" tab), Email (in the "Contact" tab) and Bio ("Abstract" field
> in the "Description" tab).
> - Submit a proposal by clicking on "Create event".
> - Important! Select the "Retrocomputing DevRoom" track (on the
> "General" tab). If you do not select a track, then nobody, from any
> track, will look at your submission!
> - Provide the title of your talk ("Event title" in the "General" tab).
> - Provide a description of the subject of the talk and the intended
> audience (in the "Abstract" field of the "Description" tab)
> - Provide a rough outline of the talk or goals of the session (a short
> list of bullet points covering topics that will be discussed) in the
> "Full description" field in the "Description" tab
> - Provide an expected length of your talk in the "Duration" field,
> including discussion. The default duration is 30 minutes.
> - Slides are NOT required at the moment of submission
>
> Please note neither FOSDEM nor the Retrocomputing DevRoom will
> reimburse any expenses you incur.
>
>
> RECORDING OF TALKS
>
> The FOSDEM organizers plan to have live streaming and recording fully
> working, both for remote/later viewing of talks, and so that people
> can watch streams in the hallways when rooms are full. This requires
> speakers to consent to being recorded and streamed.
>
> If you plan to be a speaker, please understand that by doing so you
> implicitly give consent for your talk to be recorded and streamed. The
> recordings will be published under the same license as all FOSDEM
> content (CC-BY).
>
> Hope to hear from you soon! And please forward this announcement.
>
>
> CONTACT
>
> The Retrocomputing DevRoom is managed by Pau Garcia Quiles and
> François Revol (retro-devroom-manager@fosdem.org).
>
> A mailing list of speakers, audience and the curious is available,
> please subscribe at:
> https://lists.fosdem.org/listinfo/retrocomputing-devroom
>
>
> --
> Pau Garcia Quiles
> http://www.elpauer.org
> _______________________________________________
> retrocomputing-devroom mailing list
> retrocomputing-devroom@lists.fosdem.org
> https://lists.fosdem.org/listinfo/retrocomputing-devroom
>
Saturday, 30 November 2019
Wednesday, 27 November 2019
[Rpcemu] Re my request for help compiling RPCemu 0.9.2
Hi all,
I have solved the problem, I downloaded the source code again and started afresh, it seems that there was a error created by me when I extracted the source.
With the newly downloaded source file duly extracted, and a suitable ROM image filed in the correct directory the source compiled correctly
and I now have a fully functioning RISC OS 5 emulation running sweetly on my MX-Linux desktop.
Thanks for the advice,
John
Primary: johnmcculloch1<@>gmail.com
As Last Resort: johnmcculloch1956<@>outlook.com
Windows 10, Linux MX 17.1 and Android 8.1.0
Remove < > to use!!!!
As Last Resort: johnmcculloch1956<@>outlook.com
Windows 10, Linux MX 17.1 and Android 8.1.0
Remove < > to use!!!!
Tuesday, 26 November 2019
Fwd: [retrocomputing devroom] FOSDEM 2020 - Retrocomputing DevRoom Call for Participation
Hi,
it would be cool to have a NS talk this year at FOSDEM…
François.
-------- Message transféré --------
Sujet : [retrocomputing devroom] FOSDEM 2020 - Retrocomputing DevRoom
Call for Participation
Date : Sun, 27 Oct 2019 23:48:33 +0100
De : Pau Garcia Quiles <pgquiles@elpauer.org>
Pour : retrocomputing-devroom@lists.fosdem.org
Hello,
FOSDEM is a free software event that offers open source communities a
place to meet, share ideas and collaborate. It is renowned for being
highly developer-oriented and brings together 8000+ participants from
all over the world. It is held in the city of Brussels (Belgium).
FOSDEM 2020 will take place during the weekend of February 1st-2nd
2020. More details about the event can be found at
http://www.fosdem.org.
CALL FOR PARTICIPATION
After success in the past two years, the Retrocomputing DevRoom will
be back in 2020, with talks about usage of older computing hardware
and software in modern times.
Presentation topics could include but are not limited to:
- Emulation of old systems to run videogames, legacy software, etc
- New software, hardware or related to be used with classic systems
- Open source software emulation/simulation
- Open hardware
- Operating systems/executives for retrocomputers/retrosystems
- Uses of retrocomputing today
- Other retrosystems topics
- Opportunities in retrocomputing
You are not limited to slide presentations, of course. Be creative.
However, FOSDEM is an open source conference, therefore we ask you to
stay clear of marketing presentations. We are not afraid of technical
stuff: devrooms are a place for development teams to meet, discuss,
hack and publicly present their project's latest improvements and
future directions.
If you will have special needs for your talk (e. g. because you will
need to plug some sort of a system, you need sound, etc), please note
that clearly in your proposal so that we can provide it.
You can use the Wikipedia definition of retrocomputing as a reference
definition to see if you talk qualifies, although it is not exclusive:
https://en.wikipedia.org/wiki/Retrocomputing
IMPORTANT DATES
- 30 November 2019: submission deadline for talk proposals
- 14 December 2019: announcement of the final schedule
- 1 February 2020: Retrocomputing DevRoom
USEFUL INFORMATION
Use the FOSDEM Pentabarf tool to submit your proposal:
https://penta.fosdem.org/submission/FOSDEM20
- If necessary, create a Pentabarf account and activate it. Please
reuse your account from previous years if you have already created it.
- In the "Person" section, provide First name, Last name (in the
"General" tab), Email (in the "Contact" tab) and Bio ("Abstract" field
in the "Description" tab).
- Submit a proposal by clicking on "Create event".
- Important! Select the "Retrocomputing DevRoom" track (on the
"General" tab). If you do not select a track, then nobody, from any
track, will look at your submission!
- Provide the title of your talk ("Event title" in the "General" tab).
- Provide a description of the subject of the talk and the intended
audience (in the "Abstract" field of the "Description" tab)
- Provide a rough outline of the talk or goals of the session (a short
list of bullet points covering topics that will be discussed) in the
"Full description" field in the "Description" tab
- Provide an expected length of your talk in the "Duration" field,
including discussion. The default duration is 30 minutes.
- Slides are NOT required at the moment of submission
Please note neither FOSDEM nor the Retrocomputing DevRoom will
reimburse any expenses you incur.
RECORDING OF TALKS
The FOSDEM organizers plan to have live streaming and recording fully
working, both for remote/later viewing of talks, and so that people
can watch streams in the hallways when rooms are full. This requires
speakers to consent to being recorded and streamed.
If you plan to be a speaker, please understand that by doing so you
implicitly give consent for your talk to be recorded and streamed. The
recordings will be published under the same license as all FOSDEM
content (CC-BY).
Hope to hear from you soon! And please forward this announcement.
CONTACT
The Retrocomputing DevRoom is managed by Pau Garcia Quiles and
François Revol (retro-devroom-manager@fosdem.org).
A mailing list of speakers, audience and the curious is available,
please subscribe at:
https://lists.fosdem.org/listinfo/retrocomputing-devroom
--
Pau Garcia Quiles
http://www.elpauer.org
_______________________________________________
retrocomputing-devroom mailing list
retrocomputing-devroom@lists.fosdem.org
https://lists.fosdem.org/listinfo/retrocomputing-devroom
it would be cool to have a NS talk this year at FOSDEM…
François.
-------- Message transféré --------
Sujet : [retrocomputing devroom] FOSDEM 2020 - Retrocomputing DevRoom
Call for Participation
Date : Sun, 27 Oct 2019 23:48:33 +0100
De : Pau Garcia Quiles <pgquiles@elpauer.org>
Pour : retrocomputing-devroom@lists.fosdem.org
Hello,
FOSDEM is a free software event that offers open source communities a
place to meet, share ideas and collaborate. It is renowned for being
highly developer-oriented and brings together 8000+ participants from
all over the world. It is held in the city of Brussels (Belgium).
FOSDEM 2020 will take place during the weekend of February 1st-2nd
2020. More details about the event can be found at
http://www.fosdem.org.
CALL FOR PARTICIPATION
After success in the past two years, the Retrocomputing DevRoom will
be back in 2020, with talks about usage of older computing hardware
and software in modern times.
Presentation topics could include but are not limited to:
- Emulation of old systems to run videogames, legacy software, etc
- New software, hardware or related to be used with classic systems
- Open source software emulation/simulation
- Open hardware
- Operating systems/executives for retrocomputers/retrosystems
- Uses of retrocomputing today
- Other retrosystems topics
- Opportunities in retrocomputing
You are not limited to slide presentations, of course. Be creative.
However, FOSDEM is an open source conference, therefore we ask you to
stay clear of marketing presentations. We are not afraid of technical
stuff: devrooms are a place for development teams to meet, discuss,
hack and publicly present their project's latest improvements and
future directions.
If you will have special needs for your talk (e. g. because you will
need to plug some sort of a system, you need sound, etc), please note
that clearly in your proposal so that we can provide it.
You can use the Wikipedia definition of retrocomputing as a reference
definition to see if you talk qualifies, although it is not exclusive:
https://en.wikipedia.org/wiki/Retrocomputing
IMPORTANT DATES
- 30 November 2019: submission deadline for talk proposals
- 14 December 2019: announcement of the final schedule
- 1 February 2020: Retrocomputing DevRoom
USEFUL INFORMATION
Use the FOSDEM Pentabarf tool to submit your proposal:
https://penta.fosdem.org/submission/FOSDEM20
- If necessary, create a Pentabarf account and activate it. Please
reuse your account from previous years if you have already created it.
- In the "Person" section, provide First name, Last name (in the
"General" tab), Email (in the "Contact" tab) and Bio ("Abstract" field
in the "Description" tab).
- Submit a proposal by clicking on "Create event".
- Important! Select the "Retrocomputing DevRoom" track (on the
"General" tab). If you do not select a track, then nobody, from any
track, will look at your submission!
- Provide the title of your talk ("Event title" in the "General" tab).
- Provide a description of the subject of the talk and the intended
audience (in the "Abstract" field of the "Description" tab)
- Provide a rough outline of the talk or goals of the session (a short
list of bullet points covering topics that will be discussed) in the
"Full description" field in the "Description" tab
- Provide an expected length of your talk in the "Duration" field,
including discussion. The default duration is 30 minutes.
- Slides are NOT required at the moment of submission
Please note neither FOSDEM nor the Retrocomputing DevRoom will
reimburse any expenses you incur.
RECORDING OF TALKS
The FOSDEM organizers plan to have live streaming and recording fully
working, both for remote/later viewing of talks, and so that people
can watch streams in the hallways when rooms are full. This requires
speakers to consent to being recorded and streamed.
If you plan to be a speaker, please understand that by doing so you
implicitly give consent for your talk to be recorded and streamed. The
recordings will be published under the same license as all FOSDEM
content (CC-BY).
Hope to hear from you soon! And please forward this announcement.
CONTACT
The Retrocomputing DevRoom is managed by Pau Garcia Quiles and
François Revol (retro-devroom-manager@fosdem.org).
A mailing list of speakers, audience and the curious is available,
please subscribe at:
https://lists.fosdem.org/listinfo/retrocomputing-devroom
--
Pau Garcia Quiles
http://www.elpauer.org
_______________________________________________
retrocomputing-devroom mailing list
retrocomputing-devroom@lists.fosdem.org
https://lists.fosdem.org/listinfo/retrocomputing-devroom
Re: [gccsdk] FILE structure
Hi Ronald,
> In trying to implement wget's own support lib there was a requirement
> for an implementation of freading().
Here's glibc's description. https://manned.org/__freading.3
> It looks like some extra system flag would need to be set on every
> read, and negated on a write.
That may be needed anyway as a side effect of tracking a buffer's state,
e.g.
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;a=blob;f=newlib/libc/stdio/refill.c;h=87a715b848b0009624f3fc76d938ef49a35bc282;hb=HEAD#l33
--
Cheers, Ralph.
_______________________________________________
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
> In trying to implement wget's own support lib there was a requirement
> for an implementation of freading().
Here's glibc's description. https://manned.org/__freading.3
> It looks like some extra system flag would need to be set on every
> read, and negated on a write.
That may be needed anyway as a side effect of tracking a buffer's state,
e.g.
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;a=blob;f=newlib/libc/stdio/refill.c;h=87a715b848b0009624f3fc76d938ef49a35bc282;hb=HEAD#l33
--
Cheers, Ralph.
_______________________________________________
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
Tuesday, 19 November 2019
Re: [Rpcemu] Help rpcemu-0.9.2
In article <CAF9eEQEPrJyc_NVgGQk0XONW6TqnjK4so-kPoz_cTrr6axB0Bg@mail.gmail.com>,
John McCulloch <johnmcculloch1@gmail.com> wrote:
> So I have tried to do the same on my HP G56 64bit laptop, running 64bit
> MX-Linux 19.1, have installed the source to the same location on my hard
> drive, but when I try to compile the source, an error occurs when I run the
> ./buildit.sh command in my terminal.
> /home/JohnMcCulloch/rpcemu-0.9.2/src/qt5/rpcemu.pro:3: Assignment needs
> exactly one word on the left hand side.
Check line 3 in /home/JohnMcCulloch/rpcemu-0.9.2/src/qt5/rpcemu.pro. It
should look like this:
CONFIG += debug_and_release
or this:
CONFIG += debug_and_release dynarec
The error message indicates there's something more (or less) than the
variable name CONFIG before the +=.
Regards,
Frank
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
John McCulloch <johnmcculloch1@gmail.com> wrote:
> So I have tried to do the same on my HP G56 64bit laptop, running 64bit
> MX-Linux 19.1, have installed the source to the same location on my hard
> drive, but when I try to compile the source, an error occurs when I run the
> ./buildit.sh command in my terminal.
> /home/JohnMcCulloch/rpcemu-0.9.2/src/qt5/rpcemu.pro:3: Assignment needs
> exactly one word on the left hand side.
Check line 3 in /home/JohnMcCulloch/rpcemu-0.9.2/src/qt5/rpcemu.pro. It
should look like this:
CONFIG += debug_and_release
or this:
CONFIG += debug_and_release dynarec
The error message indicates there's something more (or less) than the
variable name CONFIG before the +=.
Regards,
Frank
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[Rpcemu] Help rpcemu-0.9.2
Hi there,
I have successfully downloaded the Source for 0.9.2 to my Dell Latitude 32bit laptop, and compiled
it on my 32bit MX-Linux v18.3.
And it runs well with RISC OS 3.71.
So I have tried to do the same on my HP G56 64bit laptop, running 64bit MX-Linux 19.1, have installed the source to the same location on my hard drive, but when I try to compile the source, an error occurs when I run the ./buildit.sh command in my terminal.
/home/JohnMcCulloch/rpcemu-0.9.2/src/qt5/rpcemu.pro:3: Assignment needs
exactly one word on the left hand side.
Error processing project file:
/home/JohnMcCulloch/rpcemu-0.9.2/src/qt5/rpcemu.pro
exactly one word on the left hand side.
Error processing project file:
/home/JohnMcCulloch/rpcemu-0.9.2/src/qt5/rpcemu.pro
I cannot work out what is wrong.
Can someone help me please.
John
Primary: johnmcculloch1<@>gmail.com
As Last Resort: johnmcculloch1956<@>outlook.com
Windows 10, Linux MX 17.1 and Android 8.1.0
Remove < > to use!!!!
As Last Resort: johnmcculloch1956<@>outlook.com
Windows 10, Linux MX 17.1 and Android 8.1.0
Remove < > to use!!!!
Sunday, 10 November 2019
Re: [gccsdk] Native GCC 'hangs'
On 06/11/2019 12:05, Chris Johns wrote:
> Hi all
>
> I've found the GCC 4.7.4 compiler "hangs" while compiling some files
> when running natively. This is running RISC OS 5 under RPCEmu, but it
> also does it on an ARMBook. The gccsdk cross-compiler running on Linux
> compiles the same file fine.
>
> One example is Objects/longobject.c from Python 3.8.
>
> #if 0-ing out the PyLong_FromString function will actually let it
> compile the rest. It's a big function, so maybe I just need to wait
> longer? However I did leave it for >30 minutes the other day.
I recall that I've experienced apparent hangs when compiling code that
calls the log() function; I was able to work around it by passing
`-fno-builtin-log` on the command line.
--
James Harper
_______________________________________________
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
> Hi all
>
> I've found the GCC 4.7.4 compiler "hangs" while compiling some files
> when running natively. This is running RISC OS 5 under RPCEmu, but it
> also does it on an ARMBook. The gccsdk cross-compiler running on Linux
> compiles the same file fine.
>
> One example is Objects/longobject.c from Python 3.8.
>
> #if 0-ing out the PyLong_FromString function will actually let it
> compile the rest. It's a big function, so maybe I just need to wait
> longer? However I did leave it for >30 minutes the other day.
I recall that I've experienced apparent hangs when compiling code that
calls the log() function; I was able to work around it by passing
`-fno-builtin-log` on the command line.
--
James Harper
_______________________________________________
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
Saturday, 9 November 2019
Re: RISC OS CI#4886 - can't type reply
In message <202f3b0f58.DaveMeUK@BeagleBoard-xM> I wrote:
> Something appears to have gone wrong betweem the RISC OS CI versions 4885
> and 4886. I tried typing a reply in the ROOL site, but no keyboard input
> appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
>
> Can someone else please try this and let me know if you can reproduce it -
> if so, I will report it.
>
> I did update !Boot and !System.
The issue appears fixed in version 4891.
David
> Something appears to have gone wrong betweem the RISC OS CI versions 4885
> and 4886. I tried typing a reply in the ROOL site, but no keyboard input
> appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
>
> Can someone else please try this and let me know if you can reproduce it -
> if so, I will report it.
>
> I did update !Boot and !System.
The issue appears fixed in version 4891.
David
Friday, 8 November 2019
Re: RISC OS CI#4886 - can't type reply
Vincent Sanders wrote on 8 Nov:
> This was reported as issue
> https://bugs.netsurf-browser.org/mantis/view.php?id=2715
> I resolved the issue and should be fixed in 4890 and onwards
I loaded #4891 and re-tried the text-area thing I reported in this thread.
That problem too has now disappeared, though I'm not clear how they were
connected.
Thanks, Vincent.
--
Jim Nagel www.archivemag.co.uk
> This was reported as issue
> https://bugs.netsurf-browser.org/mantis/view.php?id=2715
> I resolved the issue and should be fixed in 4890 and onwards
I loaded #4891 and re-tried the text-area thing I reported in this thread.
That problem too has now disappeared, though I'm not clear how they were
connected.
Thanks, Vincent.
--
Jim Nagel www.archivemag.co.uk
Re: RISC OS CI#4886 - can't type reply
On Thu, Nov 07, 2019 at 02:43:09PM +0000, David Higton wrote:
> Something appears to have gone wrong betweem the RISC OS CI versions 4885
> and 4886. I tried typing a reply in the ROOL site, but no keyboard input
> appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
>
> Can someone else please try this and let me know if you can reproduce it
> - if so, I will report it.
>
> I did update !Boot and !System.
>
> David
>
>
This was reported as issue https://bugs.netsurf-browser.org/mantis/view.php?id=2715
I resolved the issue and should be fixed in 4890 and onwards
--
Regards Vincent
http://www.kyllikki.org/
> Something appears to have gone wrong betweem the RISC OS CI versions 4885
> and 4886. I tried typing a reply in the ROOL site, but no keyboard input
> appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
>
> Can someone else please try this and let me know if you can reproduce it
> - if so, I will report it.
>
> I did update !Boot and !System.
>
> David
>
>
This was reported as issue https://bugs.netsurf-browser.org/mantis/view.php?id=2715
I resolved the issue and should be fixed in 4890 and onwards
--
Regards Vincent
http://www.kyllikki.org/
Re: RISC OS CI#4886 - can't type reply
David Higton wrote on 7 Nov:
> Something appears to have gone wrong betweem the RISC OS CI versions 4885
> and 4886. I tried typing a reply in the ROOL site, but no keyboard input
> appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
> Can someone else please try this and let me know if you can reproduce it
> - if so, I will report it.
I was using #4887 earlier today and found that none of the controls for a
text area would work (Ctrl-A, Ctrl-C, Ctrl-X etc).
Went back to my previous version, #4881, and all is well.
--
Jim Nagel www.archivemag.co.uk
> Something appears to have gone wrong betweem the RISC OS CI versions 4885
> and 4886. I tried typing a reply in the ROOL site, but no keyboard input
> appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
> Can someone else please try this and let me know if you can reproduce it
> - if so, I will report it.
I was using #4887 earlier today and found that none of the controls for a
text area would work (Ctrl-A, Ctrl-C, Ctrl-X etc).
Went back to my previous version, #4881, and all is well.
--
Jim Nagel www.archivemag.co.uk
Thursday, 7 November 2019
Re: "Warning from Netsurf: Unknown"
On , netsurf-users-request@netsurf-browser.org wrote:
> Date: Mon, 04 Nov 2019 13:40:25 +0000 (GMT)
> From: "Richard Torrens (lists)" <Lists@Torrens.org>
> Subject: Re: "Warning from Netsurf: Unknown"
> To: netsurf-users@netsurf-browser.org
> Message-ID: <580da9eeabLists@Torrens.org>
> In article <20191104112318.oax3l5xs43fqrmzq@kyllikki.org>,
> Vincent Sanders <vince@netsurf-browser.org> wrote:
> > I have changed how all network errors are reported to be a proper
> > error page instead of a popup. please can those affected (using CI
> > builds) confirm that the new behaviour is more informative and works
> > for them.
>
> Nice one!
>
> Yes, the error "Couldn't resolve host name" is reported nicely.
>
I was worried that these error pages might be very slow on an
Atari (68060) but they aren't.
Although "FetchErrorTitle" is a little confusing:
-
FetchErrorTitle
An error occurred when connecting to www.45jgf945hf0.omv
Couldn't resolve host name
-
Peter
> Date: Mon, 04 Nov 2019 13:40:25 +0000 (GMT)
> From: "Richard Torrens (lists)" <Lists@Torrens.org>
> Subject: Re: "Warning from Netsurf: Unknown"
> To: netsurf-users@netsurf-browser.org
> Message-ID: <580da9eeabLists@Torrens.org>
> In article <20191104112318.oax3l5xs43fqrmzq@kyllikki.org>,
> Vincent Sanders <vince@netsurf-browser.org> wrote:
> > I have changed how all network errors are reported to be a proper
> > error page instead of a popup. please can those affected (using CI
> > builds) confirm that the new behaviour is more informative and works
> > for them.
>
> Nice one!
>
> Yes, the error "Couldn't resolve host name" is reported nicely.
>
I was worried that these error pages might be very slow on an
Atari (68060) but they aren't.
Although "FetchErrorTitle" is a little confusing:
-
FetchErrorTitle
An error occurred when connecting to www.45jgf945hf0.omv
Couldn't resolve host name
-
Peter
RISC OS CI#4886 - can't type reply
Something appears to have gone wrong betweem the RISC OS CI versions 4885
and 4886. I tried typing a reply in the ROOL site, but no keyboard input
appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
Can someone else please try this and let me know if you can reproduce it
- if so, I will report it.
I did update !Boot and !System.
David
and 4886. I tried typing a reply in the ROOL site, but no keyboard input
appeared. The same is true for for 4886 and 4887, but 4885 is OK for me.
Can someone else please try this and let me know if you can reproduce it
- if so, I will report it.
I did update !Boot and !System.
David
page refresh -- still a problem
This problem again (using Netsurf #4881 on ArmX6 OS 5.25). See threads in
this list dated 2016-may-03 (when #4088 was in use) and 2018-july-13.
Did some further updates on the Archive site today, and again came up
against the old fails-to-reload problem. None of these do the trick:
F5 or ^F5 or ^R or the buttonbar route or Adjust-click on the
buttonbar or ^buttonbar or Netsurf menu "Navigate > Reload this
page".
The old page always reappears.
Tried quitting and restarting Netsurf, still no joy.
Before anybody asks: the site does not use frames.
I guess the item will have to be cleared from my local cache. Is there a
straightforward way of doing this that I don't know about? Iconbar
"Choices > Cache" does not offer one.
Seems to me the "Reload this page" option ain't strong enuf.
--
Jim Nagel www.archivemag.co.uk
this list dated 2016-may-03 (when #4088 was in use) and 2018-july-13.
Did some further updates on the Archive site today, and again came up
against the old fails-to-reload problem. None of these do the trick:
F5 or ^F5 or ^R or the buttonbar route or Adjust-click on the
buttonbar or ^buttonbar or Netsurf menu "Navigate > Reload this
page".
The old page always reappears.
Tried quitting and restarting Netsurf, still no joy.
Before anybody asks: the site does not use frames.
I guess the item will have to be cleared from my local cache. Is there a
straightforward way of doing this that I don't know about? Iconbar
"Choices > Cache" does not offer one.
Seems to me the "Reload this page" option ain't strong enuf.
--
Jim Nagel www.archivemag.co.uk
Wednesday, 6 November 2019
[gccsdk] Native GCC 'hangs'
Hi all
I've found the GCC 4.7.4 compiler "hangs" while compiling some files
when running natively. This is running RISC OS 5 under RPCEmu, but it
also does it on an ARMBook. The gccsdk cross-compiler running on Linux
compiles the same file fine.
One example is Objects/longobject.c from Python 3.8.
#if 0-ing out the PyLong_FromString function will actually let it
compile the rest. It's a big function, so maybe I just need to wait
longer? However I did leave it for >30 minutes the other day.
Thanks
Chris
_______________________________________________
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
I've found the GCC 4.7.4 compiler "hangs" while compiling some files
when running natively. This is running RISC OS 5 under RPCEmu, but it
also does it on an ARMBook. The gccsdk cross-compiler running on Linux
compiles the same file fine.
One example is Objects/longobject.c from Python 3.8.
#if 0-ing out the PyLong_FromString function will actually let it
compile the rest. It's a big function, so maybe I just need to wait
longer? However I did leave it for >30 minutes the other day.
Thanks
Chris
_______________________________________________
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
Monday, 4 November 2019
Re: "Warning from Netsurf: Unknown"
Vincent Sanders wrote on 4 Nov:
> I have changed how all network errors are reported to be a proper error
> page instead of a popup. please can those affected (using CI builds)
> confirm that the new behaviour is more informative and works for them.
Thanks for that welcome change, Vincent. I downloaded and installed #4881
just now and tried the site that I first reported in this thread.
I now get a "Connection timed out" error page -- screenshot here :
http://archivemag.co.uk/TEMP/NS-timedout.png (45K)
But I'm not clear whether this page came from Netsurf or from the site
named in the URL bar of the page. If Netsurf, could I suggest that your
design say so? (Maybe just add a Netsurf logo.)
Anyway, it *is* more informative!
Cheers.
--
Jim Nagel www.archivemag.co.uk
> I have changed how all network errors are reported to be a proper error
> page instead of a popup. please can those affected (using CI builds)
> confirm that the new behaviour is more informative and works for them.
Thanks for that welcome change, Vincent. I downloaded and installed #4881
just now and tried the site that I first reported in this thread.
I now get a "Connection timed out" error page -- screenshot here :
http://archivemag.co.uk/TEMP/NS-timedout.png (45K)
But I'm not clear whether this page came from Netsurf or from the site
named in the URL bar of the page. If Netsurf, could I suggest that your
design say so? (Maybe just add a Netsurf logo.)
Anyway, it *is* more informative!
Cheers.
--
Jim Nagel www.archivemag.co.uk
Re: "Warning from Netsurf: Unknown"
On 4 Nov 2019 "Richard Torrens (lists)" <Lists@Torrens.org> wrote:
> In article <20191104112318.oax3l5xs43fqrmzq@kyllikki.org>,
> Vincent Sanders <vince@netsurf-browser.org> wrote:
>> I have changed how all network errors are reported to be a proper
>> error page instead of a popup. please can those affected (using CI
>> builds) confirm that the new behaviour is more informative and works
>> for them.
> Nice one!
> Yes, the error "Couldn't resolve host name" is reported nicely.
And here with CI 4881. Many thanks.
Best wishes,
Peter.
--
Peter Young (zfc Hg) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
> In article <20191104112318.oax3l5xs43fqrmzq@kyllikki.org>,
> Vincent Sanders <vince@netsurf-browser.org> wrote:
>> I have changed how all network errors are reported to be a proper
>> error page instead of a popup. please can those affected (using CI
>> builds) confirm that the new behaviour is more informative and works
>> for them.
> Nice one!
> Yes, the error "Couldn't resolve host name" is reported nicely.
And here with CI 4881. Many thanks.
Best wishes,
Peter.
--
Peter Young (zfc Hg) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
Re: [Rpcemu] Revised 0.9.2 patch for Mac
In message <1F04925E-AF93-4D6E-B193-42DBF6B30313@maemagel.com>
Timothy Coltman <lists@maemagel.com> wrote:
> Hello all
> Following on from my earlier posts, please find attached a revised
> patch for 0.9.2 that resolves the issue with dynamic recompilation. I
> have tested with 10.14.6 (Mojave) and 10.15.1 (Catalina) and it works
> in both.
Many thanks, it is working nicely here on Catalina 10.15.1 and very
welcome.
--
David Pitt
Titanium
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Timothy Coltman <lists@maemagel.com> wrote:
> Hello all
> Following on from my earlier posts, please find attached a revised
> patch for 0.9.2 that resolves the issue with dynamic recompilation. I
> have tested with 10.14.6 (Mojave) and 10.15.1 (Catalina) and it works
> in both.
Many thanks, it is working nicely here on Catalina 10.15.1 and very
welcome.
--
David Pitt
Titanium
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Re: "Warning from Netsurf: Unknown"
In article <20191104112318.oax3l5xs43fqrmzq@kyllikki.org>,
Vincent Sanders <vince@netsurf-browser.org> wrote:
> I have changed how all network errors are reported to be a proper
> error page instead of a popup. please can those affected (using CI
> builds) confirm that the new behaviour is more informative and works
> for them.
Nice one!
Yes, the error "Couldn't resolve host name" is reported nicely.
--
Richard Torrens.
http://www.Torrens.org for genealogy, natural history, wild food, walks, cats
and more!
Vincent Sanders <vince@netsurf-browser.org> wrote:
> I have changed how all network errors are reported to be a proper
> error page instead of a popup. please can those affected (using CI
> builds) confirm that the new behaviour is more informative and works
> for them.
Nice one!
Yes, the error "Couldn't resolve host name" is reported nicely.
--
Richard Torrens.
http://www.Torrens.org for genealogy, natural history, wild food, walks, cats
and more!
Re: "Warning from Netsurf: Unknown"
On Tue, Oct 22, 2019 at 01:21:26PM +0100, Richard Porter wrote:
> On 22 Oct 2019 David Pitt wrote:
>
> > It is on the bug tracker now. The example above is a very broken site,
> > neither Safari or Firefox get anywhere with it.
>
> I get the same response after a long wait.
>
I have changed how all network errors are reported to be a proper
error page instead of a popup. please can those affected (using CI
builds) confirm that the new behaviour is more informative and works
for them.
--
Regards Vincent
http://www.kyllikki.org/
> On 22 Oct 2019 David Pitt wrote:
>
> > It is on the bug tracker now. The example above is a very broken site,
> > neither Safari or Firefox get anywhere with it.
>
> I get the same response after a long wait.
>
I have changed how all network errors are reported to be a proper
error page instead of a popup. please can those affected (using CI
builds) confirm that the new behaviour is more informative and works
for them.
--
Regards Vincent
http://www.kyllikki.org/
Sunday, 3 November 2019
[Rpcemu] Revised 0.9.2 patch for Mac
Hello all
Following on from my earlier posts, please find attached a revised patch for 0.9.2 that resolves the issue with dynamic recompilation. I have tested with 10.14.6 (Mojave) and 10.15.1 (Catalina) and it works in both.
The compilation instructions are the same as before (see my email dated 27/10/2019).
Tim
Following on from my earlier posts, please find attached a revised patch for 0.9.2 that resolves the issue with dynamic recompilation. I have tested with 10.14.6 (Mojave) and 10.15.1 (Catalina) and it works in both.
The compilation instructions are the same as before (see my email dated 27/10/2019).
Tim
Subscribe to:
Posts (Atom)