for 32-bit compiles only using 64-bit compiler (using -m32) I get
mingw32/bin/ld.exe: i386:x86-64 architecture of input file
`32\diskgeometry.manifest.res' is incompatible with i386 output
collect2.exe: error: ld returned 1 exit status
Q:
- is there something special I need to do for -l switch
2014/1/18 Jim Michaels jmich...@yahoo.com
for 32-bit compiles only using 64-bit compiler (using -m32) I get
mingw32/bin/ld.exe: i386:x86-64 architecture of input file
`32\diskgeometry.manifest.res' is incompatible with i386 output
collect2.exe: error: ld returned 1 exit status
Q:
- is
I guess I misunderstood. I have used plugins in *applications* developed
with gcc in mingw-w64. I really haven't looked into plugins used directly
by gcc. Of that I am ignorant.
sorry.
2014/1/16 xunxun xunxun1...@gmail.com
于 2014/1/17 星期五 6:45, Edscott Wilson 写道:
I've used plugins fairly
This patch never got applied. Could someone please apply?
Thanks
Lars
On Mon, Dec 30, 2013 at 9:54 AM, Kai Tietz ktiet...@googlemail.com wrote:
Patch is ok for trunk.
Thanks,
Kai
2013/12/30 Lars Munch l...@segv.dk:
This patch adds wmilib for use with the DDK wmilib.h header. The .def
hmm. there seems to be a problem with 64-bit windres always making 64-bit .res
files regardless of -m32, and windows 7 is complaining.
there are no windres switches to change this.
From: Ruben Van Boxem vanboxem.ru...@gmail.com
To:
On Sat, Jan 18, 2014, Jim Michaels wrote:
hmm. there seems to be a problem with 64-bit windres always making 64-bit
.res files regardless of -m32, and windows 7 is complaining.
there are no windres switches to change this.
IMHO (well, and others think the same), multilib is a nice thing but
2014/1/18 Jim Michaels jmich...@yahoo.com
hmm. there seems to be a problem with 64-bit windres always making 64-bit
.res files regardless of -m32, and windows 7 is complaining.
there are no windres switches to change this.
Only the GCC compiler driver understands -m32/-m64. But the windres
I take that back.
supported targets: pe-x86-64 pei-x86-64 elf64-x86-64 elf64-l1om elf64-k1om
pe-i386 pei-i386 elf32-i386 elf64-little elf64-big elf32-little elf32-big srec
symbolsrec verilog tekhex binary ihex
so which one do I use for win64 and which one for win32? my guess is one of the
pe
Hi,
As previously announced, I am writing Clang Driver code so it directly
calls as/ld instead of delegating that to GCC.
I am nearly finished, with just one issue remaining. If I have this test
code:
#include stdio.h
int main()
{
printf(Hello World!\n);
}
and I run
$ i686-w64-mingw32-gcc
The LoadLibrary API calls the DLL's entry point. You can use it to check if
the DLL is working.
This simple snippet correctly printed the Hello World from the dll.
#include windows.h
int main() {
LoadLibrary(test.dll);
return 0;
}
On 1/18/2014 22:13, Lars Munch wrote:
This patch never got applied. Could someone please apply?
Thanks
Lars
Done with trunk r6444.
signature.asc
Description: OpenPGP digital signature
--
CenturyLink Cloud: The
all is well. discovered where the 32-bit DLLs were in 64-bit cvompiler using
dir/s/b *.dll and now all is working well.
thanks for the help.
From: Jim Michaels jmich...@yahoo.com
To: mingw-w64-public@lists.sourceforge.net
mingw-w64-public@lists.sourceforge.net
12 matches
Mail list logo
