From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: "Calvin Wan" <calvinwan@google.com>,
"Jonathan Tan" <jonathantanmy@google.com>,
"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: What's cooking in git.git (May 2024, #04; Thu, 9)
Date: Thu, 09 May 2024 18:04:59 -0700 [thread overview]
Message-ID: <xmqq5xvmschw.fsf@gitster.g> (raw)
In-Reply-To: <xmqqfruqsjb6.fsf@gitster.g> (Junio C. Hamano's message of "Thu, 09 May 2024 15:37:49 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> * cw/git-std-lib (2024-02-28) 4 commits
> - SQUASH??? get rid of apparent debugging crufts
> - test-stdlib: show that git-std-lib is independent
> - git-std-lib: introduce Git Standard Library
> - pager: include stdint.h because uintmax_t is used
>
> Split libgit.a out to a separate git-std-lib tor easier reuse.
>
> Expecting a reroll.
> source: <cover.1696021277.git.jonathantanmy@google.com>
Just a heads-up. The topic is pushed out of 'seen', as it seems to
be hated by osx-* jobs when linking programs. As the topic has been
expecting a reroll for some time, it is not ultra urgent to fix
this, but before resurrecting it, we may want to look into it.
https://github.com/git/git/actions/runs/9023837489
is an example run where we see error messages like:
ld: warning: ignoring duplicate libraries: 'git-std-lib.a', 'libgit.a', 'reftable/libreftable.a', 'xdiff/lib.a'
and
ld: Undefined symbols:
_git_config_get_bool, referenced from:
_precompose_string_if_needed in git-std-lib.a[11](precompose_utf8.o)
in both clang and gcc jobs.
We did not see these breakages before, and we do not see these
breakages in today's 'seen' with this topic excluded. I haven't
tried to include this but excluding tb/precompose-getcwd topic
instead, which I suspect might also work.
Thanks.
next prev parent reply other threads:[~2024-05-10 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 22:37 What's cooking in git.git (May 2024, #04; Thu, 9) Junio C Hamano
2024-05-10 1:04 ` Junio C Hamano [this message]
2024-05-10 6:32 ` Torsten Bögershausen
2024-05-10 7:54 ` Patrick Steinhardt
2024-05-10 15:35 ` Junio C Hamano
2024-05-10 16:19 ` Patrick Steinhardt
2024-05-10 18:39 ` Justin Tobler
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=xmqq5xvmschw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=calvinwan@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=tboegi@web.de \
/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.