This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

x86_64-pc-mingw32


I built a cross compiler, i.e., x86_64-pc-mingw32-gcc (release 4.1.2, I
modified ASM when necessary) on a x86_64-linux, and then I applied
x86_64-pc-mingw32-gcc to generate binaries of w32api (3.8) and mingw-runtime
(3.11, I modified ASM when necessary). Reference is inconsistent. For
example, the WINAPI EnterCriticalSection is labeled as
EnterCriticalSection@4 in library of w32api, but is labeled as
EnterCriticalSection@8 in runtime library. It seems w32api is in 32-bit, and
runtime is in 64-bit. Linker x86_64-pc-mingw32-ld fails to find the
references. Is there any way to resolve it? Thank you.

So far, the corss compiler I built can generate object code and built
library, but cannot build windows executable.

Thank you again.
-- 
View this message in context: http://www.nabble.com/x86_64-pc-mingw32-tf3331275.html#a9262940
Sent from the gcc - Help mailing list archive at Nabble.com.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]