GWIN__ ||
> (defined _WIN32 && !defined __CYGWIN__) || defined __ANDROID__)
>/* U+E003A TAG COLON */
>is = for_character ("\363\240\200\272", 4);
>ASSERT (is == 0);
>
> _______
> M4-patch
l the
other mem* interfaces.
> Every use case I see, such as a poor-man's strlcpy(3), seems to be prone
> to off-by-one errors, or have other APIs that would be more ergonomic.
> What were the original uses in 4.4BSD?
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
can have
cases where the old pointer is different from the new pointer but
where none of the object data had to be copied or moved, and that's
because implementations can take advantage of MMU mapping metadata to
direct the new pointer into resolving to the same underlying storage
as the old pointer used to see.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
tail of the allocation does not
exceed a certain bound; and Alejandro removed the quote from Doug
McIlroy from an earlier version of the draft precisely because we do
NOT want the standard to mandate the inability to fail on shrinking an
object, as that will harm quality-of-implementation.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
ut always copy
data. When doing valgrind or other similar malloc-checking analysis
of a program, I'd actually WANT that behavior for realloc, to make
sure my code is always safely dealing with any potential of a moved
pointer; but in the common case, I do NOT want the speed penalty of an
implementation that always has to copy memory rather than reusing
pointers just because the standard omitted the parenthetical hinting
that such behavior is permissible.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
cy with the wording of the other functions.
>the old object is not deallocated
>and its value is unchanged.
> +XXX)
>
> @@ New footnote XXX
> +XXX)
> +While atypical,
> +realloc may fail
> +for a call that shrinks the block of memory.
Is it worth wording this as "may fail or return a different pointer
for a call that shrinks the block of memory"?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
nux kernel in sync with POSIX, but where POSIX
generally tries hard to not alienate glibc behavior.
[Counter-examples being things like Linux behavior on
mkdir("dangling_symlink/") are an entirely different discussion...]
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
as been deallocated
>by a call to the free or realloc function,
> ## We can probably remove all of the above, because of the
> ## behavior now being defined as-if by calls to malloc(3) and
> ## free(3). But let's do that editorially in a separate change.
> -or
> -if the size is zero,
> ## We're defining the behavior.
>the behavior is undefined.
>If
> -memory for the new object is not allocated,
> +the space cannot be allocated,
> ## Editorial; for consistency with the wording of the other functions.
>the old object is not deallocated
>and its value is unchanged.
>
> @@ Returns, p4
>The realloc function returns
>a pointer to the new object
>(which can have the same value
> -as a pointer to the old object),
> +as a pointer to the old object)
> +on success.
> -or
> +If
> +space cannot be allocated,
>a null pointer
> -if the new object has not been allocated.
> +is returned.
I'm liking the direction this proposal is headed in. If it is down to
a question of whether glibc or the C standard will blink first, I'm
hoping that we can get some agreement from both sides, rather than
being stuck in a stalemate with each arguing that the other is the
reason to not fix things.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
rding that brought the
issue to light. And yet, here we are, STILL trying to get better
wording into both C and POSIX.
> > >
> > > Indeed, glibc is non-conforming to C99 too. Although, I don't like the
> > > wording from C99, either; it allows weird stuff: it allows an
> >
On Thu, Jun 19, 2025 at 01:42:38PM -0500, Eric Blake wrote:
> > +
> > + The glibc implementation of realloc() is not consistent with
> > + that, and as a consequence, it is dangerous to call
> > + realloc(p, 0) in glibc.
>
> More importantly
ough that time).
> +
> + The glibc implementation of realloc() is not consistent with
> + that, and as a consequence, it is dangerous to call
> + realloc(p, 0) in glibc.
More importantly, with C23 making it undefined behavior, it is
dangerous to call realloc(non_null, 0) in ANY libc, ever. Regardless
of whether glibc documents semantics that comply (or don't comply)
with older standards.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
mention C23, since it's UB, so anything conforms.)
>
>
> Have a lovely day!
> Alex
>
> --
> <https://www.alejandro-colomar.es/>
If you've managed to make it this far, congratulations. We probably
still need to open bugs against POSIX to have POSIX-2024-TC1 improve
any ambiguous wording, and taking into account whatever the C
committee may decide to do with Alejandro's proposals for post-C23
behaviors, and whether glibc is willing to make realloc(non_null, 0)
allocate in the same manner as malloc(0) rather than being a hidden
call to free().
I don't know if I answered all of your questions, or raised even more,
but you have your work cut out for you before declaring the man pages
good enough.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Thu, Jun 05, 2025 at 08:40:21AM -0700, Paul Eggert wrote:
> On 2025-06-05 06:21, Eric Blake wrote:
> > Adding gnulib
>
> Bruno fixed that MSVC-related bug in Gnulib three weeks ago:
>
> https://cgit.git.savannah.gnu.org/cgit/gnulib.git/commit/?id=f7810929b1d35f1edcc
et of config.log that shows why configure was
unable to use your installed library? Is it something you can work
around by priming appropriate cache variables during the configure
run?
>
> Please let me know if you are interested in result of `make check`.
Did it pass, or did you see particular failures?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Thu, May 22, 2025 at 12:30:37PM -0700, Paul Eggert wrote:
> On 2025-05-22 10:42, Eric Blake wrote:
> > BSD has tried hard to make their m4 be a drop-in replacement
> > enough that autoconf will use it instead of mandating GNU m4
>
> Is this a real problem, though? I j
On Mon, Apr 07, 2025 at 01:37:10PM -0500, Eric Blake wrote:
> On Mon, Apr 07, 2025 at 12:46:11PM -0500, Eric Blake wrote:
> > And relying on a configure-time test of what m4 supports on the
> > packager's machine is not necessarily going to work when autoconf is
> > ru
the qemu-x86_64
emulator, instead of attaching gdb to the emulated execution of
src/m4?
It could very well be a bug in qemu's user-mode emulation not handling
stack overflow in the same way a native program would do.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Sat, Apr 26, 2025 at 10:54:19AM -0700, Paul Eggert wrote:
> On 2025-04-24 09:13, Eric Blake wrote:
>
> > case '\'':
> > +case 'z':
>
> Python uses \Z for this and Python's \A ... \Z is cleaner and easier to
> remember than
glibc already has support for \` and \' as absolute input boundaries,
while ^ and $ are a bit more flexible (depending on
RE_CONTEXT_INDEP_ANCHORS). Worse, ^ and $ are not portable across all
regex flavors - there are languages where they match at any newline
within the larger input, and where bli
rom all the above for me is the build
> failure (because of the tests) for i386 on a system with a
> recent glibc. I'd love to see a snapshot fixing that before
> the final release.
>
> Thanks a lot.
Thank you for the speedy testing and feedback.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
t is no longer reasonable to assume that awk is available
on every bare-bones distro, and so we either need to tweak autoconf to
avoid awk (hard) or to at least alert the user that their environment
is too bare-bones, and they need to adjust their CI setup to install
just a bit more.
--
Eric Blake, Prin
es that the configure script will rely on,
rather than assuming that the distro has provided them out-of-the-box.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Wed, Apr 16, 2025 at 05:45:46PM +0200, Bruno Haible wrote:
> Eric Blake wrote:
> > If you want a quicker table, I can attempt to provide one (note that
> > POSIX BRE do not actually have to support \+ \? or \|; but glibc and
> > gnulib's implementation does):
> &g
ve to support \+ \? or \|; but glibc and
gnulib's implementation does):
feature 0-or-more 1-or-more 1-or-0 grouping/alternation intervals
charclasses
syntax
0 (old emacs) * +? \( \| \)n/a n/a
emacs * +? \( \| \) \{ \}[[:...:]]
posix-basic * \+ \? \( \| \) \{ \}[[:...:]]
posix-extended* +?( | ){ }[[:...:]]
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
ALS), corresponding to
> + Emacs 21 (2001) and later, because Gnulib's lib/regex.h
> + is always used and has this value. */
Or are we really guaranteed that even when we use gnulib's regex
module, we are using gnulib's regex.h but can still use the unreplaced
glibc implementations?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
not a core dump remains as a
side effect. But it does seem a bit odd that only some systems are
penalized by the higher disk usage due to the core files after a stack
overflow.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
the date the manual is built. Also, I see two
uses of @value{UPDATED} in m4.texi, but your patch only removed one;
is the other one not an issue?
$ git grep UPDATED
ChangeLog-2014: * doc/m4.texinfo: UPDATED refers to the day the manual was
built,
doc/m4.texi:This manual (@value{UPDATED}) is for GNU M4 (version
doc/m4.texi:@subtitle Edition @value{EDITION}, @value{UPDATED}
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
the bright side, the fact that you got to
the tests/ directory means that the tests in checks/ succeeded, so the
just-built M4 passes even if we have uncovered some corner cases in
the underlying gnulib functions.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
ical order, and
the definitions shifted by one from the previous bit; thus, when we
add or remove a bit, only one other definition need change. */
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Mon, Apr 07, 2025 at 10:51:26AM -0400, Zack Weinberg wrote:
> On Fri, Apr 4, 2025, at 3:56 PM, Eric Blake wrote:
> …
> > tl;dr: if I do add intervals to m4 regex, would you rather it be \{\}
> > (BRE and emacs style) or {} (ERE style)? And how to avoid breaking
>
On Mon, Apr 07, 2025 at 12:46:11PM -0500, Eric Blake wrote:
> And relying on a configure-time test of what m4 supports on the
> packager's machine is not necessarily going to work when autoconf is
> run on a developer's machine with a different version of m4. Which in
> t
Why does modules/localename have a Link: line of @INTL_MACOSX_LIBS@
instead of $(INTL_MACOSX_LIBS)? This fails 'make syntax-check' for
any project using maintainer-makefile and Automake, since that check
prefers to let automake auto-populate any $(FOO) from its underlying
@FOO@.
--
this.
ChangeLog| 5 +
pygnulib/main.py | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index 6d7435f491..076065290f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2025-04-05 Eric Blake
+
+ gnulib-tool.py: Fix missing
avoid breaking
existing m4 scripts?
On Fri, Apr 04, 2025 at 08:47:20AM -0500, Eric Blake wrote:
> On Fri, Nov 04, 2022 at 04:25:45AM +0300, Van de Bugger wrote:
> > M4 documentation for regular expressions is extremely short:
> > https://www.gnu.org/software/m4/manual/html_node/Reg
ETTIMEOFDAY@
REPLACE_GETTIMEOFDAY = @REPLACE_GETTIMEOFDAY@
Makefile:
GL_M4_GNULIB_GETTIMEOFDAY = IN_M4_GNULIB_TESTS
HAVE_GETTIMEOFDAY = 1
REPLACE_GETTIMEOFDAY = 0
Is this a case of a missing LDFLAGS in m4's tests/Makefile.am (which
right now only includes gnulib.mk) or top-level Makefile.am?
which a
> 'trap' command can guarantee).
I hadn't even thought of that angle, but it makes sense.
>
> So, feel free to put in any other neutral word in place of "phoey".
Done with "template".
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Fri, Apr 04, 2025 at 09:24:35AM -0500, Eric Blake via M4-patches wrote:
> * ChangeLog-2014: Address findings from codespell.
I made this patch in response to an offline email from a contributor
who asked to remain anonymous (I find that odd in the world of open
source, but whatever), who a
On Fri, Apr 04, 2025 at 03:33:34PM +0200, Bruno Haible wrote:
> Hi Eric,
>
> Eric Blake wrote:
> > While trying to build m4.git with clang on a Fedora 40 machine, and
> > with gnulib updated to the latest git commit, I'm hitting the
> > following during '
oth glibc and the new code in gnulib.
>
> Let me document this limitation.
>
> -This function returns the value of the @env{LOGNAME} environment variable:
> +This function returns the value of the @env{LOGNAME} environment variable
> +and this therefore arbitrarily fakeable:
s/
implementation-defined string set to "UTC" or "GMT", which shall
| have static storage duration.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
f potentially uninitialized
variables (and which treats asprintf() as if it leaves ptr unchanged
on failure) is probably sufficient to avoid bugs even if we do not
follow any glibc decision on whether to start enforcing behavior (b).
On the other hand, if glibc DOES decide to do (b) to match BSD, then
why would gnulib NOT want to guarantee the same portably across all
platforms?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
ed (what glibc used to do, but POSIX doesn't guarantee it and
it requires more boilerplate to check correctly so more programs are
likely to get it wrong, including the oss-security post about getting
it wrong turning into a security bug).
--
Eric Blake, Principal Software Engineer
Red
e than 2 years old) - it seems like gnulib has (so far) tried to
maintain a much longer window of portability and targets machines
older than what libvirt-ci is willing to cater to.
But even if you can't use it directly, it may give you some
inspiration on writing your own tool.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
e string
but within the size limit is not forbidden, and thereby risks a crash
if size is large enough to cross memory boundaries when coupled with
an implementation that does not behave as-if it reads linearly)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Wed, Jul 10, 2024 at 01:55:51AM GMT, Paul Eggert wrote:
> On 7/9/24 22:03, Eric Blake wrote:
> > https://www.austingroupbugs.net/view.php?id=1834#c6830
> >
> > The current draft of proposed wording would have the C standard state:
> >
> > 2 The strnle
rst NUL byte, they are not required
to do so, at which point you CAN trigger a crash for accessing beyond
the bounds of your actual string.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
On Wed, Jun 12, 2024 at 02:36:00AM GMT, Bruno Haible wrote:
> Eric Blake wrote:
> > - https://austingroupbugs.net/view.php?id=1635
>
> I added a couple of comments there, to explain the problem.
> It is irritating to see that the Austin Group in defect 1007 apparently
>
mp;1`
'local' is a bashism, but I can already see that tests/init.sh has
gone to lengths to require that local exists and has "sane" semantics
(by excluding dash semantics).
But as long as we're relying on Bash semantics, why not use the simpler:
local -; set -x
which wi
On Mon, Jun 10, 2024 at 11:35:11AM GMT, Collin Funk wrote:
> Eric Blake writes:
>
> > wants to change requirements for isatty() and friends to be required
> > to set errno on failure (right now, there is no obvious way to tell,
> > using only the standard, if a failure
s and/or
relax the wording of command line tools like cp to better describe how
they fare in the face of the divergent behavior in underlying
syscalls?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
based TZ settings (standardized in the soon-to-be-released
POSIX Issue 8):
https://austingroupbugs.net/view.php?id=1816
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
ke to use it under LGPLv2+, for the modules 'setpayload*'
> and 'getpayloadl' (functions defined by ISO C 23 and implemented in glibc).
>
> Can I have your agreement to relicensing your contributions to this
> module under LGPLv2+, please?
>
> * Eric Blak
n
> pointers...
It does, since callable objects exist as first class citizens. For
example:
>>> def foo():
... print("in foo")
...
>>> def bar():
... print("in bar")
...
>>> dispatch = { "foo":foo, "bar":bar }
>>> d
is that the use of serial numbers in .m4 snippets was
intentional in gnulib (more or less where the practice originated),
but only because gnulib prefers a linear history (everything is
monotonically increasing, no forks for the serial number to diverge
on). In light of this weekend's mess, Br
INE_LENGTH=72
> export UPDATE_COPYRIGHT_MAX_LINE_LENGTH
>
> +# This assignment to 'ight' is is so that data can contain strings
duplicate 'is'
> +# like "Copy$ight 2024 Free Software Foundation, Inc." without being
> +# mistakenly updated by &quo
e compiler that even when it is in pedantic mode, we are
intentionally using extensions to the language.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
ib wanted the file
in the first place, without adversely affecting the behavior of the
compiled m4 binary.
>
> Any assistance is appreciated.
>
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
widening the type @code{time_t} as needed to represent file
> -wand other timestamps after January 2038. This widening is possible
> +wand other timestamps after mid-January 2038. This widening is possible
s/wand/and/ ?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
On Fri, Mar 24, 2023 at 12:37:42PM +0100, Bruno Haible wrote:
> Eric Blake wrote in
> <https://lists.gnu.org/archive/html/bug-gnulib/2023-03/msg00060.html>:
> > C23 admits that %#B is not available for
> > portable use of outputting uppercase '0B...', you wou
Another consideration: C23 admits that %#B is not available for
portable use of outputting uppercase '0B...', you would have to
manually write 0B%b instead. However, since glibc DOES support %B as
the uppercase counterpart to %b, should we add that in gnulib (but
this time under the ausp
ot;It is not proposed for the strto* family of functions from the C
Standard Library to support digit separators at this time"
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
ugs/index.php?63307
and being fixed in 4.4.1, but it sounds like we'll have lots of
systems in the wild with 4.4, and thus lots of these workarounds
having to be applied elsewhere.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
the report; I'm looping in bug-gnulib as the owners of the
test in question. It's the first time I've heard of this issue, but I
also know that m4 needs a new release with a newer pull from gnulib,
so the issue may have been addressed in the meantime in gnulib.
--
Eric Blake, Principa
as a synonym for 'kill
-s INT', but does not require it of non-XSI systems. Are there still
systems in current use today where 'kill -s NAME' is not supported?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
a fairly short period of
> time. The list would be shortened with the following names if we used
> two years:
>
> Daiki Ueno
> Dmitry V. Levin
> Eric Blake
> Siddhesh Poyarekar
>
> So not radically different actually. It would be bad if this excercise
tation for the
different regex flavors for switching flavors on the fly), but current
m4 does not use it.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
assumes behavior that is not mandatory in POSIX, so
> technically, the test is wrong.
>
> -nc
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
o, but no chance
> of making it working.
>
> The only solution I found is by commenting the three last tests
> about Pseudo-Denormal directly in tests/test-vasprintf-posix.c
>
> Thanks a lot
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
> ucp)->uc_mcontext.uc_regs->gregs[1]
> +# define SIGSEGV_FAULT_STACKPOINTER ((ucontext_t *)
> ucp)->uc_mcontext.uc_regs->gregs[1]
> # endif
> # endif
>
> --
> 2.35.1
>
>
> ___
> M4-patches mailing list
> m4-patc...@gnu.org
> https://lists.gnu.org/mailman/listinfo/m4-patches
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
to begin with.
>
> Could you help please?
>
> Thank you for your time and contributions!
> Best,
> Julien
> --
> Julien Marrec, EBCP, BPI MFBA
> Owner at EffiBEM <http://www.effibem.com>
> T: +33 6 95 14 42 13
>
> LinkedIn (en <https://www.linkedin.com/in
if
> you belong to an organization that is a member, so I filled those in with "?"
> and am hoping for the best.
That's fine. Adding page numbers after the fact is something that
happens rather frequently; and I've done in for your bug in particular
just now.
--
Eric Bla
cursive] Error 1
> gmake[1]: Leaving directory '/opt/bw/build/m4-1.4.19_sunos5.10_sparcv9.001'
> gmake: *** [Makefile:1974: all] Error 2
>
> Where we see the asm usage that sort of says "not C99 here".
>
> However std9899:2011 seems to be just fine.
>
>
he identifier __stat for our own uses now that we know system
headers are using it. Once it is fixed there, I need to do another m4
release anyways (1.4.19 has a bug with unintended locale sensitivity
when it comes to parsing numbers), so eventually when I get the time,
the 1.4.20 release wil
Following Bruno's lead, I'm also happy with this change.
* m4/sigaltstack.m4: Change copyright notice: Write "Copyright (C) FSF"
instead of "Copyright (C) Eric Blake".
* tests/altstack-util.h: Likewise.
* tests/test-sigsegv-catch-stackoverflow1.c: Likewi
yer, for
work I was doing in my spare time, and being able to use the DCO
instead would have made my efforts easier at that time. (My current
employer already has a blanket copyright assignment on file for all
employees, but not everyone has a company that willing to promote open
source involveme
; @echo '##
> ##'"
> + echo " @echo '## --- Gnulib tests ---
> ##'"
> + echo " @echo '## Please report test failures to .
> ##'"
Is it worth the longer line for "test failures in this directory"?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
> +under other licenses, such as LGPLv2+, unlimited, or public domain.
Would read better as "A few modules are..."
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
tools?
https://spdx.github.io/spdx-spec/appendix-V-using-SPDX-short-identifiers-in-source-files/
However, for clarity, I think it is wrong to rely on SPDX tag only in
place of the full license text; adding the one-liner SPDX should be
just that, an additional line.
--
Eric Blake, Principal
failed to tell us which operating
system. The fix will need to be in gnulib's unit tests, so I'm adding
bug-gnulib in the distribution.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
FYI:
> /usr/include/sys/procfs.h:
> 41 #if !defined(_LP64) && _FILE_OFFSET_BITS == 64
> 42 #error "Cannot use procfs in the large file compilation environment"
> 43 #endif
>
>
> Regards,
>
> --- Kiyoshi
>
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
the variable.
> This is ugly BSD style of the 1980ies, which we have abandoned
> more than 10 years ago.
Yet another portable solution is:
static mbstate_t s1;
mbstate_t s = s1;
also with its own form of ugliness.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
lways say "GPL", but the real license
> specification is in the module description file." ?
Yes, that's fine with me.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
On 5/8/21 6:34 AM, Eric Blake wrote:
> but it would be a lot nicer if I didn't have to remember to do that
> after the fact. In fact, reading gnupload --help says it is as simple
> as calling:
>
> $ gnupload --to ... --symlink-regex ...
>
> in the first place.
n the suggested gnupload instructions it generates?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
On 4/22/21 1:20 PM, Eric Blake wrote:
> On 4/18/21 11:01 PM, Paul Eggert wrote:
>> * doc/safe-alloc.texi: Clarify that reallocating an array appends
>> uninitialized storage. Say ‘sizeof *p’ rather than ‘sizeof(*p)’
>> which would need a space before the paren to follow GNU
On 4/22/21 2:32 PM, Paul Eggert wrote:
> On 4/22/21 11:20 AM, Eric Blake wrote:
>
>> Looks like the definition of macro __attribute_nonnull__ from cdefs.h
>> is no longer implicitly picked up by the system headers used in that
>> file.
>
> I installed the att
oken
195 | __attribute_nonnull__ ((1))
|^
Looks like the definition of macro __attribute_nonnull__ from cdefs.h
is no longer implicitly picked up by the system headers used in that file.
I'm still poking around to see if I can fix it, but you're welcome t
ide from my contributions and a few mechanical changes (not copyrightable),
> there is this patch from Eric Blake:
> https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=4b2f21b36a615728ebf2a0e1bc2c8def175703a8
>
> Eric, would you please give me the permission to use this cha
ally test
on a Windows machine) fails to properly consume '0' when parsing in base
16 or 0 when there are no hex digits after a trailing garbage of 'x' or 'X'.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
icitly_
asking for non-POSIX extensions by setting _GNU_SOURCE; but since most
gnulib projects (including m4) indeed request _GNU_SOURCE, we can no
longer rely on the POSIX definition.
>
>> Please advise how I can get past this.
>
> Fix your .
We're going to need to fix gn
You'll first want to get this upstream at config-patc...@gnu.org
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
ear the same (both in
generated comments and in what the second-built autoconf will produce).
Ideas on streamlining that are welcome, but as we at least have a
documented procedure (even if it is multi-step), it's not essential to
fix before 2.70.
--
Eric Blake, Principal Software Engineer
On 8/4/20 10:07 AM, Eric Blake wrote:
On 8/4/20 9:58 AM, Zack Weinberg wrote:
I just pushed a commit that partially reverts a `make fetch'.
Partially revert e54e3f90: restore use of $(MAKE) in error message.
In commit 14d58bfd, the error message printed by the
‘abort-due-
hat's what 'make fetch' is
intended to do. So, if you want a change to stick in that file, update
the gnulib version first, then update autoconf to the newer version of
gnulib containing that fix.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
(for portability to many platforms).
Yes, the looser license for my contributions makes sense.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
OEXEC, and then fdopen()?
In the meantime, this is indeed more portable.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
//pubs.opengroup.org/onlinepubs/9699919799/functions/posix_spawn.html
Bug reported to the POSIX folks:
https://www.austingroupbugs.net/view.php?id=1328
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
grammar, so that we can parse everything 'at' is required to support,
and in case POSIX does decide to standardize -d using the 'at' grammar
as a starting point.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
>
> FAIL: test-mbrtowc5.sh
> ==
>
> test-mbrtowc.c:106: assertion 'wc == c' failed
> ./test-mbrtowc5.sh: line 4: 789048 Aborted (core dumped)
> LC_ALL=C ./test-mbrtowc${EXEEXT} 5
> FAIL test-mbrtowc5.sh (exit status: 134)
&g
> Related samba ticket (it also has references to the python and dovecot
> issues):
> https://bugzilla.samba.org/show_bug.cgi?id=8773
I wonder if gnulib could provide a workaround setgroups() that overcomes
this issue (it's better to maintain such a patch there, where it
benefits multiple programs, rather than just in libvirt).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
1 - 100 of 4397 matches
Mail list logo
