On 4/28/2011 22:56, Jon wrote:
> Is LIBRARY_PATH ignored in my case because i686-w64-mingw32-gcc.exe
> thinks it's cross-compiling between i686-w64-mingw32 and i686-pc-mingw32?
> My understanding is LIBRARY_PATH is ignored when cross-compiling but not
> other cases, and I want t
> >>> Is LIBRARY_PATH ignored in my case because i686-w64-mingw32-gcc.exe
> >>> thinks it's cross-compiling between i686-w64-mingw32 and i686-pc-mingw32?
> >>> My understanding is LIBRARY_PATH is ignored when cross-compiling but not
> >>> other cases, and I want to make sure I get this issue be
On Thu, Apr 28, 2011 at 1:49 PM, Jason wrote:
> On Thursday 28 April 2011 10:57:19 Sisyphus wrote:
>> - Original Message -
>> From: "Sisyphus"
>>
>> > Apart from 'gcc -v' or 'gcc --version' there's apparently nothing - and I
>> > have at least one mingw64 64-bit compiler that doesn't repor
On Thursday 28 April 2011 10:57:19 Sisyphus wrote:
> - Original Message -
> From: "Sisyphus"
>
> > Apart from 'gcc -v' or 'gcc --version' there's apparently nothing - and I
> > have at least one mingw64 64-bit compiler that doesn't report the date
> > even
> > then.
>
> But on the mingw64
- Original Message -
From: "Sisyphus"
> Apart from 'gcc -v' or 'gcc --version' there's apparently nothing - and I
> have at least one mingw64 64-bit compiler that doesn't report the date
> even
> then.
But on the mingw64 mailing list (where I asked about this, in the thread
"Compiler
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 10:20 AM, Sisyphus wrote:
>
> - Original Message -
> From: "Jason"
>
>>> > That's the secret then - just use a compiler later than 20100428. (If
>>> > only I'd waited another fortnight before I downloaded that compiler :-)
>>>
>>
>> Our configure system can reject b
- Original Message -
From: "Jason"
>> > That's the secret then - just use a compiler later than 20100428. (If
>> > only I'd waited another fortnight before I downloaded that compiler :-)
>>
>
> Our configure system can reject bad compilers , but for the test to work
> our
> assembler ya
10 matches
Mail list logo
