Re: Hot to test for _FORTIFY_SOURCE with Autoconf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jeffrey Walton <noloader@xxxxxxxxx>
Subject: Re: Hot to test for _FORTIFY_SOURCE with Autoconf
From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
Date: Wed, 18 Mar 2020 00:11:33 +0000
Cc: gcc-help <gcc-help@xxxxxxxxxxx>
In-reply-to: <CAH8yC8mPoWcb_P4CuzAisV+=ozVOKK8r3ZtxGxsJ5eYyuSZsqQ@mail.gmail.com>
References: <CAH8yC8mPoWcb_P4CuzAisV+=ozVOKK8r3ZtxGxsJ5eYyuSZsqQ@mail.gmail.com>
Reply-to: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>

On Tue, 17 Mar 2020 at 22:15, Jeffrey Walton via Gcc-help
<gcc-help@xxxxxxxxxxx> wrote:
>
> I'm trying to test for availability of _FORTIFY_SOURCE=2.

What does that mean?

If you mean you're trying to test whether setting that has any effect,
that's determined by Glibc not GCC.

Follow-Ups:
- Re: Hot to test for _FORTIFY_SOURCE with Autoconf
  - From: Jeffrey Walton via Gcc-help

References:
- Hot to test for _FORTIFY_SOURCE with Autoconf
  - From: Jeffrey Walton via Gcc-help

Prev by Date: Hot to test for _FORTIFY_SOURCE with Autoconf
Next by Date: Re: Hot to test for _FORTIFY_SOURCE with Autoconf
Previous by thread: Hot to test for _FORTIFY_SOURCE with Autoconf
Next by thread: Re: Hot to test for _FORTIFY_SOURCE with Autoconf
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux