[please CC groff@ on replies]
Hi folks,
groff recently updated its gnulib submodule[1] and published 1.23.0.rc2;
we're hoping to get a final release out soon.
A problem immediately arose on macOS 12.6.3. It's our good friend
vasnprintf again. Logs are available on Savannah[2].
lib/vasnprintf.
[re-sending to correct mailing list]
- Forwarded message from "G. Branden Robinson"
-
Date: Mon, 6 Feb 2023 02:28:10 -0600
From: "G. Branden Robinson"
To: gnu...@gnu.org
Cc: groff@gnu.org
Subject: macOS 12.6.3 and vasnprintf compilation failure
[please CC groff@ on replies]
Hi folks,
Hi Brandon,
> Am 04.02.2023 um 23:20 schrieb G. Branden Robinson
> :
>
> Due to some infrastructure problems, I couldn't offer GPG verification
> details for the distribution archive in my earlier announcement.
>
> Please find them below.
>
> At 2023-02-04T12:48:20-0600, G. Branden Robinson wr
Hi Dagobert,
Thank you for the report! I believe you have identified a non-POSIX-
conforming shell and grep utilty on Solaris 10. Judging by the domain
name from which you're sending your email, I might be recapitulating
facts already known to you below.
At 2023-02-06T10:35:56+0100, Dagobert Mi
Hi John,
At 2023-02-06T18:53:10+1100, John Gardner wrote:
> While I *strongly* advocate for the man:name(section) syntax (because
> it essentially dates right back to the earliest man pages), it would
> be remiss of me to ignore the other formats listed above.
>
> > But...ugh! I don't remember th
Hi John,
At 2023-02-06T18:53:10+1100, John Gardner wrote:
> So the exact URL format *does* need to be configurable,
Please review, apply, and test the attached patch.
> preferably with a separate string for apropos(1) links, if supported
> (which would logically default to the `an*MR-scheme` str
Hi Branden,
Having a configurable prefix/schema isn't going to cut it.
>
Then how about a callback? It could be called with the relevant parameters,
and authors can use plain ol' Roff to specify the hyperlink format.
but I have to say I really hate this and I want macOS to get its act
> togethe
Hi John,
At 2023-02-07T06:26:22+1100, John Gardner wrote:
> Then how about a callback? It could be called with the relevant
> parameters, and authors can use plain ol' Roff to specify the
> hyperlink format.
That creates more places for something to go wrong. Also I don't want
people to get the
>
> I would prefer to hold macOS up to ridicule in this respect in hopes of
> motivating its users (and developers) to standardize on something.
By "standardise", are you specifically referring to a *de jure* standard?
macOS's x-man-page:// scheme is only a *de facto* standard, but it's by far
th
Hi John,
At 2023-02-07T07:24:52+1100, John Gardner wrote:
[I wrote:]
> > I would prefer to hold macOS up to ridicule in this respect in hopes
> > of motivating its users (and developers) to standardize on
> > something.
>
> By "standardise", are you specifically referring to a *de jure*
> standar
Hello again Dagobert,
At 2023-02-06T09:20:40-0600, G. Branden Robinson wrote:
> I will look into how easily that may be done. I don't see anything
> directly on point in the GNU Automake manual[5], so if you can point
> out a working exhibit--preferably one that won't mean having to rename
> 160+
Knowing Apple, the *x-man-page://* scheme was intended for internal use
between userland programs; a similar protocol exists for looking up a
word's definition: *x-dictionary:harangue*. However, the nature of macOS's
LaunchServices makes it impossible (or at least incredibly difficult) for
any supp
Hi Branden,
> A problem immediately arose on macOS 12.6.3. It's our good friend
> vasnprintf again. Logs are available on Savannah[2].
>
> lib/vasnprintf.c:411:16: error: expected parameter declarator
> static_assert (sizeof (mp_limb_t) * CHAR_BIT == GMP_LIMB_BITS);
>^
> lib/vas
See https://savannah.gnu.org/bugs/index.php?63078
I renamed the file "groff/src/include/assert.h" in my privat branch
of groff to ".../assert.h.original".
14 matches
Mail list logo
