user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Konstantin Ryabitsev <>
Subject: Re: [PATCH 0/4] CentOS 7 fixes + fix Gcf2 everywhere
Date: Thu, 29 Sep 2022 19:40:20 +0000	[thread overview]
Message-ID: <20220929194020.M77149@dcvr> (raw)
In-Reply-To: <20220929191022.qedjevbodrkakzxh@meerkat.local>

Konstantin Ryabitsev <> wrote:
> On Thu, Sep 29, 2022 at 05:48:27PM +0000, Eric Wong wrote:
> > A bunch of CentOS 7.x fixes noted by Konstantin
> > I also just noticed I broke Gcf2 everywhere :x
> The tests pass now, thanks!
> I still noticed this error (master + this series):
>     1 at /home/mricon/public-inbox/blib/lib/PublicInbox/ line 445.
>     (repeated a bunch of times)

OK, so that's the "do {" line in a do/while loop for send_cmd4, right?

What's before and after?  Which *.t is that coming from?

This is single-process "make test"?

I'm not seeing where that warning is coming from at all...
Removing Inline::C and ~/.cache/public-inbox/inline-c doesn't
make the warning appear, either.

Of course I don't have Socket::MsgHdr installed on CentOS 7,
either, since it's not available via yum.

  reply	other threads:[~2022-09-29 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 18:46 "make test" for 1.9.0 on centos-7 Konstantin Ryabitsev
2022-09-28 19:59 ` Eric Wong
2022-09-28 20:51   ` Konstantin Ryabitsev
2022-09-29 17:48     ` [PATCH 0/4] CentOS 7 fixes + fix Gcf2 everywhere Eric Wong
2022-09-29 17:48       ` [PATCH 1/4] syscall: initialize buffer for vec() Eric Wong
2022-09-29 17:48       ` [PATCH 2/4] treewide: use --globoff with curl(1) Eric Wong
2022-09-29 17:48       ` [PATCH 3/4] gcf2: fix syntax error and require PublicInbox::Git Eric Wong
2022-09-29 17:48       ` [PATCH 4/4] tests: no IPv6 on old Net::NNTP, Mail::IMAPClient, HTTP::Tiny Eric Wong
2022-09-29 19:10       ` [PATCH 0/4] CentOS 7 fixes + fix Gcf2 everywhere Konstantin Ryabitsev
2022-09-29 19:40         ` Eric Wong [this message]
2022-09-29 17:54 ` "make test" for 1.9.0 on centos-7 Eric Wong

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220929194020.M77149@dcvr \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).