Mailing Lists: April 2022

Tuesday, 26 April 2022

Re: Mantis

On 11 Apr 2022 as I do recall,
Harriet Bazley wrote:

> Is the Mantis bug reporter still working? I notice that no bugs have
> been confirmed/acknowledged since the start of the year, and the only
> notifications I've received from the site have been when somebody posts
> a spam link as a comment....
>

I'm still getting this sort of notification, but no sign of actual
activity:

> (0002361) Jerick Fischer (reporter) - 2022-02-18 11:49
> https://bugs.netsurf-browser.org/mantis/view.php?id=2831#c2361
> ----------------------------------------------------------------------
> This thread was really helpful.
> https://tsadiklaw.com/los-angeles-special-education/
>
> ----------------------------------------------------------------------
> (0002370) Faith SArim (reporter) - 2022-04-20 14:52
> https://bugs.netsurf-browser.org/mantis/view.php?id=2831#c2370
> ----------------------------------------------------------------------
> That is really nice to hear. thank you for the update and good luck.-
> http://pittsburghfoundationrepaircontractor.com/basement-waterproofing-pittsburgh-pennsylvania/
>
>
> ----------------------------------------------------------------------
> (0002379) Moth Cruz (reporter) - 2022-04-26 04:10
> https://bugs.netsurf-browser.org/mantis/view.php?id=2831#c2379
> ----------------------------------------------------------------------
> Any update about this? http://chicagofoundationrepairpro.com/

--
Harriet Bazley == Loyaulte me lie ==

C++ - the language in which only friends can access your private members
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Sunday, 24 April 2022

[gccsdk] beebasm build with GCCSDK won't run in as RISC OS 4.39 !Make task but will run in a task window.

I know this is completely indefensible, unnecessary and obtuse use case. I don't for one moment think it needs fixing, I post it here just as an observation of a peculiar behavior.

This will run perfectly in a task window but as a !Make_task it hangs. (!Make 1.27)

beebasm -I @.hostfs/txt -o @.hostfs/rom

Alan

Friday, 22 April 2022

Re: [gccsdk] GCCSDK 10 for older cores

Hi,

> Rob Kendrick <rjek@rjek.com> wrote:
[snip]
> Is building code for ARMv3 (or v4?) supported and I'm being an idiot, or
> is this totally out of scope of the endeavour?

No idea about the GCCSDK details, but from a GCC-ARM-backend perspective,
ARMv4 and everything-non-Thumb-before-ARMv6 was deprecated I think in
GCC 6, so I guess it was removed from the ARM backend in one of the
later versions.

Current GCC docs only mention "ARMv4T" support as the oldest
architecture. ISTR there was a linker hack to basically transform
ARMv4T output to ARMv4, but I cannot find the reference for that.

So unless you re-add the support to the ARM backend, I guess you
are out of luck and need to go back to GCC 4.7.x for old ARM
architecture compatibility.

Steffen

--
Steffen Huber LambdaComm System – Welcome to Trollinger Country
steffen@huber-net.de
Private homepage https://www.huber-net.de/ (http://www.huber-net.de/)
RISC OS Blog http://riscosblog.huber-net.de/

_______________________________________________
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 10 for older cores

Hi,

I was looking at building NetSurf with the current work-in-progress GCC
10 to see what sort of performance benefits we could see.

Sadly I can't get it to build in a way that it doesn't generate (or
think it has generated) code that requires ARMv7.

Is building code for ARMv3 (or v4?) supported and I'm being an idiot, or
is this totally out of scope of the endeavour?

I essentially did this to autobuilder/develop/gcc/setvars:

Index: setvars
===================================================================
--- setvars (revision 7692)
+++ setvars (working copy)
@@ -182,9 +182,8 @@
--with-pkgversion='GCCSDK GCC 10.2.0 Release 1' \
--with-bugurl=http://gccsdk.riscos.info/ \
--with-abi=aapcs-linux \
- --with-float=hard \
- --with-fpu=vfpv3 \
- --with-arch=armv7-a
+ --with-float=soft \
+ --with-arch=armv4

make -j4 && make install

@@ -215,9 +214,8 @@
--with-pkgversion='GCCSDK GCC 10.2.0 Release 1' \
--with-bugurl=http://gccsdk.riscos.info/ \
--with-abi=aapcs-linux \
- --with-float=hard \
- --with-fpu=vfpv3 \
- --with-arch=armv7-a \
+ --with-float=soft \
+ --with-arch=armv4 \
--with-stage1-ldflags="" \
--with-diagnostics-color=never

I also needed to hack elf2aif to ignore the headers:

ndex: src/elf2aif.c
===================================================================
--- src/elf2aif.c (revision 7692)
+++ src/elf2aif.c (working copy)
@@ -203,8 +203,8 @@

if (elf_ehdr.e_ident[EI_OSABI] != ELFOSABI_ARM)
{
- fprintf (stderr, "ELF file '%s' is not for ARM\n", elf_filename);
- return EXIT_FAILURE;
+ fprintf (stderr, "ELF file '%s' is not for ARM (OS ABI field is %d)\n", elf_filename, elf_ehdr.e_ident[EI_OSABI]);
+// return EXIT_FAILURE;
}

(GCCSDK 10 sets the OSABI field in the ELF to 0, meaning unspecified.)

Sadly the resulting binary still says the CPU is too old.

B.

_______________________________________________
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] A cert issue with www.mpfr.org broke build-world added --no-check-certificate to work around it.

On Fri, Apr 22, 2022 at 02:46:10PM +0930, Alan Williams wrote:
> I was just building GCCSDK on a new machines (Rocky Linux 8.5 on x86) and
> build-world complained about being unable to verify the cert for
> www.mpfr.org.

I've verified that on Ubuntu 21.10:

$ wget https://www.mpfr.org/mpfr-current/mpfr-4.1.0.tar.xz
--2022-04-22 08:53:23-- https://www.mpfr.org/mpfr-current/mpfr-4.1.0.tar.xz
Resolving www.mpfr.org (www.mpfr.org)... 128.93.162.51
Connecting to www.mpfr.org (www.mpfr.org)|128.93.162.51|:443... connected.
ERROR: cannot verify www.mpfr.org's certificate, issued by 'CN=GEANT OV RSA
CA 4,O=GEANT Vereniging,C=NL':
Unable to locally verify the issuer's authority.
To connect to www.mpfr.org insecurely, use `--no-check-certificate'.

and SSL Labs says that part of the certificate chain is incomplete:
https://www.ssllabs.com/ssltest/analyze.html?d=www.mpfr.org

There doesn't appear to be a contact address on the mpfr.org website, but
I've applied to join their mailing list so I can let them know.

Theo

Thursday, 21 April 2022

[gccsdk] A cert issue with www.mpfr.org broke build-world added --no-check-certificate to work around it.

I was just building GCCSDK on a new machines (Rocky Linux 8.5 on x86) and build-world complained about being unable to verify the cert for www.mpfr.org.

I added --no-check-certificate to the Makefile as shown below and building continued.

# Download mpfr source:

$(SRCORIGDIR)/mpfr-$(MPFR_VERSION).tar.bz2:

-mkdir -p $(SRCORIGDIR)

cd $(SRCORIGDIR) && wget --no-check-certificate -c https://www.mpfr.org/mpfr-$(MPFR_VERSION)/mpfr-$(MPFR_VERSION).tar.bz2

touch $@

It may be distro related, I will check Ubuntu later but just in case anybody else runs into it the work around wasn't difficult.

Alan

Thursday, 14 April 2022

Re: Facebook notifications

On 10 Apr 2022 as I do recall,
Harriet Bazley wrote:

> On 9 Apr 2022 as I do recall,
> Harriet Bazley wrote:
>
> > I've been using Netsurf with m.facebook.com - as of this morning, the
> > 'notification' links that are displayed when, for example, someone
> > responds to a Facebook comment are not working when you click on them.
> > ("Sorry, something went wrong. We are working on it and we'll get it
> > fixed as soon as we can.")
> >
> > Have Facebook changed something in the link syntax?
> >
> Going back through the activity history, it looks as if the issue is not
> the notification links per se, but displaying *any* FB page that I have
> previously commented on, navigated to by any means - presumably Facebook
> have done something fancy to add a new feature of some sort to pages
> with 'user's own comments', and in some manner it has broken Netsurf's
> ability to communicate with the site when loading such pages. :-(
>
The good news is that whatever they did, they *seem* to have fixed it -
I'm now able to view my own comments and pages that I've commented on,
without any changes to Netsurf!

--
Harriet Bazley == Loyaulte me lie ==

Egotist: A person of low taste, more interested in himself than me.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Monday, 11 April 2022

Mantis

Is the Mantis bug reporter still working? I notice that no bugs have
been confirmed/acknowledged since the start of the year, and the only
notifications I've received from the site have been when somebody posts
a spam link as a comment....

--
Harriet Bazley == Loyaulte me lie ==

It is impossible to enjoy idling thoroughly unless one has plenty of work to do
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Saturday, 9 April 2022

Re: Facebook notifications

On 9 Apr 2022 as I do recall,
Harriet Bazley wrote:

> I've been using Netsurf with m.facebook.com - as of this morning, the
> 'notification' links that are displayed when, for example, someone
> responds to a Facebook comment are not working when you click on them.
> ("Sorry, something went wrong. We are working on it and we'll get it
> fixed as soon as we can.")
>
> Have Facebook changed something in the link syntax?
>
Going back through the activity history, it looks as if the issue is not
the notification links per se, but displaying *any* FB page that I have
previously commented on, navigated to by any means - presumably Facebook
have done something fancy to add a new feature of some sort to pages
with 'user's own comments', and in some manner it has broken Netsurf's
ability to communicate with the site when loading such pages. :-(

--
Harriet Bazley == Loyaulte me lie ==

The fact that you're paranoid.... doesn't mean they're NOT out to get you.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Facebook notifications

I've been using Netsurf with m.facebook.com - as of this morning, the
'notification' links that are displayed when, for example, someone
responds to a Facebook comment are not working when you click on them.
("Sorry, something went wrong. We are working on it and we'll get it
fixed as soon as we can.")

Have Facebook changed something in the link syntax?

--
Harriet Bazley == Loyaulte me lie ==

Flee at once, all is discovered.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Monday, 4 April 2022

Re: [gccsdk] OpenSSL issues

I rebuild the library and it worked .. not sure where was going on.

Ssl now imports and works, and pip downloads a file .. although I now need need to get it to unpack the wheel ..

Small steps .. :)

Sent from my iPhone

On 4 Apr 2022, at 13:34, Chris Johns <chris@lessthan3.org.uk> wrote:

yone any ideas?

If *showregs gives a valid value for r15, and that is within a library,

then

Frustratingly it doesn't (is claims all rhe registers are zero)... might just have to go down the "shove in some printf's" route.

Cheers

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

Re: [gccsdk] OpenSSL issues

yone any ideas?

If *showregs gives a valid value for r15, and that is within a library,

then

Frustratingly it doesn't (is claims all rhe registers are zero)... might just have to go down the "shove in some printf's" route.

Cheers

Chris

Re: [gccsdk] OpenSSL issues

On 04/04/2022 10:10, Chris Johns wrote:
> Hi
>
> I'm trying to track down an issue with ssl in python, which used OpenSSL
> 1.1. To try to reduce the number of moving parts, I've managed to narrow
> it down to a smaller test.
>
> The setup is .. the C code below (which runs fine on linux) has been
> compiled on RISC OS (native) with GCC10 (buult from the auto builder).
> LibSSL (1.1.0) is the one I built with the auto-builder, but I had to
> tweak it to use the 1.1.0n (rather than m) sources and I built it for
> armv6z (IIRC) instaad of armv3.

[snip]

> Anyone any ideas?

If *showregs gives a valid value for r15, and that is within a library,
then

*somaddress pc

should tell you which library and where. You can then use the library
offset given together with the output from

*nm -Dn <library>

to determine which function the crash occurs in. Finally, a few
printf's in the offending function to narrow it down even further.
That's what I usually do.

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] OpenSSL issues

Hi

I'm trying to track down an issue with ssl in python, which used OpenSSL
1.1. To try to reduce the number of moving parts, I've managed to narrow
it down to a smaller test.

The setup is .. the C code below (which runs fine on linux) has been
compiled on RISC OS (native) with GCC10 (buult from the auto builder).
LibSSL (1.1.0) is the one I built with the auto-builder, but I had to
tweak it to use the 1.1.0n (rather than m) sources and I built it for
armv6z (IIRC) instaad of armv3.

#include <openssl/ssl.h>

int main(void)
{
SSL_CTX *ctx = SSL_CTX_new( TLS_client_method() );
printf("ctx: %x\n", ctx);
printf("load_verify_locations: %d\n",
SSL_CTX_load_verify_locations(ctx, "cacert.pem", NULL) );
SSL_CTX_free(ctx);
printf("Bye!\n");
}

*gcc -c ssltest.c -ILibSSL11:
*gcc ssltest.o -o ssltest -LLibSSLl11: -lssl -lcrypto -ldl
*ssltest
ctx: 71a88

Fatal signal received: Segmentation fault

Stack backtrace:

Running thread 0x58834 (Main Thread)
(50df5f40) lr: 48fa9dbc : 7ADBC :
SharedLibs:lib.armeabihf.libunixlib/so/5/0/0
(50df5fb0) lr: 48fab450 : 7C450 :
SharedLibs:lib.armeabihf.libunixlib/so/5/0/0
(50df5fb4) lr: 50ef6d3c
(48fab450) lr: ef020014
Stack frame has gone out of bounds with address ebfff8ec

*

If I rename the pem file, it reports SSL_CTX_load_verify_locations: 0
(which one would expect) then has a similar error (wihtout pritning Bye!)

Anyone any ideas?

Cheers

Chris
--
Chris Johns

This email is measured by weight not volume - contents may settle during
transit.

_______________________________________________
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