2013/9/27 LRN :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 27.09.2013 02:20, Kai Tietz wrote:
>> Sure, this library seems to be missed.
>>
>> Please provide a patch, which just adds the missing files, and doesn't
>> touch other lines without need (whitespace changes?).
> AFAICS, the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27.09.2013 02:20, Kai Tietz wrote:
> Sure, this library seems to be missed.
>
> Please provide a patch, which just adds the missing files, and doesn't
> touch other lines without need (whitespace changes?).
AFAICS, the patch that was sent to the ML
Sure, this library seems to be missed.
Please provide a patch, which just adds the missing files, and doesn't
touch other lines without need (whitespace changes?).
Kai
--
October Webinars: Code for Performance
Free Intel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25.09.2013 21:45, Stephen Kitt wrote:
> Hi,
>
> Revision 6256 dropped libvfw32.a, the following patch restores it (I fixed
> mingw-w64-crt/lib32/Makefile.am and regenerated the Makefile.in).
>
> The patch also applies to stable (v3.0.0).
I confirm
On 9/26/2013 21:16, JonY wrote:
> On 9/26/2013 21:07, JonY wrote:
>> On 9/26/2013 18:47, Noboru Uchida wrote:
>>> When I try the following:
>>>
>>> $ echo "#include " >foo.cc && c++ -c foo.cc
>>>
>>> I get tons of redefinition errors on Interlocked functions in winbase.h.
>>>
>>
>> Looks like it ha
On 9/26/2013 21:07, JonY wrote:
> On 9/26/2013 18:47, Noboru Uchida wrote:
>> When I try the following:
>>
>> $ echo "#include " >foo.cc && c++ -c foo.cc
>>
>> I get tons of redefinition errors on Interlocked functions in winbase.h.
>>
>
> Looks like it happens only in C++ mode.
>
Adding mingw-w
2013/9/26 Frédéric Bron
> Hi,
>
> Thanks for the links.
>
> > Why do you think you need to build everything yourself?
> > There are many pre-packaged binaries available from the MinGW-w64
> download
> > page. Please use those if you don't know the answer to this question ;-)
>
> I have built ming
Hi,
Thanks for the links.
> Why do you think you need to build everything yourself?
> There are many pre-packaged binaries available from the MinGW-w64 download
> page. Please use those if you don't know the answer to this question ;-)
I have built mingw-w64 cross-compilers on RedHat Entreprise
2013/9/26 Ruben Van Boxem:
> Hi Frédéric,
>
> There are various projects' sources that need to be built and combined when
> building GCC. This includes GMP, MPFR, MPC, binutils, GCC, MinGW-w64,
> winpthreads, libiconv. These need to be built in a certain order and with a
> certain directory layout.
Hi Frédéric,
There are various projects' sources that need to be built and combined when
building GCC. This includes GMP, MPFR, MPC, binutils, GCC, MinGW-w64,
winpthreads, libiconv. These need to be built in a certain order and with a
certain directory layout.
To see the basics of how this works,
This page
http://sourceforge.net/apps/trac/mingw-w64/wiki/Native%20Win64%20compiler
says that to build a native win64 compiler, a winsup/mingw directory
must be created :
"Before you can start the building process a winsup directory is
necessary in the gcc root directory. Enter the gcc/gcc director
11 matches
Mail list logo
