From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: FORTIFY_SOURCE
Date: Sun, 15 Apr 2018 18:39:00 -0000 [thread overview]
Message-ID: <87o9ik5n70.fsf@Rainer.invalid> (raw)
Perl and Cygwin do not exactly play together at the moment, but I
haven't been able to track down where that happens. Perl configure
recognizes FORTIFY_SOURCE=2 proceeds to integrate that knowledge into
Config_heavy.pl. For whatever reason it decded to use
"-Wp,-D_FORTIFY_SOURCE=2" to do that (which works just fine). But when
compiling something through ExtUtils::Embed in the just built perl that
option suddenly ends up as just "-Wp," and hangs up the compiler. If I
rename the defined symbol to "FORCIFY_SOURCE" then it stays in the call
to gcc, so it's specific to that symbol.
I think that's happening somewhere in ExtUtils, but I'd like to ask if
maybe there is some magic going on from the Cygwin / gcc side to remove
that definition?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next reply other threads:[~2018-04-15 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 18:39 Achim Gratz [this message]
2018-04-15 18:51 ` FORTIFY_SOURCE Achim Gratz
2018-04-15 19:00 ` FORTIFY_SOURCE Brian Inglis
2018-04-15 19:08 ` FORTIFY_SOURCE Achim Gratz
2018-04-15 19:59 ` FORTIFY_SOURCE Brian Inglis
2018-04-16 17:42 ` FORTIFY_SOURCE Achim Gratz
2018-04-16 21:14 FORTIFY_SOURCE Richard Campbell
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=87o9ik5n70.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).