git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Jan 2022, #03; Thu, 13)

From
David Aguilar <davvid@gmail.com>
Date
Jan 16, 2022, 02:15 UTC
Message-ID
<CAJDDKr61fZhSOmEYzwzMgmsR7e84SwpJJ9==NV-4aepAKp2u8w@mail.gmail.com>
In-Reply-To
<xmqqo84c4xqh.fsf@gitster.g>
On Sat, Jan 15, 2022 at 11:15 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 32 quoted lines
>
> 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
Previous: Junio C Hamano
Message 19 of 19 in “What's cooking in git.git (Jan 2022, #03; Thu, 13)”
  1. Junio C HamanoJan 14, 2022
  2. Junio C HamanoJan 14, 2022
  3. Elijah NewrenJan 14, 2022
  4. Junio C HamanoJan 14, 2022
  5. Elijah NewrenJan 14, 2022
  6. Junio C HamanoJan 14, 2022
  7. Junio C HamanoJan 14, 2022
  8. Ævar Arnfjörð BjarmasonJan 14, 2022
  9. Patrick SteinhardtJan 17, 2022
  10. Mistakes in the stalled category? (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Elijah Newren, Jan 14, 2022
  11. Junio C HamanoJan 14, 2022
  12. Junio C HamanoJan 14, 2022
  13. Junio C HamanoJan 15, 2022
  14. Derrick StoleeJan 18, 2022
  15. en/present-despite-skipped & en/remerge-diff (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Elijah Newren, Jan 14, 2022
  16. tb/midx-bitmap-corruption-fix (was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Taylor Blau, Jan 14, 2022
  17. David AguilarJan 15, 2022
  18. Junio C HamanoJan 15, 2022
  19. David AguilarJan 16, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.