From: Sam James <sam@gentoo.org>
To: linux-man <linux-man@vger.kernel.org>
Subject: make check failure with man-pages-6.04?
Date: Mon, 03 Apr 2023 02:41:11 +0100 [thread overview]
Message-ID: <87lej9u4g4.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
Hi all,
Congratulations on the new release :)
With `make check`, I get the following:
```
# make check
GREP .tmp/man/man1/memusage.1.check-catman.touch
.tmp/man/man1/memusage.1.cat.grep:130: Memory usage summary: heap total: 45200, heap peak: 6440, stack peak: 224
.tmp/man/man1/memusage.1.cat.grep:133: realloc| 4044800 0 (nomove:40, dec:19, free:0)
make: *** [lib/check-catman.mk:36:
.tmp/man/man1/memusage.1.check-catman.touch] Error 1
```
I'll be honest and say I have no idea how to interpret this, if it
matters, or how to give more info (so let me know how if I need to!)
best,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next reply other threads:[~2023-04-03 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 1:41 Sam James [this message]
2023-04-05 0:49 ` make check failure with man-pages-6.04? Sam James
2023-04-05 1:17 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lej9u4g4.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox