OK, I have updated a bit the question via a comment underneath. Basically Config suggests -Wp,-D_FORTIFY_SOURCE=2 for CFLAGS. Correct me if I am wrong here but it's not its responsibility to tell me what security my C code (embeding Perl) should have. *Especially* when it breaks debugging. So I was wrong to think that Perl suggests an optimisation flag, instead it suggests a source-fortification (wow) flag which requires the optimisation flag which breaks debug. Isn't it the norm that CFLAGS/LDFLAGS suggestions (via pkg-config for example) should never suggest any optimisation for linking to an existing library? That's the user's choice. No?
That's why I considered it a bug (and still do). But hey, I am a bit strict sometimes :).
Didn't know Fakeconfig, thanks. But this is entirely a C project and I am using Autotools for it.
thanks
In reply to Re^2: Config sets optimisation compilation flags (-O/-g)!
by bliako
in thread Config sets optimisation compilation flags (-O/-g)!
by bliako
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |