All of lore.kernel.org
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: 2.54.0-rc1 NO_WRITEV=Nope  does not work
Date: Thu, 9 Apr 2026 15:48:16 -0400	[thread overview]
Message-ID: <028901dcc859$d2419470$76c4bd50$@nexbridge.com> (raw)

With a completely clean build, we are getting writev() being used anyway on
NonStop:

/usr/coreutils/bin/make NO_TCLTK=NoThanks NO_WRITEV=Nope V=1
prefix=/usr/local-ssl3.5 CFLAGS=-g -O2 -D_LARGEFILE64_SOURCE=1
-D_FILE_OFFSET_BITS=64 -Winline -I/usr/local-ssl3.5/include
-I/usr/coreutils/include -I/usr/tandem/xml/T0625L01_AAE/include
LDFLAGS=-D_LARGEFILE64_SOURCE=1 -D_FILE_OFFSET_BITS=64
/usr/coreutils/lib/libz.a -L/usr/local-ssl3.5/lib -L/usr/coreutils/lib
-L/usr/tandem/xml/T0625L01_AAE/lib SHELL=/usr/coreutils/bin/bash
GIT_VERSION=2.54.0.rc1

Down to the first instance:

Cloning into bare repository 'clone.git'...
remote: Enumerating objects: 629, done.
fatal: writev error: Invalid function argument
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
not ok 25 - clone from bitmapped repository
#
#                       rm -fr clone.git &&
#                       git clone --no-local --bare . clone.git &&
#                       git rev-parse HEAD >expect &&
#                       git --git-dir=clone.git rev-parse HEAD >actual &&
#                       test_cmp expect actual
#

Did I mess this up?

--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.



             reply	other threads:[~2026-04-09 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 19:48 rsbecker [this message]
2026-04-09 21:10 ` 2.54.0-rc1 NO_WRITEV=Nope does not work Jeff King
2026-04-09 21:53   ` Re* " Junio C Hamano
2026-04-09 22:21     ` Jeff King
2026-04-09 22:31       ` Junio C Hamano
2026-04-10  4:57         ` Patrick Steinhardt

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='028901dcc859$d2419470$76c4bd50$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.