On 2019-04-23 04:09 +0100, Ken Moffat via lfs-dev wrote: > On Thu, Apr 18, 2019 at 10:59:04PM +0100, Ken Moffat wrote: > > I was looking through my logs to identify which packages do not use > > my CFLAGS, CXXFLAGS (thinking about trying LTO at some point) and > > reading the voluminous output from perl's Configure I noticed: > > > > Guessing which symbols your C compiler and preprocessor define... > > You seem not to have gcc 4.* or later, not adding -D_FORTIFY_SOURCE. > > > > That is because 5.28.1 has the following: > > > > case "$gccversion" in > > [4567].*) case "$optimize$ccflags" in > > > > Using > > sed -i 's/^\(\[4567\)/\18/' Configure > > gives me > > > > Guessing which symbols your C compiler and preprocessor define... > > Adding -D_FORTIFY_SOURCE=2 to ccflags... > > > > ĸen > > This still applies to 5.28.2. I guess that distros such as fedora > and Arch have not reported this upstream because they *always* force > their own CFLAGS which include a -DFORTIFY_SOURCE setting.
I've reported this (several months ago): https://rt.perl.org/Public/Bug/Display.html?id=133490 And they've fixed it in dev branch. They just didn't backport this into 5.28.x. -- Xi Ruoyao <xry...@mengyan1223.wang> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
