From: David Aguilar <davvid@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13)
Date: Sat, 15 Jan 2022 18:15:10 -0800 [thread overview]
Message-ID: <CAJDDKr61fZhSOmEYzwzMgmsR7e84SwpJJ9==NV-4aepAKp2u8w@mail.gmail.com> (raw)
In-Reply-To: <xmqqo84c4xqh.fsf@gitster.g>
On Sat, Jan 15, 2022 at 11:15 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> David Aguilar <davvid@gmail.com> writes:
>
> > I ran into the c99 test balloon. I get the (expected?) c99 build
> > errors and an uncompress2 build error with RHEL7.9's stock gcc 4.8.5.
> >
> > Are we dropping support for RHEL7.9?
>
> No. Our expectation is that those who care about various distros
> and platforms supply patches like ...
>
> > Using NO_UNCOMPRESS2=YesPlease and CFLAGS += -std=c99 in config.mak
>
> ... this, but not locallly but to config.mak.uname, to help the
> users and builders on their favorite systems. It is better done
> sooner rather than later.
>
> > works but I'm not sure if we actually expect users to deal with those
> > details themselves.
>
> Users would not have to, as long as somebody else on the list uses
> the smea system as theirs cares enough to supply such patches to
> config.mak.uname.
>
> > Sorry for being out of the loop on the plan for older toolchains, but
> > I wasn't sure if we should be expecting a patch that configures the
> > default flags so that things build out of the box again or if this is
> > considered the new status quo and we're okay regressing?
>
> Obviously the former. This is a team effort and everybody who finds
> new issues is very appreciated to chip in.
>
Thanks for verifying; patch sent. A simple $(uname_R) check worked for me
so hopefully that's not too much cruft to carry around for a few years.
cheers,
--
David
prev parent reply other threads:[~2022-01-16 2:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 0:48 What's cooking in git.git (Jan 2022, #03; Thu, 13) Junio C Hamano
2022-01-14 4:18 ` Junio C Hamano
2022-01-14 16:27 ` Elijah Newren
2022-01-14 19:47 ` Junio C Hamano
2022-01-14 21:49 ` Elijah Newren
2022-01-14 22:03 ` Junio C Hamano
2022-01-14 22:18 ` Junio C Hamano
2022-01-14 18:12 ` Ævar Arnfjörð Bjarmason
2022-01-17 7:18 ` Patrick Steinhardt
2022-01-14 15:44 ` Mistakes in the stalled category? (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13)) Elijah Newren
2022-01-14 23:32 ` Mistakes in the stalled category? Junio C Hamano
2022-01-14 23:49 ` Junio C Hamano
2022-01-15 19:38 ` Junio C Hamano
2022-01-18 16:11 ` Derrick Stolee
2022-01-14 15:54 ` en/present-despite-skipped & en/remerge-diff (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13)) Elijah Newren
2022-01-14 19:39 ` tb/midx-bitmap-corruption-fix (was: " Taylor Blau
2022-01-15 16:45 ` What's cooking in git.git (Jan 2022, #03; Thu, 13) David Aguilar
2022-01-15 19:15 ` Junio C Hamano
2022-01-16 2:15 ` David Aguilar [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJDDKr61fZhSOmEYzwzMgmsR7e84SwpJJ9==NV-4aepAKp2u8w@mail.gmail.com' \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).