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

Re: [PATCH] merge-file: fix build warning with gcc 4.8.5

From
Jeff King <peff@peff.net>
Date
Jul 30, 2022, 01:40 UTC
Message-ID
<YuSL/2N29cCy9Dzd@coredump.intra.peff.net>
In-Reply-To
<YuR5Jado2LrtZUjP@danh.dev>
On Sat, Jul 30, 2022 at 07:19:49AM +0700, Đoàn Trần Công Danh wrote:
Show 8 quoted lines
> > Tested on a debian jessie chroot using gcc-4.8 and 4.9. Though note that
> > you also need to manually specify -std=gnu99 to get it to work at all
> > with those compilers these days! So I kind of wonder if it's even worth
> > catering to their warnings automatically.
> 
> Well, config.mak.uname automatically adds -std=c99 for RHEL 7 and
> CentOS7. Can we add the same things for Debian? Or should we just
> remove both?

Ah, I didn't know about that. No, I don't think there's any reason to remove them. If people are able to compile out of the box there, then my patch to config.mak.dev may be worth doing.

As far as adding a similar config.mak.uname thing for Debian, I don't have a strong opinion. Jessie is far beyond being supported, so I'd probably wait to see if somebody who actually cares proposes a patch.

-Peff
Previous: Đoàn Trần Công DanhNext: brian m. carlson
Message 9 of 11 in “merge-file: fix build warning with gcc 4.8.5”
  1. merge-file: fix build warning with gcc 4.8.5Đoàn Trần Công Danh, Jul 29, 2022
  2. Junio C HamanoJul 29, 2022
  3. Jeff KingJul 29, 2022
  4. Jeff KingJul 29, 2022
  5. Eric SunshineJul 29, 2022
  6. Jeff KingJul 29, 2022
  7. Junio C HamanoJul 29, 2022
  8. Đoàn Trần Công DanhJul 30, 2022
  9. Jeff KingJul 30, 2022
  10. brian m. carlsonJul 30, 2022
  11. Jeff KingJul 30, 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.