On 3/7/23 02:15, Alejandro Colomar wrote:
> Hi Branden,
>
> On 3/6/23 18:46, G. Branden Robinson wrote:
>> You're close but not quite there, I _think_. (Until I've root-caused
>> this myself, or seen someone else's convincing demonstration, my
>> conclusions must be tentative ones.)
>>
>> Becau
Hi Branden,
On 3/6/23 18:46, G. Branden Robinson wrote:
> You're close but not quite there, I _think_. (Until I've root-caused
> this myself, or seen someone else's convincing demonstration, my
> conclusions must be tentative ones.)
>
> Because _ordinary_ spaces don't get squeezed, I would start
At 2023-03-06T00:31:18+0100, Bruno Haible wrote:
> On FreeBSD, NetBSD, and AIX, with the platform's 'make' program (which
> is good enough for building many GNU packages, even as a VPATH build),
> I get this build failure:
>
> $ make
> ...
> GEN font/devpdf/DESC
> GEN font/devpdf/Fou
At 2023-03-06T17:39:52+0100, Bruno Haible wrote:
> G. Branden Robinson wrote:
> > I think I'll go ahead and refactor the test a bit, committing
> > something that may be more revealing when time permits testing on
> > the Hurd and NetBSD again.
>
> +1. It's perfectly to OK to have 1 test fail in a
[self-follow-up]
At 2023-03-06T09:56:37-0600, G. Branden Robinson wrote:
> At 2023-03-06T01:56:56+0100, Bruno Haible wrote:
> > On FreeBSD 13.1, the build succeeds, but there is 1 test failure:
> >
> > FAIL: contrib/gdiffmk/tests/runtests.sh
> >
> > Find attached the log. Apparently non-numeric
Hi Alex,
At 2023-03-06T18:37:41+0100, Alejandro Colomar wrote:
> Am I in the right path with this?:
>
> $ ./troff -man -Tutf8 ~/tmp/space.man -rLL=60n 2>&1 | sed -n '/746/,/746/p'
> ALX: src/roff/troff/input.cpp:process():7462
> ALX: src/roff/troff/node.h:node():130
> ALX: src/roff/troff/node.cpp
On 3/6/23 14:47, G. Branden Robinson wrote:
> Hi Alex,
Hi Branden,
>
> At 2023-03-06T14:16:02+0100, Alejandro Colomar wrote:
>> Hi Branden!
>>
>> I only tested this with groff 1.23.0, so I don't know if it's a
>> regression or a longstanding bug (I hope they aren't a renewable
>> source? :p).
>
G. Branden Robinson wrote:
> > * With mingw (in 64-bit mode), the build failed here:
> >
> > ../src/include/symbol.h: In member function ‘long unsigned int
> > symbol::hash() const’:
> > ../src/include/symbol.h:61:25: error: cast from ‘const char*’ to ‘long
> > unsigned int’ loses precision [-fp
G. Branden Robinson wrote:
> I think I'll go ahead and refactor the test a bit, committing something
> that may be more revealing when time permits testing on the Hurd and
> NetBSD again.
+1. It's perfectly to OK to have 1 test fail in a release and fix that only
in the next or a subsequent releas
[self-follow-up]
At 2023-03-06T09:32:06-0600, G. Branden Robinson wrote:
> At 2023-03-06T01:54:44+0100, Bruno Haible wrote:
> > On GNU/Hurd and NetBSD 9.0, the build succeeds,
> > and there is 1 test failure:
>
> They're different in each case.
This statement is incorrect, or at least premature.
G. Branden Robinson wrote:
> I'm pretty apprehensive about regressing one platform
> while accommodating another
Yes, this can happen. 20 years ago, it happened regularly that I broke
one platform while fixing another one. Nowadays, the portability problems
have become more isolated and more platf
At 2023-03-06T02:03:53+0100, Bruno Haible wrote:
> On the following platforms, the build succeeded and all tests passed:
>
> - Linux
> Ubuntu 22.04
> Debian 9.1
> Debian 11.1
> CentOS 8-stream
> CentOS Stream 9
> OpenSUSE Leap 15.2
> Manjaro 17
> - macOS 12.5
> - OpenBS
Hi Bruno,
Thanks for testing yet another host configuration!
At 2023-03-06T02:00:41+0100, Bruno Haible wrote:
> On Alpine Linux 3.14 the build works fine, but there is one test
> failure:
>
> FAIL: contrib/gdiffmk/tests/runtests.sh
>
> Find attached the log file. The cause is apparently that th
Hi Bruno,
At 2023-03-06T01:56:56+0100, Bruno Haible wrote:
> On FreeBSD 13.1, the build succeeds, but there is 1 test failure:
>
> FAIL: contrib/gdiffmk/tests/runtests.sh
>
> Find attached the log. Apparently non-numeric arguments get passed to the
> 'expr' program.
Yes. Here's the relevant ou
Hi Bruno,
At 2023-03-06T01:54:44+0100, Bruno Haible wrote:
> On GNU/Hurd and NetBSD 9.0, the build succeeds,
Excellent news!
My conntections to FSF France's NetBSD host have timed out for me every
time I've tried for the past few weeks.
> and there is 1 test failure:
They're different in each
Hi Bruno,
At 2023-03-06T01:50:46+0100, Bruno Haible wrote:
> On Solaris 11.4, with the default PATH setting, the build succeeds
> but there are 95 test failures. Log is attached.
>
> The cause is that the 'grep' program in $PATH is old. Solaris 11.4
> comes with two alternatives:
> /usr/xpg4/bi
Hi Bruno,
These Windows issues seem trickier to deal with.
At 2023-03-06T01:46:49+0100, Bruno Haible wrote:
> On native Windows, I attempted a build with mingw and with MSVC 14.
>
> * With mingw (in 64-bit mode), the build failed here:
>
> ../src/include/symbol.h: In member function ‘long unsig
Hi Alex,
At 2023-03-06T14:16:02+0100, Alejandro Colomar wrote:
> Hi Branden!
>
> I only tested this with groff 1.23.0, so I don't know if it's a
> regression or a longstanding bug (I hope they aren't a renewable
> source? :p).
I can reproduce it with groff 1.23.0-HEAD and groff 1.22.4. So not a
Hi Bruno,
First, thanks for your tremendous help with portability testing!
At 2023-03-06T01:32:17+0100, Bruno Haible wrote:
> On AIX 7.2, for a 64-bit build, the environment variable AR needs to be set
> to 'ar -X 64', see
> https://gitlab.com/ghwiki/gnow-how/-/wikis/Platforms/Configuration .
>
Hi Bruno,
At 2023-03-06T01:40:37+0100, Bruno Haible wrote:
> On Solaris 10, I tried two compilers:
>
> * The Sun C, C++ compilers.
>
> This resulted in a build failure:
>
> CC -xarch=generic64 -O -DHAVE_CONFIG_H -I. -I.. -I./src/include
> -I../src/include -I../lib -I./src/include -I./lib
>
Hi Branden!
I only tested this with groff 1.23.0, so I don't know if it's a regression
or a longstanding bug (I hope they aren't a renewable source? :p).
See the following source:
$ cat interval.man
.TH interval notation to-day experiments
.SH Description
What happens if we use interval notatio
Hi James,
On 2/27/23 20:17, James K. Lowden wrote:
> On Wed, 7 Sep 2022 00:13:18 +0200
> Alejandro Colomar
> wrote to :
>
>> If someone wants to send it as a patch, I'm open to discussing it.
>> I remember having some concerns when I read the page, but I don't
>> remember now about them. I'd
22 matches
Mail list logo
