Hi, I agree with the others. Strip your PATH from spaces and until only
one toolset is found at a time .
A good place for this is a batchfile that creates a mingw session if you
need. Never mix-up VS and
mingw paths unless you are aware what they are doing exactly. Sometimes
it is also helpful u
>> configure:1340: checking for gcc
>> configure:1356: found /c/Program Files/OpenAxiom/bin/gcc
You're begging for failures when you install to a PATH with spaces. For example:
C:\Users\Jon\Documents\CDev\sandbox>echo %PATH%
C:\"spacey path\mingw-rvb\bin";...
C:\Users\Jon\Documents\CDev\sandbox>
On Fri, Jun 8, 2012 at 3:52 AM, Jim Michaels wrote:
> it looks to be the fact that *this* gcc expects an argument on -V while the
> one on linux does not (?).
> interesting. there are a LOT of things I would like to compile, but I can't
> because of this bug.
>
> --config.log
>
>
2012/6/8 Tristan Gingold :
>
> On Jun 8, 2012, at 2:12 PM, Kai Tietz wrote:
>
>> Hello Tristan,
>>
>> Thanks for working on this. The patch is ok. As JonY said, unified
>> diffs are more welcome ;)
>>
>>
>> 2012/6/8 Tristan Gingold :
>>> Hi,
>>>
>>> I am currently working on porting our toolset to
On Jun 8, 2012, at 2:12 PM, Kai Tietz wrote:
> Hello Tristan,
>
> Thanks for working on this. The patch is ok. As JonY said, unified
> diffs are more welcome ;)
>
>
> 2012/6/8 Tristan Gingold :
>> Hi,
>>
>> I am currently working on porting our toolset to gcc 4.7 compiled to fully
>> suppor
On Jun 8, 2012, at 1:55 PM, JonY wrote:
> On 6/8/2012 18:27, Tristan Gingold wrote:
>> Hi,
>>
>> I am currently working on porting our toolset to gcc 4.7 compiled to fully
>> support SEH, and I have compiled gdb. This gdb crashes frequently, and I
>> traced that to the use of setjmp/longjmp.
Hello Tristan,
Thanks for working on this. The patch is ok. As JonY said, unified
diffs are more welcome ;)
2012/6/8 Tristan Gingold :
> Hi,
>
> I am currently working on porting our toolset to gcc 4.7 compiled to fully
> support SEH, and I have compiled gdb. This gdb crashes frequently, and
On 6/8/2012 18:27, Tristan Gingold wrote:
> Hi,
>
> I am currently working on porting our toolset to gcc 4.7 compiled to fully
> support SEH, and I have compiled gdb. This gdb crashes frequently, and I
> traced that to the use of setjmp/longjmp.
>
> When compiled with SEH enabled, mingw64 make
Hi, I was using the "former" way and it works, thank you. I've created a cross
qt-makespec that points the compiler, linker, etc. to x86_64-w64-mingw32-g++.
This one then can be used with the -xplatform configure switch.
However, this is quite a qt item, the only caveat is that all the qt-tools
Hi,
I am currently working on porting our toolset to gcc 4.7 compiled to fully
support SEH, and I have compiled gdb. This gdb crashes frequently, and I
traced that to the use of setjmp/longjmp.
When compiled with SEH enabled, mingw64 makes longjmp use RtlUnwinEx, and to
achieve that it calls
On 6/8/2012 16:26, Ruben Van Boxem wrote:
> Op 8 jun. 2012 09:53 schreef "Jim Michaels" het
> volgende:
>>
>> it looks to be the fact that *this* gcc expects an argument on -V while
> the one on linux does not (?).
>> interesting. there are a LOT of things I would like to compile, but I
> can't b
Op 8 jun. 2012 09:53 schreef "Jim Michaels" het
volgende:
>
> it looks to be the fact that *this* gcc expects an argument on -V while
the one on linux does not (?).
> interesting. there are a LOT of things I would like to compile, but I
can't because of this bug.
>
> --config.log
it looks to be the fact that *this* gcc expects an argument on -V while the one
on linux does not (?).
interesting. there are a LOT of things I would like to compile, but I can't
because of this bug.
--config.log
This file contains any messages produced by compilers while
runni
13 matches
Mail list logo
