Closed wxlg1117 closed 4 years ago
Here is a patch that fixes this issue: https://github.com/vincentkfu/fio/commit/23c6037b216e45d5de174e1e8921dbe9b646af53
I was going to do some more testing to make sure that the problem wasn't just with my setup but now you have confirmed that it isn't just me.
@vincentkfu How come this doesn't turn up on CI? Is this only with new mingw installs?
@vincentkfu How come this doesn't turn up on CI? Is this only with new mingw installs?
yes !!! before build fio.exe i upgrade cygwin to the latest version use "setup-x86_64.exe --root d:\cygwin64 -q --upgrade-also "
@sitsofe I wondered about that too and was planning to investigate more. The bug report linked in the commit message says that this issue appeared in the middle of October. So my guess is that appveyor is using a mingw install from earlier than that.
OK there's lots of talk about this over on https://github.com/msys2/MINGW-packages/issues/5803 too. I guess the only question is whether to change the link flag or use something like -fstack-protector-all
...
@vincentkfu The mozilla folks (https://bugzilla.mozilla.org/show_bug.cgi?id=1601701 and https://hg.mozilla.org/releases/mozilla-esr68/rev/c677377208c2 ) seem to have taken the -lssp
route when using llvm-mingw too so it looks like what you've got is a sensible direction to go.
@wxlg1117 I assume @vincentkfu's patch fixes the issue for you?
@wxlg1117 I assume @vincentkfu's patch fixes the issue for you?
yes, it's perfect .
how to fix it ? or anybody can help me how to build fio.exe x64 in linux system..