After removing _FORTIFY_SOURCE=2 from CPPFLAGS in pacmans scripts
ncurses builds again,
no need for libssp either unless you actually want stack smashing
protection.
Seems some recent change in the runtime libraries causes this flag to
break stuff :/
it also caused python2 to fail building with an obscure segmentation
fault error in the 32 bit build.
Den 17-09-2019 kl. 11:06 skrev Liu Hao:
在 2019/9/17 15:18, ralph engels 写道:
It is set in the makepkg scripts in /etc.
Does -fstack-protector-all or -fstack-protector-strong work ?.
`-fstack-protector-strong` didn't work. I didn't try `-all`.
linking directly to libssp should not be nessesary if the build chain
works as it should.
Then probably this `_FORTIFY_SOURCE` thing should be disabled when
building GCC. Prior to recent patches it had no effect, so there is no
loss by disabling it.
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
