2012/9/11 niXman:
> Please, don't do it =)
Yesterday I built 4.8.0 64bit with SEH.
http://sourceforge.net/projects/mingwbuilds/files/windows-host/4.8.0/snapshot/x86_64-mingw-w64-gcc-4.8.0-snapshot-20120910-rev-191124-c%2Cc%2B%2B%2Cfortran-seh.7z
--
Regards,
niXman
_
2012/9/11 Peter Kümmel:
> Yes, would be some fiddling at the beginning. But in the long run both
> of you would benefit. But it's more a question of motivation/vision
> than a technically one.
I don't mind. It actually would be better. Also there would be no so
much confusion for users in case of
On 11.09.2012 02:07, Ruben Van Boxem wrote:
>>
>> Best would be you merge the two projects into one.
>> (I haven't searched the list if you are arch-enemies)
>>
>
> We're not arch-enemies at all, but we are two completely seperate
> "ventures". I'd think a merge of our efforts would be either a man
2012/9/10 Peter Kümmel
> On 10.09.2012 12:12, Ruben Van Boxem wrote:
> >>
> >> I had a look at Ruben's github code,
> >> and it looks like it is only for personal use only: no readme,
> >> no automatic source download (e.g. were to set LIBICONV_VERSION?),
> >> not usable out of the box.
> >>
> >
On 10.09.2012 12:12, Ruben Van Boxem wrote:
>>
>> I had a look at Ruben's github code,
>> and it looks like it is only for personal use only: no readme,
>> no automatic source download (e.g. were to set LIBICONV_VERSION?),
>> not usable out of the box.
>>
>
> Hi,
>
> I will not deny the points you
2012/9/10 Peter Kümmel
> On 09.09.2012 14:38, niXman wrote:
> > 2012/9/9 Peter Kümmel:
> >
> >> But why do you also point to Ruben's scripts, what's the difference?
> >> Don't your scripts work on Linux?
>
> This was only a question not a critic.
>
> > My scripts were originally created to build
2012/9/10 Peter Kümmel:
> Great, when you push it I'm happy to try it out.
> I've no problem when it is broken a bit, I'm glad to help.
I understand. Thank you for the feedback!
--
Regards,
niXman
___
Dual-target(32 & 64 bit) MinGW compilers for
On 10.09.2012 11:48, niXman wrote:
> 2012/9/10 Peter Kümmel:
>
>> Shouldn't be that hard. The main difference is that the cross-compiler
>> are already installed on the system, for instance on Ubuntu
>> /usr/bin/x86_64-w64-mingw32-gcc, so the compiler name has a prefix and
>> x32/x64 are both in /u
2012/9/10 Peter Kümmel:
> Shouldn't be that hard. The main difference is that the cross-compiler
> are already installed on the system, for instance on Ubuntu
> /usr/bin/x86_64-w64-mingw32-gcc, so the compiler name has a prefix and
> x32/x64 are both in /usr/bin.
> Also it could be assumened that
2012/9/10 Peter Kümmel :
> On 09.09.2012 14:38, niXman wrote:
>> 2012/9/9 Peter Kümmel:
>>
>>> But why do you also point to Ruben's scripts, what's the difference?
>>> Don't your scripts work on Linux?
>
> This was only a question not a critic.
>
>> My scripts were originally created to build MinG
On 09.09.2012 14:38, niXman wrote:
>
> Linux support will be made in the next version of MinGW-builds
> squeaks. About a month.
>
Shouldn't be that hard. The main difference is that the cross-compiler
are already installed on the system, for instance on Ubuntu
/usr/bin/x86_64-w64-mingw32-gcc, so t
On 9/10/2012 16:44, Peter Kümmel wrote:
> - how to disable SLJL(enable SEH) for x64? (--disable-sjlj-exceptions)
Don't specify --disable-sjlj-exceptions or --enable-sjlj-exceptions.
signature.asc
Description: OpenPGP digital signature
--
On 10.09.2012 03:05, Zouzou wrote:
> On 09/09/12 23:16, Peter Kümmel wrote:
Is SEH in 4.7.2 or only in 4.8? How stable is it?
>>>
>>> SEH is enabled in 4.8 series, not sure about 4.7.3 though.
>>
>> Only in 4.8. The patch
>>
>>
>> http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=8ad0b5
On 09.09.2012 14:38, niXman wrote:
> 2012/9/9 Peter Kümmel:
>
>> But why do you also point to Ruben's scripts, what's the difference?
>> Don't your scripts work on Linux?
This was only a question not a critic.
> My scripts were originally created to build MinGW in Windows. I think
> it is not ri
On 09/09/12 23:16, Peter Kümmel wrote:
>>> Is SEH in 4.7.2 or only in 4.8? How stable is it?
>>
>> SEH is enabled in 4.8 series, not sure about 4.7.3 though.
>
> Only in 4.8. The patch
>
>
> http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=8ad0b5306ddfc738d6e450528ee9beb281212ea0
>
> was not
>> Is SEH in 4.7.2 or only in 4.8? How stable is it?
>
> SEH is enabled in 4.8 series, not sure about 4.7.3 though.
Only in 4.8. The patch
http://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=8ad0b5306ddfc738d6e450528ee9beb281212ea0
was not applied to 4.7 branch. I'll try to backport.
Peter
On 9/9/2012 20:37, Peter Kümmel wrote:
>>
>>> Also no 32/dwarf & 64/SEH? Any technical reasons or simply not supported by
>>> GCC?
>>
>> I think it's impossible. But I'll find out.
>
> That would be great!
AFAIK, no technical reason other than the build system getting in your
way. Not using mult
2012/9/9 Peter Kümmel:
> But why do you also point to Ruben's scripts, what's the difference?
> Don't your scripts work on Linux?
My scripts were originally created to build MinGW in Windows. I think
it is not right to force Windows users to use Linux to building MinGW.
In addition, most Windows
On 09.09.2012 12:14, niXman wrote:
> 2012/9/9 Peter Kümmel:
>
>> Ah thanks:
>> http://sourceforge.net/apps/trac/mingw-w64/wiki/Exception%20Handling
>>
>> So until now on 64 bit always SJLJ is used? Or are there alternatives?
>>
>> Is SEH in 4.7.2 or only in 4.8? How stable is it?
>
> As far as I kn
On 09.09.2012 11:46, JonY wrote:
> On 9/9/2012 17:33, Peter Kümmel wrote:
>> On 09.09.2012 11:13, niXman wrote:
>>> 2012/9/9 Peter Kümmel:
>>>
- 32 bit target: dwarf2
>>> Get scripts from Github:
>>> $ git clone g...@github.com:niXman/mingw-builds.git
>>> $ cd mingw-builds
>>> $ ./build gcc-4.
On 09.09.2012 11:13, niXman wrote:
> 2012/9/9 Peter Kümmel:
>
>> - 32 bit target: dwarf2
> Get scripts from Github:
> $ git clone g...@github.com:niXman/mingw-builds.git
> $ cd mingw-builds
> $ ./build gcc-4.7.1 x32 --dwarf --mingw-compress
Yes, this looks great, I will try them.
But why do you a
2012/9/9 Peter Kümmel:
> Ah thanks:
> http://sourceforge.net/apps/trac/mingw-w64/wiki/Exception%20Handling
>
> So until now on 64 bit always SJLJ is used? Or are there alternatives?
>
> Is SEH in 4.7.2 or only in 4.8? How stable is it?
As far as I know - in 4.8.0. About stability I can not say an
On 9/9/2012 17:33, Peter Kümmel wrote:
> On 09.09.2012 11:13, niXman wrote:
>> 2012/9/9 Peter Kümmel:
>>
>>> - 32 bit target: dwarf2
>> Get scripts from Github:
>> $ git clone g...@github.com:niXman/mingw-builds.git
>> $ cd mingw-builds
>> $ ./build gcc-4.7.1 x32 --dwarf --mingw-compress
>>
>>
>>>
On 09.09.2012 11:13, niXman wrote:
> 2012/9/9 Peter Kümmel:
>
>> - 32 bit target: dwarf2
> Get scripts from Github:
> $ git clone g...@github.com:niXman/mingw-builds.git
> $ cd mingw-builds
> $ ./build gcc-4.7.1 x32 --dwarf --mingw-compress
>
>
>> - 64 bit target: dwarf2 < 4.7.1, SEH > 4.7.1
> dwar
2012/9/9 Peter Kümmel:
> - 32 bit target: dwarf2
Get scripts from Github:
$ git clone g...@github.com:niXman/mingw-builds.git
$ cd mingw-builds
$ ./build gcc-4.7.1 x32 --dwarf --mingw-compress
> - 64 bit target: dwarf2 < 4.7.1, SEH > 4.7.1
dwarf is not implemented for 64 bit target.
> - multili
Hello, as you know we are discussing which mingw compiler to use on the Qt
mailing list:
http://lists.qt-project.org/pipermail/development/2012-August/005984.html
http://thread.gmane.org/gmane.comp.lib.qt.devel/6026
and we ended in a mingw-w64 compiler version which is not provided by
26 matches
Mail list logo
