On 10/26/2012 02:19, Kai Tietz wrote:
> Helle Simson,
>
> this list seems to me more like good content to our FAQ-section in
> Wiki. Some of those points might be defining general goals we wanna
> to define, or decline for mingw-w64 in general.
> Most of those points are looking like something de
Hi,
well this issue is caused by invalid, or better said inadequate
testcase for windows. tzname is a imported variable provided by
msvcr*.dll (C-runtime). So its decoration with the
dllimport-attribute is correct. We could remove from our C-headers
the dllimport-attribute for dll-imported vari
Helle Simson,
this list seems to me more like good content to our FAQ-section in
Wiki. Some of those points might be defining general goals we wanna
to define, or decline for mingw-w64 in general.
Most of those points are looking like something desirable, but on a
technical POV it shows that some
Conftest source is:
/* confdefs.h */
#define _GNU_SOURCE 1
#define _NETBSD_SOURCE 1
#define __BSD_VISIBLE 1
#define _BSD_TYPES 1
#define _DARWIN_C_SOURCE 1
#define _XOPEN_SOURCE 600
#define _XOPEN_SOURCE_EXTENDED 1
#define _POSIX_C_SOURCE 200112L
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#
Hi!
I have error window on crashing conftest during configure program. This
error is only on 64-bit configure when on 32-bit its ok.
I compare config.log's and crash is on:
configure:14317: checking for working tzset()
configure:14393: x86_64-w64-mingw32-gcc -o conftest.exe -O2 -pipe
-fomit-frame-
I've been on this mailing list for some time now and use mingw (both the 32-bit
and 64-bit versions) for several production systems. What I would like to see
is not a commitment to a release schedule but a document that clearly states
the commitment to specific principles. For example:
* Can co
On Thu, Oct 25, 2012 at 8:51 AM, Jacek Caban wrote:
> On 10/24/12 21:19, Kai Tietz wrote:
>> So I would like to get your opinion. You might have complete
>> different opinion about planning mingw-w64's release-cycles, so don't
>> hesitate to tell us what you think about this subject.
>
> I've nev
On 10/24/12 21:19, Kai Tietz wrote:
> So I would like to get your opinion. You might have complete
> different opinion about planning mingw-w64's release-cycles, so don't
> hesitate to tell us what you think about this subject.
Current release-cycles strategy works fine for me, but now that you
m
2012/10/25 Suresh Govindachar
>
> Hello,
>
> The latest mingw-w64 binary for mingw that I have been able to find is
> the following:
>
> mingw-w64-bin_i686-mingw_20111220.zip
>
> Is there a newer build?
>
Not in the autobuilds, but there are numerous "personal builds" available:
rubenvb
> -Original Message-
> From: ext Suresh Govindachar [mailto:sgovindac...@yahoo.com]
> Sent: Thursday, October 25, 2012 2:36 PM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: [Mingw-w64-public] Latest binary mingw build -- from 2011 12 20?
>
>
> Hello,
>
> The latest mingw-w64 b
Hello,
The latest mingw-w64 binary for mingw that I have been able to find is
the following:
mingw-w64-bin_i686-mingw_20111220.zip
Is there a newer build?
Thanks,
--Suresh
--
Everyone hates slow websites. S
On Thu, Oct 25, 2012 at 3:04 AM, Ruben Van Boxem
wrote:
> 2012/10/24 Kai Tietz
>>
>> Hello everybody,
>>
>> I want to raise this discussion on public mailing-list, as mingw-w64's
>> release-cycle might be also of interest to some of our users. Right
>> now we do the major-release by gut feeling
On 10/25/2012 15:04, Ruben Van Boxem wrote:
> 2012/10/24 Kai Tietz
>
>> Hello everybody,
>>
>> I want to raise this discussion on public mailing-list, as mingw-w64's
>> release-cycle might be also of interest to some of our users. Right
>> now we do the major-release by gut feeling with a backgr
2012/10/24 Kai Tietz
> Hello everybody,
>
> I want to raise this discussion on public mailing-list, as mingw-w64's
> release-cycle might be also of interest to some of our users. Right
> now we do the major-release by gut feeling with a background plan
> about features new version shall include.
14 matches
Mail list logo
