On Thu, Apr 28, 2011 at 12:26 PM, Sisyphus wrote:
>
> - Original Message -
> From: "Ruben Van Boxem"
>
>>> Is there a simple way for a program to determine the date that the
>> compiler
>>> was built ?
>>> (A #define that tells us would be ideal, if such exists.)
>>
>> I hope you're not pl
- Original Message -
From: "Ruben Van Boxem"
>> Is there a simple way for a program to determine the date that the
> compiler
>> was built ?
>> (A #define that tells us would be ideal, if such exists.)
>
> I hope you're not planning on using the old compilers with wrong
> underscore
> p
Op 28 apr. 2011 05:39 schreef "Sisyphus" het
volgende:
>
>
> - Original Message -
> From: "Ozkan Sezer"
>
> > Win64-targeting builds from mingw-w64 up to 2010-04-27 didn't
> > follow MSVC x64 convention and did *not* prepend an undersocore
> > to the symbols: this is why you are seeing t
On Thu, Apr 28, 2011 at 6:36 AM, Sisyphus wrote:
>>
>> All win64-targeting toolchains created after 2010-04-28, including
>> the sezero's gcc-4.4-based personal builds follow the MS convention.
>
> Just a quick follow-up question on that.
>
> Is there a simple way for a program to determine the da
- Original Message -
From: "Ozkan Sezer"
> Win64-targeting builds from mingw-w64 up to 2010-04-27 didn't
> follow MSVC x64 convention and did *not* prepend an undersocore
> to the symbols: this is why you are seeing the incompatibilities
> with the newer toolchains.
>
> All win64-targe
On Wed, Apr 27, 2011 at 9:12 AM, Sisyphus wrote:
>
> - Original Message -
> From: "Ozkan Sezer"
>
>> Win64-targeting builds from mingw-w64 up to 2010-04-27 didn't
>> follow MSVC x64 convention and did *not* prepend an undersocore
>> to the symbols: this is why you are seeing the incompat
- Original Message -
From: "Ozkan Sezer"
> Win64-targeting builds from mingw-w64 up to 2010-04-27 didn't
> follow MSVC x64 convention and did *not* prepend an undersocore
> to the symbols: this is why you are seeing the incompatibilities
> with the newer toolchains.
>
> All win64-tar
On Wed, Apr 27, 2011 at 7:01 AM, Sisyphus wrote:
> Hi,
>
> On Windows Vista I have been using the 64-bit 4.6.0 cross-compiler
> (automated build 20100414) for close on 12 months.
>
> I'm now finding that the static and import libraries built using it are
> unusable by any of the recent 64-bit comp
Hi,
On Windows Vista I have been using the 64-bit 4.6.0 cross-compiler
(automated build 20100414) for close on 12 months.
I'm now finding that the static and import libraries built using it are
unusable by any of the recent 64-bit compilers (and vice versa). Looks like
they require different g
