gcc linker error: undefined reference to `__security_cookie' when building with gcc 8.5.0 based MinGW-w64 release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DC++ |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
Trying to build DC++ with https:/
Got multiple " undefined reference to `__security_
https:/
It says you either need to link bufferoverflowU.lib or build without the /GS switch.
<https:/
summary: |
gcc linker error: undefined reference to `__security_cookie' when - building with gcc 8.5.0 basedMinGW-w64 release + building with gcc 8.5.0 based MinGW-w64 release |
[09:24:34] <eMTee> https:/ /sourceforge. net/p/mingw- w64/mailman/ message/ 36804945/ "* __FORTIFY_SOURCE support " /github. com/StephanTLav avej/mingw- distro/ issues/ 71 , https:/ /github. com/msys2/ MINGW-packages/ issues/ 5803 protector' , '-fno-stack- clash-protectio n', '-D_FORTIFY_ SOURCE= 0' , still errors
[09:40:16] <eMTee> https:/
[11:39:11] <eMTee> meh, it's not because of these. I tried '-fstack-check=no', '-fno-stack-check', '-fno-stack-
[14:16:20] <eMTee> managed to compile it by adding 'BufferOverflowU' lib from the SDK. Altough some fix it by using dummy defines like https:/ /github. com/kfrlib/ fft-benchmark/ blob/master/ mingw_fix. h
I tried
extern "C" {
int __security_cookie;
}
with no luck, not sure if I added it to the proper place though.
[14:17:37] <eMTee> I still want to know what option to disable or what was enabled vs. the old 8.1 build we've been using but I'm at a loss how to find it out what it is. practice.
[14:18:39] <eMTee> Nevertheless these checks should make the app more safe, not sure to what extent though since it's a 20 year old technology/
Will try a similar winlibs built compiler which reportedly don't exhibit this issue with its defaults.