From: Edgar Bonet <bonet@grenoble.cnrs.fr>
To: Arnout Vandecappelle <arnout@mind.be>, buildroot@buildroot.org
Cc: Samuel Martin <s.martin49@gmail.com>
Subject: Re: [Buildroot] Nginx fails to build with GCC 14
Date: Thu, 16 May 2024 10:38:10 +0200 [thread overview]
Message-ID: <a7168f66-76c7-42e0-b1e2-c82b821695f5@grenoble.cnrs.fr> (raw)
In-Reply-To: <d0cbd392-35af-4501-9703-d9d79db2a984@mind.be>
Hello Arnout, all!
> the patch should have an Upstream: tag with the URL of the PR or
> whatever you made to send the patch upstream.
OK. I guess I will have to learn some basic mercurial commands, as the
Nginx developers expect patches to be submitted in “HG changeset patch”
format...
> > ++ ngx_feature_test="volatile size_t n = 0;
>
> The interface actually defines it as AO_t, so perhaps use that instead
> of volatile size_t?
Oh right! I hadn't even checked the API. Will use AO_t.
Thanks!
Edgar.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-16 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 20:28 [Buildroot] Nginx fails to build with GCC 14 Edgar Bonet
2024-05-15 15:31 ` Edgar Bonet
2024-05-15 19:19 ` Arnout Vandecappelle via buildroot
2024-05-16 8:38 ` Edgar Bonet [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7168f66-76c7-42e0-b1e2-c82b821695f5@grenoble.cnrs.fr \
--to=bonet@grenoble.cnrs.fr \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=s.martin49@gmail.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.
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).