From: chrubis@suse.cz
To: Mike Frysinger <vapier@gentoo.org>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] RFC add _FORTIFY_SOURCE to default LTP CFLAGS
Date: Wed, 28 Aug 2013 13:56:01 +0200 [thread overview]
Message-ID: <20130828115601.GA4804@rei> (raw)
In-Reply-To: <201308271218.22009.vapier@gentoo.org>
Hi!
>
> unfortunately that does not work. this snippet from coreutils is probably
> better:
> AH_VERBATIM([FORTIFY_SOURCE],
> [/* Enable compile-time and run-time bounds-checking, and some warnings,
> without upsetting glibc 2.15+. */
> #if !defined _FORTIFY_SOURCE && defined __OPTIMIZE__ && __OPTIMIZE__
> # define _FORTIFY_SOURCE 2
> #endif
> ])
That wouldn't work here, as config.h is included only in a few testcases
(in these that actually use some of the defines there).
But given that this just copies some ifdefs into config.h what about
adding the snippet directly into compiler.h that is included from
test.h thus ends up in all testcases?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-08-28 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 11:00 [LTP] RFC add _FORTIFY_SOURCE to default LTP CFLAGS chrubis
[not found] ` <201308242143.45598.vapier@gentoo.org>
2013-08-27 11:04 ` chrubis
[not found] ` <201308271218.22009.vapier@gentoo.org>
2013-08-28 11:56 ` chrubis [this message]
[not found] ` <201308281234.41447.vapier@gentoo.org>
2013-08-28 16:37 ` Mike Frysinger
2013-09-02 12:23 ` chrubis
2013-09-02 14:27 ` chrubis
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=20130828115601.GA4804@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.org \
/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