2013/6/4 zhangxinghai
> hello
> I have just succeeded in building wx 2.9.4 with tdm-gcc-64 4.7.1-3,I'm
> very glad.Thanks for all help.
> I invoke the command
> mingw32-make -f makefile.gcc -j4 BUILD=release SHARED=1 MONOLITHIC=0
> UNICODE=1 CXXFLAGS="-m32 -pipe -fno-keep-inline-dllexport -Os"
On Tue, Jun 4, 2013 at 1:58 AM, dw wrote:
>
>> If you can prepare patches for your recent asm stuff against the stable
>> branch, I would happily merge.
>
> It might make sense to hold off on this a bit. I have several more that I'm
> working on.
>
OK,
> Also, I hate asking questions that expos
I suggest not to use multiple lib gcc here, unless you know -m32
*windres*needs -F pe-i386.
You can choose one gcc with only x86 or x64.
On Tue, Jun 4, 2013 at 11:23 AM, zhangxinghai wrote:
> hello
> I have just succeeded in building wx 2.9.4 with tdm-gcc-64 4.7.1-3,I'm
> very glad.Thanks for
hello
I have just succeeded in building wx 2.9.4 with tdm-gcc-64 4.7.1-3,I'm very
glad.Thanks for all help.
I invoke the command
mingw32-make -f makefile.gcc -j4 BUILD=release SHARED=1 MONOLITHIC=0 UNICODE=1
CXXFLAGS="-m32 -pipe -fno-keep-inline-dllexport -Os" LDFLAGS=-m32
CFLAGS=-m32 RCFLAG
>> I think option #3 is that one I prefer too. Just one thing about
>> SSE-instruction. For 64-bit we can assume that SSE has to be present
>> in any case. Just for 32-bit we should check in headers for the
>> __SSE__ macro, and in the intrinsic-function (none-inline) we should
>> default to no
Hi,
I've uploaded a new version of that page:
http://notk.org/~adrien/picker.php
As you'll see, quite a lot of things have changed and the page should
feel lighter and more intuitive. Some of the new data isn't completely
right and there are a few cosmetics change to do. Apart from that, I
hope
Hello,
zhangxinghai,
As I remember it is possible to compile wxWidgets library with Ruben's
toolchain on MSYS. At the end of configure command details of guess
should be correct for 32 bit os.
Regards
--
How ServiceNow
I have this error only on 64-bit Cygwin
2013/6/3 Kai Tietz
> 2013/6/3 Алексей Павлов :
> > Hi, all!
> >
> > When using latest mingw-w64 runtime from trunk for Cygwin I have error:
> > http://pastebin.com/9WVgE1Gu
> >
> > Regards, Alexey.
>
> Hmm, means that Interlocked-Functions getting defined
2013/6/3 Алексей Павлов :
> Hi, all!
>
> When using latest mingw-w64 runtime from trunk for Cygwin I have error:
> http://pastebin.com/9WVgE1Gu
>
> Regards, Alexey.
Hmm, means that Interlocked-Functions getting defined twice with
different prototypes.
Corinna, any idea here?
Regards,
Kai
---
Hi, all!
When using latest mingw-w64 runtime from trunk for Cygwin I have error:
http://pastebin.com/9WVgE1Gu
Regards, Alexey.
--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting t
On 6/3/2013 20:16, Rafaël Carré wrote:
> Le 03/06/2013 13:00, Gunnar a écrit :
>> In MinGW564 the code:
>>
>> #define __STDC_FORMAT_MACROS 1
>> #include
>>
>> ..
>> ..
>>
>> uint64_t i = 0;
>> printf("i = %" PRIu64 "\n", i);
>>
>>
>>
>> leads to a "unknown conversion type character 'l' in format".
On 6/3/2013 22:18, Rafaël Carré wrote:
> new file mode 100644
> index 000..c49fc51
> --- /dev/null
> +++ b/mingw-w64-crt/lib32/runtimeobject.def
> @@ -0,0 +1,25 @@
> +LIBRARY "api-ms-win-core-winrt-string-l1-1-0.dll"
> new file mode 100644
> index 000..c211978
> --- /dev/null
> +++ b/min
2013/6/3 Rafaël Carré :
> ---
> mingw-w64-crt/Makefile.am | 6 +-
> mingw-w64-crt/lib32/runtimeobject.def | 25 +
> mingw-w64-crt/lib64/runtimeobject.def | 29 +
> mingw-w64-headers/include/winstring.h | 202
> ++
> 4 files changed, 260 inse
---
mingw-w64-crt/Makefile.am | 6 +-
mingw-w64-crt/lib32/runtimeobject.def | 25 +
mingw-w64-crt/lib64/runtimeobject.def | 29 +
mingw-w64-headers/include/winstring.h | 202 ++
4 files changed, 260 insertions(+), 2 deletions(-)
create mode
Le 03/06/2013 13:57, Kai Tietz a écrit :
> 2013/6/3 dw :
>> 3) Use code like:
>>
>> __MINGW_INTRIN_INLINE void x__faststorefence(void) {
>>
>> #ifdef __SSE__ // defined by gcc when sse instructions are available
>> asm ("sfence" ::: "memory");
>> #else
>> asm ("lock or %[zero], (%%
Le 03/06/2013 13:00, Gunnar a écrit :
> In MinGW564 the code:
>
> #define __STDC_FORMAT_MACROS 1
> #include
>
> ..
> ..
>
> uint64_t i = 0;
> printf("i = %" PRIu64 "\n", i);
>
>
>
> leads to a "unknown conversion type character 'l' in format". In MiGW32 it
> compiles witout a warning.
>
>
2013/6/3 dw :
> So, a question about __faststorefence. The current implementation in
> winnt.h is incorrect. I have 3 alternates to propose, and which one is
> "best" depends on the goals of the mingw-w64 project. One approach is "just
> do what MSVC does." However, there's also something to be
In MinGW564 the code:
#define __STDC_FORMAT_MACROS 1
#include
..
..
uint64_t i = 0;
printf("i = %" PRIu64 "\n", i);
leads to a "unknown conversion type character 'l' in format". In MiGW32 it
compiles witout a warning.
The command that I use is
x86_64-w64-mingw32-gcc-4.8.0.exe -fexception
>
> > It seems clear to me that you should submit a patch that fixes this to Qt
> > Project, and also if possible file the boost unit_test issue with the
> > mingw-builds project.
> >
> >
> I took the liberty to submit a bug report to the Qt Project:
> https://bugreports.qt-project.org/browse/QTCRE
> It seems clear to me that you should submit a patch that fixes this to Qt
> Project, and also if possible file the boost unit_test issue with the
> mingw-builds project.
>
> I will try to do so (It is kind of hard for an IDE user to submit IDE
patch :( ). And that is why I asked the (original) q
2013/6/3 Ray Donnelly
> It seems clear to me that you should submit a patch that fixes this to Qt
> Project, and also if possible file the boost unit_test issue with the
> mingw-builds project.
>
>
I took the liberty to submit a bug report to the Qt Project:
https://bugreports.qt-project.org/brow
On Mon, Jun 3, 2013 at 12:26 AM, dw wrote:
> I have found some problems with the InterlockedBitTestAndXXX functions. For
> example:
>
> - Despite sezero's recent update, they still don't all have the "memory"
> clobber.
> - The constraints for the 64bit versions are incorrect (I vs J).
> - There
It seems clear to me that you should submit a patch that fixes this to Qt
Project, and also if possible file the boost unit_test issue with the
mingw-builds project.
On Mon, Jun 3, 2013 at 9:56 AM, Abir Basak wrote:
>
>
>> > I was using build by Ruben for Mingw W64 for long times with Qt Creato
>
> > I was using build by Ruben for Mingw W64 for long times with Qt Creator
> > IDE. However from version 2.7 onward it fails to debug using the gdb
> > shipped by it. The reason is most likely that it fails to parse the gdb
> > version information like GNU gdb (rubenvb-4.7.2-release)
> > 7.5.50.
2013/6/3 Abir Basak
> I was using build by Ruben for Mingw W64 for long times with Qt Creator
> IDE. However from version 2.7 onward it fails to debug using the gdb
> shipped by it. The reason is most likely that it fails to parse the gdb
> version information like GNU gdb (rubenvb-4.7.2-release)
Sorry, gmail fail (Enter Key caused a Send rather than a newline..)
The URL for mingw-builds Qt-builds releases is:
http://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds/
On Mon, Jun 3, 2013 at 8:11 AM, Ray Donnelly wrote:
> Hi Abir,
>
> Qt Project official relea
Hi Abir,
Qt Project official releases are currently using mingw-builds toolchain
releases which includes Python with pretty-printers. Also, mingw-builds
project build their own (comprehensive) Qt releases.
The toolchain that's likely to be used in 5.1.0 is (I think):
http://heanet.dl.sourceforge
27 matches
Mail list logo
