public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Increase _FORTIFY_SOURCE level from 2 to 3 in CFLAGS
Date: Sun, 11 Feb 2024 17:04:15 +0000	[thread overview]
Message-ID: <0f4b19fc-2e20-4ffd-aa32-56d5abe95b47@dronecode.org.uk> (raw)
In-Reply-To: <79fbabcb-5e29-32e9-9543-70b8198a6e8c@t-online.de>

On 04/02/2024 16:30, Christian Franke via Cygwin-apps wrote:
> Jon Turney wrote:
>> On 02/02/2024 16:13, Christian Franke via Cygwin-apps wrote:
>>> _FORTIFY_SOURCE=3 is supported by Cygwin 3.5.0 headers and Cygwin gcc 
>>> 13.2.1 test release.
>>>
>>> Silently falls back to level 2 if level 3 is unsupported (older 
>>> headers or gcc) or to level 0 if unsupported at all (C++, clang).
>>
>> Thanks. I applied this.
>>
>> I'm thinking I want to try to do another cygport release fairly 
>> soonish, so please feel free to remind me about any other patches by 
>> you (or others) which I need to look at before then.
>>
> 
> Possibly some initial SOURCE_DATE_EPOCH support:
> https://sourceware.org/pipermail/cygwin-apps/2023-August/043108.html

I've applied this (and I think I might have caught up on most of the 
pending patches...)

It would be nice to have some sort of test, since there's no coverage 
with SOURCE_DATE_EPOCH defined at the moment.

Even if we just verify that an existing test continues to build without 
problems with it defined, that would be a good start, let alone 
verifying that it actually sets timestamps as expected...


  reply	other threads:[~2024-02-11 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 16:13 Christian Franke
2024-02-04 15:43 ` Jon Turney
2024-02-04 16:30   ` Christian Franke
2024-02-11 17:04     ` Jon Turney [this message]
2024-04-28 10:21 ` ASSI
2024-04-28 12:21   ` Christian Franke
2024-04-30 22:19     ` Jon Turney

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=0f4b19fc-2e20-4ffd-aa32-56d5abe95b47@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.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).