Mailing Lists

Sunday, 18 June 2023

Re: netsurf-users Digest, Vol 180, Issue 3

On 18 Jun 2023 as I do recall,
pslegg@scubadivers.co.uk wrote:

> Is the list working again ?
>
> I haven't been able to post to it for months.
>

Appears to be working from this end.

--
Harriet Bazley == Loyaulte me lie ==

Sattinger's Law: It works better if you plug it in.
_______________________________________________
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org

Re: netsurf-users Digest, Vol 180, Issue 3

Is the list working again ?

I haven't been able to post to it for months.

Peter

On 18 Jun 2023, at 00:00, netsurf-users-request@netsurf-browser.org wrote:

Send netsurf-users mailing list submissions to
 netsurf-users@netsurf-browser.org

To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
 netsurf-users-request@netsurf-browser.org

You can reach the person managing the list at
 netsurf-users-owner@netsurf-browser.org

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

Today's Topics:

   1. User Agent (jtzz11@post.com)




Date: Sat, 17 Jun 2023 10:50:54 +0300
From: "jtzz11@post.com" <jtzz11@post.com>
Subject: User Agent
To: netsurf-users@netsurf-browser.org
Message-ID: <10c15b4c-fc8c-8b8c-7fb2-96954edbf75a@post.com>
Content-Type: text/html; charset=UTF-8

<html style="direction: ltr;">
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <style id="bidiui-paragraph-margins" type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
  </head>
  <body bidimailui-charset-is-forced="true" style="direction: ltr;">
    <p><font face="DejaVu Sans">Hi,</font></p>
    <p><br>
    </p>
    <p><font face="DejaVu Sans">A new NS user here.</font></p>
    <p><font face="DejaVu Sans">Can the User Agent string be set, e.g.
        as in Elinks?.</font></p>
    <p><br>
    </p>
    <p><font face="DejaVu Sans">Thanks</font><br>
    </p>
  </body>
</html>



Subject: Digest Footer


netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-leave@netsurf-browser.org




End of netsurf-users Digest, Vol 180, Issue 3
*********************************************

Saturday, 17 June 2023

User Agent

Hi,

A new NS user here.

Can the User Agent string be set, e.g. as in Elinks?.

Thanks

Wednesday, 14 June 2023

Portability patches to libcss libdom libutf8proc netsurf

Hello, as communicated on IRC, these attached patches replace
instances of int with int32_t where necessary to compile on platforms
where int32_t is actually long, alongside using the portable format
macros (e.g. PRIx32 where x or lx can't be hardcoded).
Tested by compiling on gcc 13.
Hope this helps, and let me know if I left any of my porting patches
in there instead of just correctness changes!

Saturday, 27 May 2023

Re: "error: ‘t.data.character.ptr’ may be used uninitialized " when building hubbub with gcc 11

From 69d81a8a4d4c223aad67cde0fdf64d64351b9802 Mon Sep 17 00:00:00 2001
From: Andy Tai <atai@atai.org>
Date: Sat, 27 May 2023 00:01:34 -0700
Subject: [PATCH] prevent -Werror=maybe-uninitialized build failure with gcc 11
when building tests tokeniser2 and tokeniser3

---
test/tokeniser2.c | 2 +-
test/tokeniser3.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/test/tokeniser2.c b/test/tokeniser2.c
index c8ab9c0..4caae38 100644
--- a/test/tokeniser2.c
+++ b/test/tokeniser2.c
@@ -438,7 +438,7 @@ hubbub_error token_handler(const hubbub_token *token, void *pw)
/* Expected token only contained part of the data
* Calculate how much is left, then try again with
* the next expected token */
- hubbub_token t;
+ hubbub_token t = { 0 };

t.type = HUBBUB_TOKEN_CHARACTER;
t.data.character.ptr += len;
diff --git a/test/tokeniser3.c b/test/tokeniser3.c
index e33d018..b3be901 100644
--- a/test/tokeniser3.c
+++ b/test/tokeniser3.c
@@ -447,7 +447,7 @@ hubbub_error token_handler(const hubbub_token *token, void *pw)
/* Expected token only contained part of the data
* Calculate how much is left, then try again with
* the next expected token */
- hubbub_token t;
+ hubbub_token t = { 0 };

t.type = HUBBUB_TOKEN_CHARACTER;
t.data.character.ptr += len;
--
2.40.1

patch to get rid of the warning:

On Thu, May 25, 2023 at 12:16 PM Andy Tai <atai@atai.org> wrote:
>
> Hi, I found from GNU Guix's build check that when building with gcc 11,
>
> building hubbub would fail when building tests with errors like
>
> COMPILE: test/tokeniser2.c
> COMPILE: test/tokeniser3.c
> COMPILE: test/tree.c
> COMPILE: test/tree2.c
> COMPILE: test/tree-buf.c
> test/tokeniser2.c: In function 'token_handler':
> test/tokeniser2.c:444:46: error: 't.data.character.ptr' may be used
> uninitialized [-Werror=maybe-uninitialized]
> 444 | t.data.character.ptr += len;
> | ^~
> test/tokeniser2.c:441:38: note: 't' declared here
> 441 | hubbub_token t;
> | ^
> test/tokeniser2.c:445:46: error: 't.data.character.len' may be used
> uninitialized [-Werror=maybe-uninitialized]
> 445 | t.data.character.len -= len;
> | ^~
>
> ...
>
> I briefly took a look of the test source code in question and the
> hubbub_token structs seem not explicitly initialized. Is this a real
> warning from gcc of possibly uninitialized variable which can cause
> the build to fail if allow warnings are treated as errors by gcc
> during build (a common practice)? Thanks if maintainer can take a
> look.
>
> relevant bug entry and complete bug logs:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63526

--
Andy Tai, atai@atai.org, Skype: licheng.tai, Line: andy_tai, WeChat: andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能

Thursday, 25 May 2023

"error: ‘t.data.character.ptr’ may be used uninitialized " when building hubbub with gcc 11

Hi, I found from GNU Guix's build check that when building with gcc 11,

building hubbub would fail when building tests with errors like

COMPILE: test/tokeniser2.c
COMPILE: test/tokeniser3.c
COMPILE: test/tree.c
COMPILE: test/tree2.c
COMPILE: test/tree-buf.c
test/tokeniser2.c: In function 'token_handler':
test/tokeniser2.c:444:46: error: 't.data.character.ptr' may be used
uninitialized [-Werror=maybe-uninitialized]
444 | t.data.character.ptr += len;
| ^~
test/tokeniser2.c:441:38: note: 't' declared here
441 | hubbub_token t;
| ^
test/tokeniser2.c:445:46: error: 't.data.character.len' may be used
uninitialized [-Werror=maybe-uninitialized]
445 | t.data.character.len -= len;
| ^~

...

I briefly took a look of the test source code in question and the
hubbub_token structs seem not explicitly initialized. Is this a real
warning from gcc of possibly uninitialized variable which can cause
the build to fail if allow warnings are treated as errors by gcc
during build (a common practice)? Thanks if maintainer can take a
look.

relevant bug entry and complete bug logs:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63526
_______________________________________________
netsurf-dev mailing list -- netsurf-dev@netsurf-browser.org
To unsubscribe send an email to netsurf-dev-leave@netsurf-browser.org

Tuesday, 23 May 2023

Re: [gccsdk] libssl1.1.1 no longer builds

On 21 May, alan buckley <alan_baa@hotmail.com> wrote:
> Thanks Chris, that got libssl1.1.1 building, but then there was another build problem with c-ares. I was trying to get libcurl to build. I agree it would be better to use libssl3, do you know if there is a libcurl that could be built using libssl3?

libcurl3 has been updated to build 8.0.1. Also the dependencies have been
updated to depend on libssl3 instead of libssl1.1.1 and libcares instead of
c-ares.
To use libssl3 didn't required any changes to libcurl3.

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