https://bugs.winehq.org/show_bug.cgi?id=53392
--- Comment #5 from malic malicorne@chez.com --- (In reply to Zeb Figura from comment #4)
(In reply to malic from comment #3)
I understand. What are my options there apart from digging and removing all the fno-PIC ?
Is there a reason you need -fPIC? As stated, Windows programs really do need -fno-PIC, so the ideal solution would be to compile with -fno-PIC.
The reason I need -fPIC is on the description of the "bug" : ld: fatal: relocations remain against allocatable but non-writable sections Which is worked around or fixed by using -fPIC
Is the behaviour supposed to be the same for x64 ?
We use -fPIC on all architectures other than i386.
So compiling with -m64 should do the trick ? I guess nowadays we should not even think about compiling without -m64