Re: [Mingw-w64-public] [Interest] Not getting large file support when configuring Qt 4.8.4 for win32-g++-4.6
Hi Jon! On Sun, Apr 14, 2013 at 6:11 PM, JonY <> wrote: > On 4/15/2013 00:46, K. Frank wrote: >> Hello Lists! >> >> I'm am building Qt 4.8.4 with mingw-w64 4.8.1 on a 64-bit windows 7 machine. >> >> (Specifically, qt-everywhere-opensource-src-4.8.4.zip and >> x86_64-w64-mingw32-gcc-4.8-stdthread-win64_rubenvb.7z, downloaded >> recently.) >> >> When I run configure, specifying "-platform win32-g++-4.6", but not >> specifying >> anything about large file support one way or the other, it seems that large >> file >> support is turned off. The output form configure contains: >> >>Large File support..no >> >> I am under the impression that configure is supposed to turn on large file >> support, based on auto-detected capabilities of the system in question. >> >> One thought that crossed my mind is that maybe 64-bit mingw-w64 no >> longer needs special large file support turned on, in that it always has >> is, but I couldn't find any commentary to this effect. >> >> Maybe I'm wrong about configure auto-detecting large file support, and I >> need to specify it manually. >> >> Or maybe my system is messed up somehow. >> >> Thanks for any advice. > > Is there some sort of log? Hard to tell what configure did to test > without it. First, I don't know whether configure does a test. I saw some online comments that suggest it does, but nothing definitive. Second, I don't see anything that looks like a log of tests run by configure. (But I certainly don't know where to look.) Third, the online qt documentation for configure I found was silent on large file support. Fourth, running "configure --help" reports: -largefile . Enables Qt to access files larger than 4 GB. with the -largefile argument not being flagged with a "*" (default) or a "+" (an "evaluated" default). So taking this at face value, large file support is off by default. Fifth -- and here's where it gets annoying -- I cleaned everything out and re-ran configure with "-largefile" specified. Now configure claimed that large file support was turned on. So far so good. But when I ran the build, I got many copies of the following warning: ..\..\..\include/QtCore/../../src/corelib/global/qconfig.h:41:0: warning: "QT_LARGEFILE_SUPPORT" redefined [enabled by default] #define QT_LARGEFILE_SUPPORT 64 ^ :0:0: note: this is the location of the previous definition And, indeed, the g++ compile command run by the build does contain: -DQT_LARGEFILE_SUPPORT I guess things are running correctly and these are just annoying warnings. But it makes me think that the "correct" thing to have done would have been to run configure without -largefile, hopefully shutting up all the warnings, but having large file support enabled anyway. Do any Qt experts know what is going on here? What's the "right" way to build Qt to get large file support? I'm suspecting that this is a Qt issue, and not specific to mingw-w64. But I'll take the liberty of leaving it cross-posted to the mingw64 list for the time being. Thanks. K. Frank -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] GCC 4.8 and MinGW-w64 release versions
On 4/15/2013 01:16, Ruben Van Boxem wrote: > Hi, > > Is it possible to use mingw-w64 v2.0.8 to build GCC 4.8? V2.0.7 fails in > libstdc++ for sure, I currently used trunk for my arch packages, but a user > says 2.0.8 would work too. Will all functionality be present (e.g. > std::to_string)? > > Please advise, > You need trunk for that. signature.asc Description: OpenPGP digital signature -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Interest] Not getting large file support when configuring Qt 4.8.4 for win32-g++-4.6
On 4/15/2013 00:46, K. Frank wrote: > Hello Lists! > > I'm am building Qt 4.8.4 with mingw-w64 4.8.1 on a 64-bit windows 7 machine. > > (Specifically, qt-everywhere-opensource-src-4.8.4.zip and > x86_64-w64-mingw32-gcc-4.8-stdthread-win64_rubenvb.7z, downloaded > recently.) > > When I run configure, specifying "-platform win32-g++-4.6", but not specifying > anything about large file support one way or the other, it seems that large > file > support is turned off. The output form configure contains: > >Large File support..no > > I am under the impression that configure is supposed to turn on large file > support, based on auto-detected capabilities of the system in question. > > One thought that crossed my mind is that maybe 64-bit mingw-w64 no > longer needs special large file support turned on, in that it always has > is, but I couldn't find any commentary to this effect. > > Maybe I'm wrong about configure auto-detecting large file support, and I > need to specify it manually. > > Or maybe my system is messed up somehow. > > Thanks for any advice. Is there some sort of log? Hard to tell what configure did to test without it. signature.asc Description: OpenPGP digital signature -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] winpthreads testsuite
May be related to openmp hang that I have reported earlier on this list. I can repost the example if needed. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] GCC 4.8 and MinGW-w64 release versions
2013/4/14 Ozkan Sezer > On 4/14/13, Ruben Van Boxem wrote: > > Hi, > > > > Hi Ruben, > > > Is it possible to use mingw-w64 v2.0.8 to build GCC 4.8? V2.0.7 fails > > in libstdc++ for sure, I currently used trunk for my arch packages, > > but a user says 2.0.8 would work too. Will all functionality be > > present (e.g. std::to_string)? > > > > Please advise, > > > > Ruben > > > > Excluding the ChangeLogs and the deleted useless include/directx > stuff, the 2.0.7->2.0.8 diffstat looks like the following: > > mingw-w64-crt/crt/tlssup.c | 11 +-- > mingw-w64-crt/intrincs/bitscanfwd.c |4 - > mingw-w64-crt/intrincs/bitscanfwd64.c |4 - > mingw-w64-crt/intrincs/bitscanrev.c |4 - > mingw-w64-crt/intrincs/bitscanrev64.c |4 - > mingw-w64-crt/intrincs/bittest.c|2 > mingw-w64-crt/intrincs/bittest64.c |2 > mingw-w64-crt/intrincs/bittestc.c |2 > mingw-w64-crt/intrincs/bittestc64.c |2 > mingw-w64-crt/intrincs/bittestci.c |2 > mingw-w64-crt/intrincs/bittestr.c |2 > mingw-w64-crt/intrincs/bittestr64.c |2 > mingw-w64-crt/intrincs/bittestri.c |2 > mingw-w64-crt/intrincs/bittestri64.c|2 > mingw-w64-crt/intrincs/bittests.c |2 > mingw-w64-crt/intrincs/bittests64.c |2 > mingw-w64-crt/intrincs/bittestsi.c |2 > mingw-w64-crt/intrincs/bittestsi64.c|2 > mingw-w64-crt/lib32/iphlpapi.def| 45 ++-- > mingw-w64-crt/lib32/msvcr90d.def|2 > mingw-w64-crt/lib64/iphlpapi.def|5 + > mingw-w64-crt/lib64/msvcr90d.def|2 > mingw-w64-headers/crt/math.h|6 - > mingw-w64-headers/direct-x/include/dinput.h |8 ++ > mingw-w64-headers/include/icmpapi.h |4 - > mingw-w64-headers/include/mstcpip.h | 101 > > mingw-w64-headers/include/winbase.h | 13 ++- > mingw-w64-headers/include/winnls.h |8 -- > mingw-w64-headers/include/winnt.h | 46 +++- > mingw-w64-headers/include/winternl.h| 33 ++--- > 31 files changed, 153 insertions(+), 177 deletions(-) > > Also attached the diff file here for your reference. If 2.0.7 fails > with libstdc+++ in 4.8.0, I can't see how it would succeed with 2.0.8. > indeed, there should at least be some change to some sprintf-kind of thing. Thanks! Ruben > > -- > O.S. > > > -- > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > ___ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > > -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] GCC 4.8 and MinGW-w64 release versions
On 4/14/13, Ruben Van Boxem wrote: > Hi, > Hi Ruben, > Is it possible to use mingw-w64 v2.0.8 to build GCC 4.8? V2.0.7 fails > in libstdc++ for sure, I currently used trunk for my arch packages, > but a user says 2.0.8 would work too. Will all functionality be > present (e.g. std::to_string)? > > Please advise, > > Ruben > Excluding the ChangeLogs and the deleted useless include/directx stuff, the 2.0.7->2.0.8 diffstat looks like the following: mingw-w64-crt/crt/tlssup.c | 11 +-- mingw-w64-crt/intrincs/bitscanfwd.c |4 - mingw-w64-crt/intrincs/bitscanfwd64.c |4 - mingw-w64-crt/intrincs/bitscanrev.c |4 - mingw-w64-crt/intrincs/bitscanrev64.c |4 - mingw-w64-crt/intrincs/bittest.c|2 mingw-w64-crt/intrincs/bittest64.c |2 mingw-w64-crt/intrincs/bittestc.c |2 mingw-w64-crt/intrincs/bittestc64.c |2 mingw-w64-crt/intrincs/bittestci.c |2 mingw-w64-crt/intrincs/bittestr.c |2 mingw-w64-crt/intrincs/bittestr64.c |2 mingw-w64-crt/intrincs/bittestri.c |2 mingw-w64-crt/intrincs/bittestri64.c|2 mingw-w64-crt/intrincs/bittests.c |2 mingw-w64-crt/intrincs/bittests64.c |2 mingw-w64-crt/intrincs/bittestsi.c |2 mingw-w64-crt/intrincs/bittestsi64.c|2 mingw-w64-crt/lib32/iphlpapi.def| 45 ++-- mingw-w64-crt/lib32/msvcr90d.def|2 mingw-w64-crt/lib64/iphlpapi.def|5 + mingw-w64-crt/lib64/msvcr90d.def|2 mingw-w64-headers/crt/math.h|6 - mingw-w64-headers/direct-x/include/dinput.h |8 ++ mingw-w64-headers/include/icmpapi.h |4 - mingw-w64-headers/include/mstcpip.h | 101 mingw-w64-headers/include/winbase.h | 13 ++- mingw-w64-headers/include/winnls.h |8 -- mingw-w64-headers/include/winnt.h | 46 +++- mingw-w64-headers/include/winternl.h| 33 ++--- 31 files changed, 153 insertions(+), 177 deletions(-) Also attached the diff file here for your reference. If 2.0.7 fails with libstdc+++ in 4.8.0, I can't see how it would succeed with 2.0.8. -- O.S. 208.diff.gz Description: GNU Zip compressed data -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] GCC 4.8 and MinGW-w64 release versions
Hi, Is it possible to use mingw-w64 v2.0.8 to build GCC 4.8? V2.0.7 fails in libstdc++ for sure, I currently used trunk for my arch packages, but a user says 2.0.8 would work too. Will all functionality be present (e.g. std::to_string)? Please advise, Ruben -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] winpthreads testsuite
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.04.2013 20:25, K. Frank wrote: > Hi LRN! > > On Sun, Apr 14, 2013 at 10:16 AM, LRN <> wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 14.04.2013 17:55, K. Frank wrote: >>> Hello LRN! >>> >>> On Sun, Apr 14, 2013 at 2:54 AM, LRN <...> wrote: ... This patch should integrate the testsuite imported from pthreads with winpthreads. ... >>> >>> Did you ever learn more about / sort out the create / join >>> race condition you reported earlier? >> No. Ktietz gave me a patch, but it didn't fix the bug. >> >>> (Sorry to semi-hijack the current thread.) >> One of the reasons why i want testsuite is that create2, in >> particular, fails due to the create/join race. So it's not that >> bad :) ... > > How frequently does the race occur? > > The reason I ask is that I've used a couple of mingw-w64 builds > where std::thread is implemented on top of winpthreads. I didn't > try any raw winpthreads create / join tests, but I did do the > equivalent at the std::thread level, namely instantiate / join some > std::threads. When I ran my elementary (and not particularly > high-stress) join tests I didn't see any problems. (This was on a > two-core windows 7 machine.) > > So I'm wondering if the bug you found is relatively rare, or > whether I would need to run a more sophisticated test to catch it. > (Or maybe whether the specific std::thread use case avoids it > somehow.) As i have said, new testsuite triggers that bug for me (create2 test). -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRat32AAoJEOs4Jb6SI2CwDNgIAL5XZGDZbfbCffTRdxIA4LoT St+DavJxeZ6O7kX9MPG8h322q32oGMd73woBLCMpbIDRlGE+h4BkkiqHpjrSr53m +7NOa9NCbrI1LAYL0Frh4i8sa11fMeiVjSOreFclqUn5D82x45kBzdwToQDE5u1o T/P4ctGMA+i+1q9r4U0PhAqzKNkHQK+aw4wKxmeDhqJco3OQmg5nUc1vLEqAtaG3 S3Uee1x3fL51YO05qBnUNWgjDWs0njSVW+zPOTJRJtVufXICdLGAFGBBxaJ54fJs QcIRPSqqA78DIhkPe5FPfP+9fravJ2KR0schFFAKQ7oh5VMawF4AA2dCp4L0R8Q= =+NeW -END PGP SIGNATURE- -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] [Interest] Not getting large file support when configuring Qt 4.8.4 for win32-g++-4.6
Hello Lists! I'm am building Qt 4.8.4 with mingw-w64 4.8.1 on a 64-bit windows 7 machine. (Specifically, qt-everywhere-opensource-src-4.8.4.zip and x86_64-w64-mingw32-gcc-4.8-stdthread-win64_rubenvb.7z, downloaded recently.) When I run configure, specifying "-platform win32-g++-4.6", but not specifying anything about large file support one way or the other, it seems that large file support is turned off. The output form configure contains: Large File support..no I am under the impression that configure is supposed to turn on large file support, based on auto-detected capabilities of the system in question. One thought that crossed my mind is that maybe 64-bit mingw-w64 no longer needs special large file support turned on, in that it always has is, but I couldn't find any commentary to this effect. Maybe I'm wrong about configure auto-detecting large file support, and I need to specify it manually. Or maybe my system is messed up somehow. Thanks for any advice. K. Frank -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] winpthreads testsuite
Hi LRN! On Sun, Apr 14, 2013 at 10:16 AM, LRN <> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 14.04.2013 17:55, K. Frank wrote: >> Hello LRN! >> >> On Sun, Apr 14, 2013 at 2:54 AM, LRN <...> wrote: >>> ... This patch should integrate the testsuite imported from >>> pthreads with winpthreads. ... >> >> Did you ever learn more about / sort out the create / join race >> condition you reported earlier? > No. Ktietz gave me a patch, but it didn't fix the bug. > >> (Sorry to semi-hijack the current thread.) > One of the reasons why i want testsuite is that create2, in > particular, fails due to the create/join race. So it's not that bad :) > ... How frequently does the race occur? The reason I ask is that I've used a couple of mingw-w64 builds where std::thread is implemented on top of winpthreads. I didn't try any raw winpthreads create / join tests, but I did do the equivalent at the std::thread level, namely instantiate / join some std::threads. When I ran my elementary (and not particularly high-stress) join tests I didn't see any problems. (This was on a two-core windows 7 machine.) So I'm wondering if the bug you found is relatively rare, or whether I would need to run a more sophisticated test to catch it. (Or maybe whether the specific std::thread use case avoids it somehow.) Thanks. K. Frank -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] winpthreads testsuite
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14.04.2013 17:55, K. Frank wrote: > Hello LRN! > > On Sun, Apr 14, 2013 at 2:54 AM, LRN <...> wrote: >> ... This patch should integrate the testsuite imported from >> pthreads with winpthreads. ... > > Did you ever learn more about / sort out the create / join race > condition you reported earlier? No. Ktietz gave me a patch, but it didn't fix the bug. > (Sorry to semi-hijack the current thread.) One of the reasons why i want testsuite is that create2, in particular, fails due to the create/join race. So it's not that bad :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRaro5AAoJEOs4Jb6SI2CwxdEIAKcvVcgoV4tuZN8OyNNcaHjz e6t+gPpKM+gXMtmoBAi2b0YrQzaHTmVwqpokDygvs4e4sA7GwG5qQzRqal0LuA3h SAnDeNlMV0QLvnAmb57Hb0jIWS0pVc36JpIB0mSh6Xk8yXyFw8eJEGe+pM7/htBE tNzEwN+7lDn8uibUX88GDoxjyjCZUOdcJ9MrWsAB8/O6GwgrXQcpesl+/WjNQjE/ DBBIy41O7KjZqcsQ+v9rJ3iyBGATrDw9IaiI7SPbR3RrSJr6LNDLH9wWXk57UuQW CdCDswb8fDShU0KQxgueGwZbCGxJNgrGgTUouKOg91UNr+tp2rgl4HYecYFut10= =DJIW -END PGP SIGNATURE- -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] winpthreads testsuite
Hello LRN! On Sun, Apr 14, 2013 at 2:54 AM, LRN <...> wrote: > ... > This patch should integrate the testsuite imported from pthreads with > winpthreads. > ... Did you ever learn more about / sort out the create / join race condition you reported earlier? (Sorry to semi-hijack the current thread.) Thanks. K. Frank -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] winpthreads testsuite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.04.2013 10:54, LRN wrote:
> This patch should integrate the testsuite imported from pthreads
> with winpthreads. (includes re-generated configure and Makefile.in
> - it is very sad that those are tracked in SVN).
>
OK, here is a better patch - split into parts, without generated
files. Say "think you" to git-svn and its wonderful awesomeness!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRaqqYAAoJEOs4Jb6SI2CwVOQH/iQJq/QHNUGJJfjfr6aj2afS
GCskdC8Hr3XvTSSltTx38UfvM8alQaKE2W+T21JakjHk380IYm6paqN/4LpB9lul
iM13Uu2SQiw7iZ6o5YHvuHgahMcCB+JpbtkcF6Ac5Egu/BEodQnp3tD73D19m5xo
jU7eJutnGneBjG1JCwaxTsNrD2IHujvkX1NpQp9P6TAw/Y6wpi7DmQ6gIReQVWgy
i3mpHIdRjlj5qY1R752o+ttKDXdVfkn7X3c96mR9rU6AdHwsaOIap9vwcmQRHRDt
GXV2F/v8NqbISTTZeeSJWcwQYtxDjHyoum+8THpDUj0D2h20oF+Gl5/hGbYcrzo=
=wWKE
-END PGP SIGNATURE-
From b10962796e7dbd89718a964edec9db9b58760c26 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=A0=D1=83=D1=81=D0=BB=D0=B0=D0=BD=20=D0=98=D0=B6=D0=B1?=
=?UTF-8?q?=D1=83=D0=BB=D0=B0=D1=82=D0=BE=D0=B2?=
Date: Sun, 14 Apr 2013 14:21:20 +0400
Subject: [PATCH 1/3] Integrate the testsuite
---
Makefile.am | 2 ++
configure.ac | 11 +-
tests/Makefile.am | 66 +++
3 files changed, 78 insertions(+), 1 deletion(-)
create mode 100644 tests/Makefile.am
diff --git a/Makefile.am b/Makefile.am
index f117785..f57a553 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -33,6 +33,8 @@ libpthread_dll_a_DEPENDENCIES = libwinpthread.la
libpthread_dll_a_SOURCES =
endif
+SUBDIRS = tests
+
# Tell libtool how to use the resource compiler
.rc.lo:
$(LIBTOOL) $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --tag=RC --mode=compile
$(RC) $(RCFLAGS) -i $< -o $@
diff --git a/configure.ac b/configure.ac
index b579286..40c3449 100644
--- a/configure.ac
+++ b/configure.ac
@@ -53,5 +53,14 @@ AC_TYPE_SIZE_T
AC_SUBST([RCFLAGS])
-AC_CONFIG_FILES([Makefile])
+AC_MSG_CHECKING(if benchmarking tests should be run)
+AC_ARG_ENABLE(
+ [benchmarks],
+ [AS_HELP_STRING([--enable-benchmarks], [enable benchmarking tests])],
+ [enable_benchmarks=${enableval}],
+ [enable_benchmarks=no])
+AC_MSG_RESULT($enable_benchmarks)
+AM_CONDITIONAL([ENABLE_BENCHMARKS], [test "x$enable_benchmarks" = "xyes"])
+
+AC_CONFIG_FILES([Makefile tests/Makefile])
AC_OUTPUT
diff --git a/tests/Makefile.am b/tests/Makefile.am
new file mode 100644
index 000..8aed465
--- /dev/null
+++ b/tests/Makefile.am
@@ -0,0 +1,66 @@
+INCLUDES = -I$(top_srcdir)/include
+
+LDADD = $(top_builddir)/libwinpthread.la
+
+noinst_LTLIBRARIES = \
+ libbench.la
+libbench_la_SOURCES = \
+ benchlib.c
+libbench_la_LIBADD = \
+ $(LDADD)
+
+if ENABLE_BENCHMARKS
+ BENCHMARKS = benchtest1 benchtest2 benchtest3 benchtest4 benchtest5
+else
+ BENCHMARKS =
+endif
+
+TESTS = \
+ sizes loadfree \
+ self1 mutex5 \
+ mutex1 mutex1n mutex1e mutex1r \
+ semaphore1 semaphore2 semaphore3 \
+ mutex2 mutex3 \
+ mutex2r mutex2e mutex3r mutex3e \
+ condvar1 condvar1_1 condvar1_2 condvar2 condvar2_1 \
+ exit1 create1 create2 reuse1 reuse2 equal1 \
+ kill1 valid1 valid2 \
+ exit2 exit3 exit4 exit5 \
+ join0 join1 detach1 join2 join3 \
+ mutex4 mutex6 mutex6n mutex6e mutex6r \
+ mutex6s mutex6es mutex6rs \
+ mutex7 mutex7n mutex7e mutex7r \
+ mutex8 mutex8n mutex8e mutex8r \
+ count1 \
+ once1 once2 once3 once4 \
+ self2 \
+ cancel1 cancel2 \
+ semaphore4 semaphore4t semaphore5 \
+ barrier1 barrier2 barrier3 barrier4 barrier5 barrier6 \
+ tsd1 tsd2 delay1 delay2 eyal1 \
+ condvar3 condvar3_1 condvar3_2 condvar3_3 \
+ condvar4 condvar5 condvar6 \
+ condvar7 condvar8 condvar9 \
+ errno1 \
+ rwlock1 rwlock2 rwlock3 rwlock4 \
+ rwlock5 rwlock6 rwlock7 rwlock8 \
+ rwlock2_t rwlock3_t rwlock4_t rwlock5_t rwlock6_t rwlock6_t2 \
+ context1 \
+ cancel3 cancel4 cancel5 cancel6a cancel6d \
+ cancel7 cancel8 \
+ cleanup0 cleanup1 cleanup2 cleanup3 \
+ priority1 priority2 inherit1 \
+ spin1 spin2 spin3 spin4 \
+ exception1 exception2 exception3 \
+ cancel9 create3 stress1 \
+$(BENCHMARKS)
+
+cancel9_LDADD = $(LDADD) -lws2_32
+
+benchtest1_LDADD = $(LDADD) libbench.la
+benchtest2_LDADD = $(LDADD) libbench.la
+benchtest3_LDADD = $(LDADD) libbench.la
+benchtest4_LDADD = $(LDADD) libbench.la
+benchtest5_LDADD = $(LDADD) libbench.la
+
+noinst_PROGRAMS = $(TESTS)
--
1.8.0.3
From 4a2a7122823df8c30179fa5cc6a6f6b118e7788b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=A0=D1=83=D1=81=D0=BB=D0=B0=D0=BD=20=D0=98=D0=B6=D0=B1?=
=?UTF-8?q?=D1=83=D0=BB=D0=B0=D1=82=D0=BE=D0=B2?=
Date: Sun, 14
