Re: [Mingw-w64-public] [Project News|New Builds]

[sisyphus1]

-Original Message- 
From: niXman Sent: Friday, May 25, 2018 2:26 AM To: mingw-w64-public 
Subject: [Mingw-w64-public] [Project News|New Builds]



Hi,


The new builds of MinGW-W64 based on 'GCC-8.1.0' and MinGW-w64 'master' 
branch was uploaded.


Thank you !!
I'll be trying them out soon.

A few days ago I grabbed and installed 
i686-7.3.0-release-posix-dwarf-rt_v5-rev0.7z and 
x86_64-7.3.0-release-posix-seh-rt_v5-rev0.7z.


I discovered that, despite being labelled as "rt_v5", 
__MINGW64_VERSION_MAJOR and __MINGW64_VERSION_MINOR actually report as being 
"6" and "0" respectively.


I mention this only in (the unlikely) case it hasn't already come to your 
attention.


Cheers,
Rob 



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

Carl Kleffner 2018-03-24 12:36:

Hi Nixman,

is mingw-w64 trunk used, or the latest release? It is not clear from
build-info.txt.


v5.x branch:
https://sourceforge.net/p/mingw-w64/mingw-w64/ci/v5.x/tree/


--
Regards, niXman
___
Work for Bitcoins
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Carl Kleffner]

Hi Nixman,

is mingw-w64 trunk used, or the latest release? It is not clear from
build-info.txt.

Carl

2018-03-24 9:05 GMT+01:00 niXman :

> Hi,
>
>
> The new builds of MinGW-W64 based on 'GCC-7.3.0' and 'MinGW-w64 v5.x
> branch' as 'rev0' was uploaded.
>
>
> 32-bit:
> posix-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.3.0/threads-
> posix/sjlj/i686-7.3.0-release-posix-sjlj-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/c1f80f43dd0fb625ee925b4fd
> 01974140871fe09bb771d0684b306ba58ed47f3/detection)
>
> posix-dwarf: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.3.0/threads-
> posix/dwarf/i686-7.3.0-release-posix-dwarf-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/0475b097ad645ae25438ae347
> 0af7e16e218ec1bd617b73e50b6a6c9622589a7/detection)
>
> win32-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.3.0/threads-
> win32/sjlj/i686-7.3.0-release-win32-sjlj-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/f69470f3d4734ff75058f5809
> 247e2f4e1b02072002d33ebc96ee6d27fb21d41/detection)
>
> win32-dwarf: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.3.0/threads-
> win32/dwarf/i686-7.3.0-release-win32-dwarf-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/099257f9861bc38024c09bfd1
> e220fe5c59dd8f60fe129e2333814cf91cc447f/detection)
>
>
> 64-bit:
> posix-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.3.0/threads-
> posix/sjlj/x86_64-7.3.0-release-posix-sjlj-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/3dc29897093ff063ca2ced45e
> adc6f248a97632383cb55fb61daf1a705b6516e/detection)
>
> posix-seh: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.3.0/threads-
> posix/seh/x86_64-7.3.0-release-posix-seh-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/784d25b00e7cf27aa64abe236
> 3b315400c27526bfce672fdee97137f71823d03/detection)
>
> win32-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.3.0/threads-
> win32/sjlj/x86_64-7.3.0-release-win32-sjlj-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/f5d3add9afe6ef0b8ff072500
> 76aa1410f238bcbf15b45c245a06cbf7111e645/detection)
>
> win32-seh: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.3.0/threads-
> win32/seh/x86_64-7.3.0-release-win32-seh-rt_v5-rev0.7z
> (https://www.virustotal.com/#/file/9dc08c9c2bdd5d8173f87791b
> ed644f6e290624f739de474f117b590dfd8a721/detection)
>
>
>
> The online installer is also available:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe
>
>
> --
> Regards, niXman
> ___
> Work for Bitcoins
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> https://sf.net/p/mingw-w64/
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Lajos Foldy]

Any news?

Thanks,
Lajos

On Tue, Aug 22, 2017 at 3:24 PM, niXman  wrote:
> Carl Kleffner 2017-08-22 15:57:
>>
>> Hi niXman,
>>
>> all 32bit builds are blocked by sf:
>>
>> "This file may contain malware and the automatic download has been
>> disabled."
>
>
> Hi,
>
> Hmm... this is very strange...
>
> I think this is a false positives, because the build environment is the same
> as I've been using for more than a year...
>
> All 7.2 builds removed until the cause is clarified.
>
> Thank you for report!
>
>
> --
> Regards, niXman
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> https://sf.net/p/mingw-w64/
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Martin Mitáš]

I recommend uploading those files to virustotal.com. It scans
with plethora of antivirus engines and it can give you quite
good idea whether it is really a false positive or not.

AFAIK there is also good data exchange between virustotal.com
and many AV vendors so this is often an indirect way how to
make the AV vendor notice an issue :-)

Of course, try also talking with people from sf.net what AV they
are using and propagating the files to the AV vendor directly
for further analysis.

Usually AV vendors are quite responsive to such kind of reports.
It is in any AV vendor's interest to fix false positives asap,
especially of such popular SW. Often, the false positives are
caused by too weakly defined pattern sample in their virus database
which then can often be responsible for more false positives.

Martin



Dne 22. 8. 2017 v 15:24 niXman napsal(a):
> Carl Kleffner 2017-08-22 15:57:
>> Hi niXman,
>>
>> all 32bit builds are blocked by sf:
>>
>> "This file may contain malware and the automatic download has been
>> disabled."
> 
> Hi,
> 
> Hmm... this is very strange...
> 
> I think this is a false positives, because the build environment is the same 
> as I've been using for more than a year...
> 
> All 7.2 builds removed until the cause is clarified.
> 
> Thank you for report!
> 
> 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

Carl Kleffner 2017-08-22 15:57:

Hi niXman,

all 32bit builds are blocked by sf:

"This file may contain malware and the automatic download has been
disabled."


Hi,

Hmm... this is very strange...

I think this is a false positives, because the build environment is the 
same as I've been using for more than a year...


All 7.2 builds removed until the cause is clarified.

Thank you for report!


--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Carl Kleffner]

Hi niXman,

all 32bit builds are blocked by sf:

"This file may contain malware and the automatic download has been
disabled."


2017-08-21 21:50 GMT+02:00 niXman :

>
> Hi,
>
> The new builds of MinGW-W64 based on GCC-7.2.0 is uploaded.
> MinGW-w64 master branch is used.
>
>
> 32-bit:
> posix-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.2.0/threads-
> posix/sjlj/i686-7.2.0-release-posix-sjlj-rt_v6-rev0.7z
> posix-dwarf: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.2.0/threads-
> posix/dwarf/i686-7.2.0-release-posix-dwarf-rt_v6-rev0.7z
> win32-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.2.0/threads-
> win32/sjlj/i686-7.2.0-release-win32-sjlj-rt_v6-rev0.7z
> win32-dwarf: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/7.2.0/threads-
> win32/dwarf/i686-7.2.0-release-win32-dwarf-rt_v6-rev0.7z
>
> 64-bit:
> posix-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.2.0/threads-
> posix/sjlj/x86_64-7.2.0-release-posix-sjlj-rt_v6-rev0.7z
> posix-seh: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.2.0/threads-
> posix/seh/x86_64-7.2.0-release-posix-seh-rt_v6-rev0.7z
> win32-sjlj: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.2.0/threads-
> win32/sjlj/x86_64-7.2.0-release-win32-sjlj-rt_v6-rev0.7z
> win32-seh: https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win64/Personal%20Builds/mingw-builds/7.2.0/threads-
> win32/seh/x86_64-7.2.0-release-win32-seh-rt_v6-rev0.7z
>
>
>
> The online installer is also available:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targett
> ing%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe
>
>
>
> --
> Regards, niXman
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> https://sf.net/p/mingw-w64/
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Liu Hao]

On 2017/8/17 23:03, Adrien Nader wrote:

Hi,

On Tue, Aug 15, 2017, niXman wrote:

niXman 2017-08-15 10:23:

Adrien Nader 2017-08-15 10:16:
Have you checked your emails, including the spam folder?

Yes.


ping?


An issue in the host system configuration has been confirmed and
identified. A fix has been devised but not deployed yet.

This should happen soon but in the meantime I have created and
configured an account for you and Liu Hao by hand. I will send the
credentials by mail in a minute.



Gotcha. Thanks for your work! :>

--
Best regards,
LH_Mouse


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Adrien Nader]

Hi,

On Tue, Aug 15, 2017, niXman wrote:
> niXman 2017-08-15 10:23:
> >>Adrien Nader 2017-08-15 10:16:
> >>Have you checked your emails, including the spam folder?
> >Yes.
> 
> ping?

An issue in the host system configuration has been confirmed and
identified. A fix has been devised but not deployed yet.

This should happen soon but in the meantime I have created and
configured an account for you and Liu Hao by hand. I will send the
credentials by mail in a minute.

-- 
Adrien

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

niXman 2017-08-15 10:23:

Adrien Nader 2017-08-15 10:16:
Have you checked your emails, including the spam folder?

Yes.


ping?


--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

Adrien Nader 2017-08-15 10:16:


Have you checked your emails, including the spam folder?


Yes.


--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Liu Hao]

On 2017/8/15 15:16, Adrien Nader wrote:

On Tue, Aug 15, 2017, niXman wrote:

Liu Hao 2017-08-15 05:59:


When I click the Register button the page reloads and nothing happens
thereafter.


+1


Have you checked your emails, including the spam folder?



Yes. There are no such mails.


--
Best regards,
LH_Mouse


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Adrien Nader]

On Tue, Aug 15, 2017, niXman wrote:
> Liu Hao 2017-08-15 05:59:
> 
> >When I click the Register button the page reloads and nothing happens
> >thereafter.
> 
> +1

Have you checked your emails, including the spam folder?

-- 
Adrien

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

Liu Hao 2017-08-15 05:59:


When I click the Register button the page reloads and nothing happens
thereafter.


+1


--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Liu Hao]

On 2017/8/15 3:22, Adrien Nader wrote:

On Mon, Aug 14, 2017, niXman wrote:

Norbert Pfeiler 2017-08-14 18:19:

What do you want the contents to be? (regarding it currently shows 2
versions)
I usually update Msys2 and Arch where only 1 version applies.


will be better if you explain how I can update this myself.


Scroll to the bottom, click login/register, fill in and validate the
form, check your emails. 


When I click the Register button the page reloads and nothing happens 
thereafter.



Edits on some pages require me to add editors
to a specific group, this is the case for the download pages so you have
to tell me or Jonathan about your username.
After login you will get edit buttons on the right of the content (both
a button for the whole page and one per content section).



I would like such an account but I am still struggling with creating one...

--
Best regards,
LH_Mouse


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Adrien Nader]

On Mon, Aug 14, 2017, niXman wrote:
> Norbert Pfeiler 2017-08-14 18:19:
> >What do you want the contents to be? (regarding it currently shows 2
> >versions)
> >I usually update Msys2 and Arch where only 1 version applies.
> 
> will be better if you explain how I can update this myself.

Scroll to the bottom, click login/register, fill in and validate the
form, check your emails. Edits on some pages require me to add editors
to a specific group, this is the case for the download pages so you have
to tell me or Jonathan about your username.
After login you will get edit buttons on the right of the content (both
a button for the whole page and one per content section).

As an additional note (this does not apply for your case), for
maintainability reasons some of the download infos have been moved to
separate pages that are "included" in the main one. This is not visible
to visitors, only to editors. This is easily spotted because the
textblock contains '{{section>download/...' and the corresponding page
('download/...') should be edited instead.

-- 
Adrien Nader

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

Norbert Pfeiler 2017-08-14 18:19:

What do you want the contents to be? (regarding it currently shows 2
versions)
I usually update Msys2 and Arch where only 1 version applies.


will be better if you explain how I can update this myself.


--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Norbert Pfeiler]

What do you want the contents to be? (regarding it currently shows 2
versions)
I usually update Msys2 and Arch where only 1 version applies.

On Mon, Aug 14, 2017 at 4:47 PM niXman  wrote:

> JonY via Mingw-w64-public 2017-08-14 17:18:
> > On 08/14/2017 12:28 PM, niXman wrote:
>
> > Would you please update mingw-builds on this page?
> > http://mingw-w64.org/doku.php/download
>
> I do not know how.
>
>
> --
> Regards, niXman
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> https://sf.net/p/mingw-w64/
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

JonY via Mingw-w64-public 2017-08-14 17:18:

On 08/14/2017 12:28 PM, niXman wrote:



Would you please update mingw-builds on this page?
http://mingw-w64.org/doku.php/download


I do not know how.


--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[JonY via Mingw-w64-public]

On 08/14/2017 12:28 PM, niXman wrote:
> Hi,
> 
> The new builds of MinGW-W64 based on GCC-7.1.0 with bugfix
> 647(https://sourceforge.net/p/mingw-w64/bugs/647/) is uploaded.
> MinGW-w64 v5.x is used.
> 
> 

Would you please update mingw-builds on this page?
http://mingw-w64.org/doku.php/download

Thanks.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

Gisle Vanem 2017-07-24 19:35:


Do any of these support '-m32' *and* '-m64'?


sjlj builds supports '-m32' and '-m64'.



--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
https://sf.net/p/mingw-w64/

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Gisle Vanem]

niXman wrote:


The new builds of MinGW-W64 based on GCC-7.1.0 is uploaded.
MinGW-w64 v5.x is used.


Do any of these support '-m32' *and* '-m64'?

I guess not, since on SF I see a directory-branch named
"Multilib Toolchains(Targetting Win32 and Win64)"
which is a bit old.

--
--gv

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Stephen Kitt]

Hi niXman,

On Tue, 20 Sep 2016 21:32:02 +0300, niXman  wrote:
> Zouzou 2016-09-18 17:28:
> > One note: The source is missing from
> > .
> 
> The uploading of the builds and sources is performed by scripts. It 
> looks like something went wrong with the scripts... I'll check...

I tried to find the source but failed; any news on the scripts? I'm curious
to see how you enabled filesystem TS support (I'm getting build failures
because dir.cc expects DIR* but MinGW-w64 _wopendir returns WDIR*).

Regards,

Stephen

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[niXman]

Zouzou 2016-09-18 17:28:
> Hey,
> 
> As always, thanks for these builds!
> 
> One note: The source is missing from
> .
> 
> Zouzou

Hi,

The uploading of the builds and sources is performed by scripts. It 
looks like something went wrong with the scripts... I'll check...



-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News|New Builds]

[Zouzou]

On 09/09/2016 12:22, niXman wrote:
> Hi,
>
> The new builds of MinGW-W64 based on GCC-6.2.0 as revision 1 is
> uploaded.
> Bug 506(sf.net/p/mingw-w64/bugs/506/) was fixed. Many thanks to
> DarkUranium ;)
> MinGW-w64 v5 is used.
>
> As earlier, you can try to use the new
> 'std::experimental::filesystem'(http://en.cppreference.com/w/cpp/experimental/fs)
> module. For this, add the '-lstdc++fs' options to the linker command
> line.
>
>
> 32-bit:
> posix-sjlj:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/6.2.0/threads-posix/sjlj/i686-6.2.0-release-posix-sjlj-rt_v5-rev1.7z
> posix-dwarf:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/6.2.0/threads-posix/dwarf/i686-6.2.0-release-posix-dwarf-rt_v5-rev1.7z
> win32-sjlj:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/6.2.0/threads-win32/sjlj/i686-6.2.0-release-win32-sjlj-rt_v5-rev1.7z
> win32-dwarf:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/6.2.0/threads-win32/dwarf/i686-6.2.0-release-win32-dwarf-rt_v5-rev1.7z
>
> 64-bit:
> posix-sjlj:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/6.2.0/threads-posix/sjlj/x86_64-6.2.0-release-posix-sjlj-rt_v5-rev1.7z
> posix-seh:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/6.2.0/threads-posix/seh/x86_64-6.2.0-release-posix-seh-rt_v5-rev1.7z
> win32-sjlj:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/6.2.0/threads-win32/sjlj/x86_64-6.2.0-release-win32-sjlj-rt_v5-rev1.7z
> win32-seh:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/6.2.0/threads-win32/seh/x86_64-6.2.0-release-win32-seh-rt_v5-rev1.7z
>
>
>
> The online installer is also available at:
> https://sf.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe
>
>

Hey,

As always, thanks for these builds!

One note: The source is missing from 
.

Zouzou

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Ray Donnelly]

On Mon, Nov 3, 2014 at 3:45 PM, Baruch Burstein  wrote:
> On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem 
> wrote:
>>
>> 2014-11-03 10:30 GMT+01:00 Baruch Burstein :
>>>
>>> I am curious why only a few of the executables get prefixed versions? I
>>> just tried running a certain makefile with prefixed versions of the
>>> toolchain, and it failed looking for the prefixed versions of 'ar' and
>>> 'windres'. Easily solvable (make a copy and prefix it), but I am still
>>> curious why some get it by default while others don't?
>>
>>
>> Because this is a native toolchain. Native toolchains don't have
>> everything prefixed. Your makefile shouldn't be using any prefixes, and just
>> call the bare "gcc" etc. instead.
>
>
> a. Then why are some prefixed?
> b. Is there another way to determine in the makefile if compiling for x64 or
> x32 without using the compiler executable name?
>

To be pedantic, you'll never be running x32 on Windows:
http://en.wikipedia.org/wiki/X32_ABI

>
> --
> ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
>
> --
>
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[NAKAI Yuta]

> From: bmburst...@gmail.com
> Date: Mon, 3 Nov 2014 17:45:59 +0200
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] [Project News | New Builds]
>
> On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem
> mailto:vanboxem.ru...@gmail.com>> wrote:
> 2014-11-03 10:30 GMT+01:00 Baruch Burstein
> mailto:bmburst...@gmail.com>>:
> I am curious why only a few of the executables get prefixed versions? I
> just tried running a certain makefile with prefixed versions of the
> toolchain, and it failed looking for the prefixed versions of 'ar' and
> 'windres'. Easily solvable (make a copy and prefix it), but I am still
> curious why some get it by default while others don't?
>
> Because this is a native toolchain. Native toolchains don't have
> everything prefixed. Your makefile shouldn't be using any prefixes, and
> just call the bare "gcc" etc. instead.
>
> a. Then why are some prefixed?
It's the specification of gcc.

> b. Is there another way to determine in the makefile if compiling for
> x64 or x32 without using the compiler executable name?
Determine by checking size of void* in configure.
If you don't want to use configure, just add shell variables setting in your 
Makefile (for example, ARCH=x86_64 make ...)

>
>
> --
> ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
>
> --
> ___ Mingw-w64-public
> mailing list Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
  
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Ruben Van Boxem]

2014-11-03 16:45 GMT+01:00 Baruch Burstein :

> On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem 
> wrote:
>
>> 2014-11-03 10:30 GMT+01:00 Baruch Burstein :
>>
>>> I am curious why only a few of the executables get prefixed versions? I
>>> just tried running a certain makefile with prefixed versions of the
>>> toolchain, and it failed looking for the prefixed versions of 'ar' and
>>> 'windres'. Easily solvable (make a copy and prefix it), but I am still
>>> curious why some get it by default while others don't?
>>>
>>
>> Because this is a native toolchain. Native toolchains don't have
>> everything prefixed. Your makefile shouldn't be using any prefixes, and
>> just call the bare "gcc" etc. instead.
>>
>
> a. Then why are some prefixed?
>

That's the whole GCC/binutils/autotools ecosystem that does that and uses
that. Don't ask me for the reasons, I did not write the tools way back when.



> b. Is there another way to determine in the makefile if compiling for x64
> or x32 without using the compiler executable name?
>

First, a makefile shouldn't care if it's building for 32 or 64-bit. That is
a distinction you'd want to make at the code-level, if you need to make it
at all.
If you want to be able to cross-compile, a good way is to have the makefile
"accept an option" like CROSS_PREFIX, which could be "i686-w64-mingw32-",
and passed in like:
make CROSS_PREFIX=i686-w64-mingw32-

And prefixing all calls to the tools with this prefix. For native
toolchains, just "make" with an empty CROSS_PREFIX would work.


Cheers,

Ruben
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Baruch Burstein]

On Mon, Nov 3, 2014 at 2:37 PM, Ruben Van Boxem 
wrote:

> 2014-11-03 10:30 GMT+01:00 Baruch Burstein :
>
>> I am curious why only a few of the executables get prefixed versions? I
>> just tried running a certain makefile with prefixed versions of the
>> toolchain, and it failed looking for the prefixed versions of 'ar' and
>> 'windres'. Easily solvable (make a copy and prefix it), but I am still
>> curious why some get it by default while others don't?
>>
>
> Because this is a native toolchain. Native toolchains don't have
> everything prefixed. Your makefile shouldn't be using any prefixes, and
> just call the bare "gcc" etc. instead.
>

a. Then why are some prefixed?
b. Is there another way to determine in the makefile if compiling for x64
or x32 without using the compiler executable name?


-- 
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Ruben Van Boxem]

2014-11-03 10:30 GMT+01:00 Baruch Burstein :

> I am curious why only a few of the executables get prefixed versions? I
> just tried running a certain makefile with prefixed versions of the
> toolchain, and it failed looking for the prefixed versions of 'ar' and
> 'windres'. Easily solvable (make a copy and prefix it), but I am still
> curious why some get it by default while others don't?
>

Because this is a native toolchain. Native toolchains don't have everything
prefixed. Your makefile shouldn't be using any prefixes, and just call the
bare "gcc" etc. instead.

Cheers,

Ruben
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Baruch Burstein]

I am curious why only a few of the executables get prefixed versions? I
just tried running a certain makefile with prefixed versions of the
toolchain, and it failed looking for the prefixed versions of 'ar' and
'windres'. Easily solvable (make a copy and prefix it), but I am still
curious why some get it by default while others don't?

On Sun, Nov 2, 2014 at 10:42 AM, niXman  wrote:

>
> *ANNOUNCING* GCC-4.9.2 builds are released.
>
> Program *versions* in builds:
>
> 1. *GCC-4.9.2*
> 2. *binutils-2.24*
> 3. *mingw-w64 v3 git c6f0d3d981c70ad31bb1c2bfc2850b827281e189*
> 4. *gdb-7.8.1*
> 5. *python-2.7.8(with dev-files)*
> 6. *make-4.1*
>
>
> Links:
> 32-bit:
>posix-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-posix/sjlj/i686-4.9.2-release-posix-sjlj-rt_v3-rev0.7z
>posix-dwarf:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-posix/dwarf/i686-4.9.2-release-posix-dwarf-rt_v3-rev0.7z
>win32-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-win32/sjlj/i686-4.9.2-release-win32-sjlj-rt_v3-rev0.7z
>win32-dwarf:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.2/threads-win32/dwarf/i686-4.9.2-release-win32-dwarf-rt_v3-rev0.7z
>
> 64-bit:
>posix-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-posix/sjlj/x86_64-4.9.2-release-posix-sjlj-rt_v3-rev0.7z
>posix-seh:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-posix/seh/x86_64-4.9.2-release-posix-seh-rt_v3-rev0.7z
>win32-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-win32/sjlj/x86_64-4.9.2-release-win32-sjlj-rt_v3-rev0.7z
>win32-seh:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.2/threads-win32/seh/x86_64-4.9.2-release-win32-seh-rt_v3-rev0.7z
>
>
> The online installer is also available:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe
>
>
> --
> Regards, niXman
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> http://sourceforge.net/projects/mingw-w64/
> ___
> Another online IDE: http://liveworkspace.org/
>
>
> --
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>



-- 
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Martin Mitáš]

I know this is feature in at least one quite wide-spread antivirus. 

It implements something called "file reputation service" (in a cloud) and 
it simply sees any (executable) file which it does not know as potentially 
dangerous.

The logic is that if it sees the file more often and for some time (and it 
still has not find a path to a virus database), it is likely safe and legitmate 
file.  

Some shields (e.g. web shield) may ask the cloud about the file reputation when
you download it and it then may present the warning in the browser via browser 
extension.

So as soon as it will see the file more often (and assuming there is no 
malware),
the warning shall cease to appear.

If you are using this particular antivirus, then mingw-w64 team cannot do 
anything with that: Any newly built executable file with unique hash shall 
trigger the same warning until it becomes more wide-spread.

Other AV vendors may implement something similar too.


Martin




Dne 1. 11. 2014 v 8:12 Rashad M napsal(a):
> Hi ,
> 
> Download installer on chrome (Windows 7 32bit) gives weird warning. 
> Screenshot attached. I understand this is not a issue as I am sure the 
> installer is "not dangerous". But this may scare people who are using an 
> antivirus as that will report it dangerous or maybe delete the file!
> 
> 
> 
> On Sat, Nov 1, 2014 at 12:01 PM, niXman  > wrote:
> 
> 
> Hi,
> 
> Builds of MinGW-W64 based on GCC-4.9.1 is updated.
> MinGW-w64 is updated to c6f0d3d981c70ad31bb1c2bfc2850b827281e189
> GDB is updated to 7.8.1
> 
> Links:
> 32-bit:
>  posix-sjlj:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-posix/sjlj/i686-4.9.1-release-posix-sjlj-rt_v3-rev3.7z
>  posix-dwarf:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev3.7z
>  win32-sjlj:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-win32/sjlj/i686-4.9.1-release-win32-sjlj-rt_v3-rev3.7z
>  win32-dwarf:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-win32/dwarf/i686-4.9.1-release-win32-dwarf-rt_v3-rev3.7z
> 
> 64-bit:
>  posix-sjlj:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-posix/sjlj/x86_64-4.9.1-release-posix-sjlj-rt_v3-rev3.7z
>  posix-seh:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-posix/seh/x86_64-4.9.1-release-posix-seh-rt_v3-rev3.7z
>  win32-sjlj:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-win32/sjlj/x86_64-4.9.1-release-win32-sjlj-rt_v3-rev3.7z
>  win32-seh:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-win32/seh/x86_64-4.9.1-release-win32-seh-rt_v3-rev3.7z
> 
> 
> The online installer is also available:
> 
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe
> 
> 
> Builds based on GCC-4.9.2 will be uploaded soon.
> 
> 
> --
> Regards, niXman
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> http://sourceforge.net/projects/mingw-w64/
> ___
> Another online IDE: http://liveworkspace.org/
> 
> 
> --
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net 
> 
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> 
> 
> 
> 
> -- 
> Regards,
>Rashad
> 
> 
> --
> 
> 
> 
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> 

--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Rashad M]

Hi ,

Download installer on chrome (Windows 7 32bit) gives weird warning.
Screenshot attached. I understand this is not a issue as I am sure the
installer is "not dangerous". But this may scare people who are using an
antivirus as that will report it dangerous or maybe delete the file!



On Sat, Nov 1, 2014 at 12:01 PM, niXman  wrote:

>
> Hi,
>
> Builds of MinGW-W64 based on GCC-4.9.1 is updated.
> MinGW-w64 is updated to c6f0d3d981c70ad31bb1c2bfc2850b827281e189
> GDB is updated to 7.8.1
>
> Links:
> 32-bit:
>  posix-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-posix/sjlj/i686-4.9.1-release-posix-sjlj-rt_v3-rev3.7z
>  posix-dwarf:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev3.7z
>  win32-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-win32/sjlj/i686-4.9.1-release-win32-sjlj-rt_v3-rev3.7z
>  win32-dwarf:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/threads-win32/dwarf/i686-4.9.1-release-win32-dwarf-rt_v3-rev3.7z
>
> 64-bit:
>  posix-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-posix/sjlj/x86_64-4.9.1-release-posix-sjlj-rt_v3-rev3.7z
>  posix-seh:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-posix/seh/x86_64-4.9.1-release-posix-seh-rt_v3-rev3.7z
>  win32-sjlj:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-win32/sjlj/x86_64-4.9.1-release-win32-sjlj-rt_v3-rev3.7z
>  win32-seh:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-win32/seh/x86_64-4.9.1-release-win32-seh-rt_v3-rev3.7z
>
>
> The online installer is also available:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe
>
>
> Builds based on GCC-4.9.2 will be uploaded soon.
>
>
> --
> Regards, niXman
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> http://sourceforge.net/projects/mingw-w64/
> ___
> Another online IDE: http://liveworkspace.org/
>
>
> --
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>



-- 
Regards,
   Rashad
--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

Also, the sources of the mingw-w64-installer is now published as part of 
the mingw-builds scripts project.

https://github.com/niXman/mingw-builds/tree/develop/mingw-builds-install


--
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Adrien Nader]

On Tue, May 06, 2014, niXman wrote:
> niXman 2014-05-06 19:18:
> > I hope that someone from the project administrators, will place the 
> > link
> > to installer on the green button on the main page of the project.
> 
> ping?

I've updated the link on the website download page and someone (I don't
know who) changed the "featured download" link on sourceforge's file
release system to point to it (it was pointing to the sources before).

-- 
Adrien Nader

--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

niXman 2014-05-06 19:18:
> I hope that someone from the project administrators, will place the 
> link
> to installer on the green button on the main page of the project.

ping?

-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Adrien Nader]

On Sun, Apr 27, 2014, Dongsheng Song wrote:
> On Sat, Apr 26, 2014 at 11:49 PM, Dongsheng Song
>  wrote:
> > On Sat, Apr 26, 2014 at 10:25 PM, Adrien Nader  wrote:
> >> On Sat, Apr 26, 2014, Dongsheng Song wrote:
> >>> On Sat, Apr 26, 2014 at 3:22 PM, Adrien Nader  wrote:
> >>> > On Sat, Apr 26, 2014, Dongsheng Song wrote:
> >>> >> On Sat, Apr 26, 2014 at 12:31 AM, Adrien Nader  wrote:
> >>> >> > I believe --with-arch=core2 is a big issue for generic toolchains. It
> >>> >> > will create troubles which will be very annoying to pinpoint.
> >>> >> >
> >>> >> > Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
> >>> >> > already has SSE2 and there is little value in restricting this 
> >>> >> > except in
> >>> >> > very specific situation which are better dealt on a case-by-case 
> >>> >> > basis.
> >>> >> >
> >>> >> > Regards,
> >>> >> > Adrien Nader
> >>> >> >
> >>> >>
> >>> >> Do you really meet this issue ? I can not image someone still running
> >>> >> 64 bit Windows on such old CPU.
> >>> >>
> >>> >> Intel core2 release in July 2006, shutdown in January 2010.
> >>> >> http://en.wikipedia.org/wiki/Intel_Core_2
> >>> >
> >>> > I have troubles believing people still run XP but many do. :P
> >>> >
> >>> > The issue is rather when you look at the AMD CPUs.
> >>> > First models with SSE3 are from the end of 2007 (meaning you would still
> >>> > easily see machines with them at the end of 2008, even beginning of
> >>> > 2009).
> >>> > The real issue is with SSSE3 (one more 'S') since the first mobile CPUs
> >>> > with it have been released beginning of 2011 and the first desktop CPUs
> >>> > with it have been released end of 2011 are are still easily found.
> >>> >
> >>> > I have a machine without SSE3 in my living room (albeit it needs a new
> >>> > PSU), along with a machine without SSSE3 which is definitely running
> >>> > strong (in particular since the rate of CPU speed improvement has
> >>> > dramatically slowed down in the last few years).
> >>> >
> >>> > I don't think there is a point in making core2 the default; I don't
> >>> > think it will bring any improvements except when building multimedia
> >>> > stuff and even then it's not unlikely they don't provide hand-tuned
> >>> > assembly but even then, -mtune should do be able to bring the
> >>> > performance benefits on the newer CPUs while still running on the older
> >>> > ones.
> >>> >
> >>>
> >>> I agree with you the performance view.
> >>>
> >>> But from gcc view, Intel 64 cpu is: nocona, core2 or later. In my
> >>> memory, I never hear someone can run 64 bit windows on nocona without
> >>> problem. I know it's unfair for AMD CPUs, but both without -march and
> >>> with -march= give 3DNow defined, it's not acceptable for
> >>> Intel CPUs.
> >>
> >> "Intel 64" is a name that doesn't exist. It's either AMD64 (AMD
> >> parlance), EM64T (Intel parlance), x64 (Microsoft parlance) or x86_64
> >> (parlance of anyone not interested in marketing and propaganda). The
> >> first CPUs handling x86_64 date from 2003 and were server-class CPUs.
> >>
> >> Using "--with-arch=core2" means that there many CPUs sold during pretty
> >> much *10* years will not be able to run the programs compiled with these
> >> toolchains and will crash at surprising times in surprising ways.
> >>
> >> Right now I have a Windows 8 x86_64 VM running on a CPU from 2009 or
> >> 2010 without SSSE3. Actually it maybe doesn't have SSE3 either. I've
> >> never had issues with x86_64 stuff on it.
> >> I've also grabbed my XP 64 box and there's a cute logo of a Pentium 4.
> >> While everyone will agree XP 64 was far from perfect, I think it's a
> >> good indication that it worked at least for some people.
> >>
> >>
> >> As for not specifying any arch, I wasn't able to quickly find a
> >> reference or documentation on the matter. However, Linux distributions
> >> are a good example however: they run on all x86_64 CPUs and don't set
> >> anything specific and that's what a generic toolchain should do too.
> >>
> >> In any case, if not setting --with-arch makes code that cannot run on
> >> the triplet specified during the build of GCC (which I do not believe)
> >> then this is an issue in GCC and should be dealt in GCC and not
> >> worked-around (but again, I believe it is not the case).
> >>
> >> --
> >> Adrien Nader
> >>
> >
> > Just pick Linux 64 bit gcc:
> >
> > gcc -dM -E - < /dev/null | grep -i k8
> > #define __k8 1
> > #define __k8__ 1
> >
> > From http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86-64-Options.html , k8 is:
> >
> > Processors based on the AMD K8 core with x86-64 instruction set
> > support, including the AMD Opteron, Athlon 64, and Athlon 64 FX
> > processors. (This supersets MMX, SSE, SSE2, 3DNow!, enhanced 3DNow!
> > and 64-bit instruction set extensions.)
> 
> By the way, You can use your prefer -march when compile programs. It's
> best practices, many people use -march to support newer or older CPUs,
> no one default setting suits us all.

Indeed, it 

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 11:49 PM, Dongsheng Song
 wrote:
> On Sat, Apr 26, 2014 at 10:25 PM, Adrien Nader  wrote:
>> On Sat, Apr 26, 2014, Dongsheng Song wrote:
>>> On Sat, Apr 26, 2014 at 3:22 PM, Adrien Nader  wrote:
>>> > On Sat, Apr 26, 2014, Dongsheng Song wrote:
>>> >> On Sat, Apr 26, 2014 at 12:31 AM, Adrien Nader  wrote:
>>> >> > I believe --with-arch=core2 is a big issue for generic toolchains. It
>>> >> > will create troubles which will be very annoying to pinpoint.
>>> >> >
>>> >> > Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
>>> >> > already has SSE2 and there is little value in restricting this except 
>>> >> > in
>>> >> > very specific situation which are better dealt on a case-by-case basis.
>>> >> >
>>> >> > Regards,
>>> >> > Adrien Nader
>>> >> >
>>> >>
>>> >> Do you really meet this issue ? I can not image someone still running
>>> >> 64 bit Windows on such old CPU.
>>> >>
>>> >> Intel core2 release in July 2006, shutdown in January 2010.
>>> >> http://en.wikipedia.org/wiki/Intel_Core_2
>>> >
>>> > I have troubles believing people still run XP but many do. :P
>>> >
>>> > The issue is rather when you look at the AMD CPUs.
>>> > First models with SSE3 are from the end of 2007 (meaning you would still
>>> > easily see machines with them at the end of 2008, even beginning of
>>> > 2009).
>>> > The real issue is with SSSE3 (one more 'S') since the first mobile CPUs
>>> > with it have been released beginning of 2011 and the first desktop CPUs
>>> > with it have been released end of 2011 are are still easily found.
>>> >
>>> > I have a machine without SSE3 in my living room (albeit it needs a new
>>> > PSU), along with a machine without SSSE3 which is definitely running
>>> > strong (in particular since the rate of CPU speed improvement has
>>> > dramatically slowed down in the last few years).
>>> >
>>> > I don't think there is a point in making core2 the default; I don't
>>> > think it will bring any improvements except when building multimedia
>>> > stuff and even then it's not unlikely they don't provide hand-tuned
>>> > assembly but even then, -mtune should do be able to bring the
>>> > performance benefits on the newer CPUs while still running on the older
>>> > ones.
>>> >
>>>
>>> I agree with you the performance view.
>>>
>>> But from gcc view, Intel 64 cpu is: nocona, core2 or later. In my
>>> memory, I never hear someone can run 64 bit windows on nocona without
>>> problem. I know it's unfair for AMD CPUs, but both without -march and
>>> with -march= give 3DNow defined, it's not acceptable for
>>> Intel CPUs.
>>
>> "Intel 64" is a name that doesn't exist. It's either AMD64 (AMD
>> parlance), EM64T (Intel parlance), x64 (Microsoft parlance) or x86_64
>> (parlance of anyone not interested in marketing and propaganda). The
>> first CPUs handling x86_64 date from 2003 and were server-class CPUs.
>>
>> Using "--with-arch=core2" means that there many CPUs sold during pretty
>> much *10* years will not be able to run the programs compiled with these
>> toolchains and will crash at surprising times in surprising ways.
>>
>> Right now I have a Windows 8 x86_64 VM running on a CPU from 2009 or
>> 2010 without SSSE3. Actually it maybe doesn't have SSE3 either. I've
>> never had issues with x86_64 stuff on it.
>> I've also grabbed my XP 64 box and there's a cute logo of a Pentium 4.
>> While everyone will agree XP 64 was far from perfect, I think it's a
>> good indication that it worked at least for some people.
>>
>>
>> As for not specifying any arch, I wasn't able to quickly find a
>> reference or documentation on the matter. However, Linux distributions
>> are a good example however: they run on all x86_64 CPUs and don't set
>> anything specific and that's what a generic toolchain should do too.
>>
>> In any case, if not setting --with-arch makes code that cannot run on
>> the triplet specified during the build of GCC (which I do not believe)
>> then this is an issue in GCC and should be dealt in GCC and not
>> worked-around (but again, I believe it is not the case).
>>
>> --
>> Adrien Nader
>>
>
> Just pick Linux 64 bit gcc:
>
> gcc -dM -E - < /dev/null | grep -i k8
> #define __k8 1
> #define __k8__ 1
>
> From http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86-64-Options.html , k8 is:
>
> Processors based on the AMD K8 core with x86-64 instruction set
> support, including the AMD Opteron, Athlon 64, and Athlon 64 FX
> processors. (This supersets MMX, SSE, SSE2, 3DNow!, enhanced 3DNow!
> and 64-bit instruction set extensions.)

By the way, You can use your prefer -march when compile programs. It's
best practices, many people use -march to support newer or older CPUs,
no one default setting suits us all.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started No

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 10:25 PM, Adrien Nader  wrote:
> On Sat, Apr 26, 2014, Dongsheng Song wrote:
>> On Sat, Apr 26, 2014 at 3:22 PM, Adrien Nader  wrote:
>> > On Sat, Apr 26, 2014, Dongsheng Song wrote:
>> >> On Sat, Apr 26, 2014 at 12:31 AM, Adrien Nader  wrote:
>> >> > I believe --with-arch=core2 is a big issue for generic toolchains. It
>> >> > will create troubles which will be very annoying to pinpoint.
>> >> >
>> >> > Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
>> >> > already has SSE2 and there is little value in restricting this except in
>> >> > very specific situation which are better dealt on a case-by-case basis.
>> >> >
>> >> > Regards,
>> >> > Adrien Nader
>> >> >
>> >>
>> >> Do you really meet this issue ? I can not image someone still running
>> >> 64 bit Windows on such old CPU.
>> >>
>> >> Intel core2 release in July 2006, shutdown in January 2010.
>> >> http://en.wikipedia.org/wiki/Intel_Core_2
>> >
>> > I have troubles believing people still run XP but many do. :P
>> >
>> > The issue is rather when you look at the AMD CPUs.
>> > First models with SSE3 are from the end of 2007 (meaning you would still
>> > easily see machines with them at the end of 2008, even beginning of
>> > 2009).
>> > The real issue is with SSSE3 (one more 'S') since the first mobile CPUs
>> > with it have been released beginning of 2011 and the first desktop CPUs
>> > with it have been released end of 2011 are are still easily found.
>> >
>> > I have a machine without SSE3 in my living room (albeit it needs a new
>> > PSU), along with a machine without SSSE3 which is definitely running
>> > strong (in particular since the rate of CPU speed improvement has
>> > dramatically slowed down in the last few years).
>> >
>> > I don't think there is a point in making core2 the default; I don't
>> > think it will bring any improvements except when building multimedia
>> > stuff and even then it's not unlikely they don't provide hand-tuned
>> > assembly but even then, -mtune should do be able to bring the
>> > performance benefits on the newer CPUs while still running on the older
>> > ones.
>> >
>>
>> I agree with you the performance view.
>>
>> But from gcc view, Intel 64 cpu is: nocona, core2 or later. In my
>> memory, I never hear someone can run 64 bit windows on nocona without
>> problem. I know it's unfair for AMD CPUs, but both without -march and
>> with -march= give 3DNow defined, it's not acceptable for
>> Intel CPUs.
>
> "Intel 64" is a name that doesn't exist. It's either AMD64 (AMD
> parlance), EM64T (Intel parlance), x64 (Microsoft parlance) or x86_64
> (parlance of anyone not interested in marketing and propaganda). The
> first CPUs handling x86_64 date from 2003 and were server-class CPUs.
>
> Using "--with-arch=core2" means that there many CPUs sold during pretty
> much *10* years will not be able to run the programs compiled with these
> toolchains and will crash at surprising times in surprising ways.
>
> Right now I have a Windows 8 x86_64 VM running on a CPU from 2009 or
> 2010 without SSSE3. Actually it maybe doesn't have SSE3 either. I've
> never had issues with x86_64 stuff on it.
> I've also grabbed my XP 64 box and there's a cute logo of a Pentium 4.
> While everyone will agree XP 64 was far from perfect, I think it's a
> good indication that it worked at least for some people.
>
>
> As for not specifying any arch, I wasn't able to quickly find a
> reference or documentation on the matter. However, Linux distributions
> are a good example however: they run on all x86_64 CPUs and don't set
> anything specific and that's what a generic toolchain should do too.
>
> In any case, if not setting --with-arch makes code that cannot run on
> the triplet specified during the build of GCC (which I do not believe)
> then this is an issue in GCC and should be dealt in GCC and not
> worked-around (but again, I believe it is not the case).
>
> --
> Adrien Nader
>

Just pick Linux 64 bit gcc:

gcc -dM -E - < /dev/null | grep -i k8
#define __k8 1
#define __k8__ 1

>From http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86-64-Options.html , k8 is:

Processors based on the AMD K8 core with x86-64 instruction set
support, including the AMD Opteron, Athlon 64, and Athlon 64 FX
processors. (This supersets MMX, SSE, SSE2, 3DNow!, enhanced 3DNow!
and 64-bit instruction set extensions.)

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Adrien Nader]

On Sat, Apr 26, 2014, Dongsheng Song wrote:
> On Sat, Apr 26, 2014 at 3:22 PM, Adrien Nader  wrote:
> > On Sat, Apr 26, 2014, Dongsheng Song wrote:
> >> On Sat, Apr 26, 2014 at 12:31 AM, Adrien Nader  wrote:
> >> > I believe --with-arch=core2 is a big issue for generic toolchains. It
> >> > will create troubles which will be very annoying to pinpoint.
> >> >
> >> > Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
> >> > already has SSE2 and there is little value in restricting this except in
> >> > very specific situation which are better dealt on a case-by-case basis.
> >> >
> >> > Regards,
> >> > Adrien Nader
> >> >
> >>
> >> Do you really meet this issue ? I can not image someone still running
> >> 64 bit Windows on such old CPU.
> >>
> >> Intel core2 release in July 2006, shutdown in January 2010.
> >> http://en.wikipedia.org/wiki/Intel_Core_2
> >
> > I have troubles believing people still run XP but many do. :P
> >
> > The issue is rather when you look at the AMD CPUs.
> > First models with SSE3 are from the end of 2007 (meaning you would still
> > easily see machines with them at the end of 2008, even beginning of
> > 2009).
> > The real issue is with SSSE3 (one more 'S') since the first mobile CPUs
> > with it have been released beginning of 2011 and the first desktop CPUs
> > with it have been released end of 2011 are are still easily found.
> >
> > I have a machine without SSE3 in my living room (albeit it needs a new
> > PSU), along with a machine without SSSE3 which is definitely running
> > strong (in particular since the rate of CPU speed improvement has
> > dramatically slowed down in the last few years).
> >
> > I don't think there is a point in making core2 the default; I don't
> > think it will bring any improvements except when building multimedia
> > stuff and even then it's not unlikely they don't provide hand-tuned
> > assembly but even then, -mtune should do be able to bring the
> > performance benefits on the newer CPUs while still running on the older
> > ones.
> >
> 
> I agree with you the performance view.
> 
> But from gcc view, Intel 64 cpu is: nocona, core2 or later. In my
> memory, I never hear someone can run 64 bit windows on nocona without
> problem. I know it's unfair for AMD CPUs, but both without -march and
> with -march= give 3DNow defined, it's not acceptable for
> Intel CPUs.

"Intel 64" is a name that doesn't exist. It's either AMD64 (AMD
parlance), EM64T (Intel parlance), x64 (Microsoft parlance) or x86_64
(parlance of anyone not interested in marketing and propaganda). The
first CPUs handling x86_64 date from 2003 and were server-class CPUs.

Using "--with-arch=core2" means that there many CPUs sold during pretty
much *10* years will not be able to run the programs compiled with these
toolchains and will crash at surprising times in surprising ways.

Right now I have a Windows 8 x86_64 VM running on a CPU from 2009 or
2010 without SSSE3. Actually it maybe doesn't have SSE3 either. I've
never had issues with x86_64 stuff on it.
I've also grabbed my XP 64 box and there's a cute logo of a Pentium 4.
While everyone will agree XP 64 was far from perfect, I think it's a
good indication that it worked at least for some people.


As for not specifying any arch, I wasn't able to quickly find a
reference or documentation on the matter. However, Linux distributions
are a good example however: they run on all x86_64 CPUs and don't set
anything specific and that's what a generic toolchain should do too.

In any case, if not setting --with-arch makes code that cannot run on
the triplet specified during the build of GCC (which I do not believe)
then this is an issue in GCC and should be dealt in GCC and not
worked-around (but again, I believe it is not the case).

-- 
Adrien Nader

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[JonY]

On 4/26/2014 16:58, Dongsheng Song wrote:
> On Sat, Apr 26, 2014 at 4:47 PM, JonY  wrote:
>> On 4/26/2014 10:27, Matthew Brett wrote:
>>>
>>> I've had problems with sourceforge before.  It looks like, to allow
>>> people to upload, you have add the person as Developer or Admin, and
>>> then (this for the project 'numpy'):
>>>
>>> Go the 'tools' sidebar:
>>>   https://sourceforge.net/p/numpy/admin/tools
>>> Under Files, select Release Technicians:
>>>   https://sourceforge.net/p/numpy/admin/downloads/releasers/
>>> Click the box next to the developer's name.
>>>
>>> That seemed to work for other projects at least.
>>
>> Release manager can't release...
>>
>> Anyway, try again Dongsheng.
>>
> 
> Thanks, both web and sftp are OK now.
> How do you fix this issue ?

I followed Matthew's instructions, looks like it is working.




signature.asc
Description: OpenPGP digital signature
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

niXman 2014-04-26 13:53:
> try:
> $ ssh dongsheng,mingw-...@frs.sourceforge.net
ssh -t dongsheng,mingw-...@shell.sourceforge.net create

-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

Dongsheng Song 2014-04-26 12:22:
> $ sftp dongsheng,mingw-...@frs.sourceforge.net
try:
$ ssh dongsheng,mingw-...@frs.sourceforge.net

-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 4:47 PM, JonY  wrote:
> On 4/26/2014 10:27, Matthew Brett wrote:
>>
>> I've had problems with sourceforge before.  It looks like, to allow
>> people to upload, you have add the person as Developer or Admin, and
>> then (this for the project 'numpy'):
>>
>> Go the 'tools' sidebar:
>>   https://sourceforge.net/p/numpy/admin/tools
>> Under Files, select Release Technicians:
>>   https://sourceforge.net/p/numpy/admin/downloads/releasers/
>> Click the box next to the developer's name.
>>
>> That seemed to work for other projects at least.
>
> Release manager can't release...
>
> Anyway, try again Dongsheng.
>

Thanks, both web and sftp are OK now.
How do you fix this issue ?

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 3:22 PM, Adrien Nader  wrote:
> On Sat, Apr 26, 2014, Dongsheng Song wrote:
>> On Sat, Apr 26, 2014 at 12:31 AM, Adrien Nader  wrote:
>> > I believe --with-arch=core2 is a big issue for generic toolchains. It
>> > will create troubles which will be very annoying to pinpoint.
>> >
>> > Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
>> > already has SSE2 and there is little value in restricting this except in
>> > very specific situation which are better dealt on a case-by-case basis.
>> >
>> > Regards,
>> > Adrien Nader
>> >
>>
>> Do you really meet this issue ? I can not image someone still running
>> 64 bit Windows on such old CPU.
>>
>> Intel core2 release in July 2006, shutdown in January 2010.
>> http://en.wikipedia.org/wiki/Intel_Core_2
>
> I have troubles believing people still run XP but many do. :P
>
> The issue is rather when you look at the AMD CPUs.
> First models with SSE3 are from the end of 2007 (meaning you would still
> easily see machines with them at the end of 2008, even beginning of
> 2009).
> The real issue is with SSSE3 (one more 'S') since the first mobile CPUs
> with it have been released beginning of 2011 and the first desktop CPUs
> with it have been released end of 2011 are are still easily found.
>
> I have a machine without SSE3 in my living room (albeit it needs a new
> PSU), along with a machine without SSSE3 which is definitely running
> strong (in particular since the rate of CPU speed improvement has
> dramatically slowed down in the last few years).
>
> I don't think there is a point in making core2 the default; I don't
> think it will bring any improvements except when building multimedia
> stuff and even then it's not unlikely they don't provide hand-tuned
> assembly but even then, -mtune should do be able to bring the
> performance benefits on the newer CPUs while still running on the older
> ones.
>

I agree with you the performance view.

But from gcc view, Intel 64 cpu is: nocona, core2 or later. In my
memory, I never hear someone can run 64 bit windows on nocona without
problem. I know it's unfair for AMD CPUs, but both without -march and
with -march= give 3DNow defined, it's not acceptable for
Intel CPUs.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[JonY]

On 4/26/2014 10:27, Matthew Brett wrote:
> 
> I've had problems with sourceforge before.  It looks like, to allow
> people to upload, you have add the person as Developer or Admin, and
> then (this for the project 'numpy'):
> 
> Go the 'tools' sidebar:
>   https://sourceforge.net/p/numpy/admin/tools
> Under Files, select Release Technicians:
>   https://sourceforge.net/p/numpy/admin/downloads/releasers/
> Click the box next to the developer's name.
> 
> That seemed to work for other projects at least.

Release manager can't release...

Anyway, try again Dongsheng.





signature.asc
Description: OpenPGP digital signature
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 3:24 PM, JonY  wrote:
> On 4/26/2014 13:44, Dongsheng Song wrote:
>> On Sat, Apr 26, 2014 at 10:24 AM, niXman  wrote:
>>> Dongsheng Song 2014-04-26 06:17:
 Not help, still no 'Add File' or 'Add Folder'.
>>>
>>> I also can't see this buttons(bug?), but I use ShellService:
>>> https://sourceforge.net/p/forge/documentation/Shell%20Service/
>>>
>>
>> Thanks for your information.
>>
>> When I use ssh login, then 'sf-help --frs' said I did't have FRS on 
>> mingw-w64.
>> When I use sftp, 'docbook' and 'osb' is OK, mingw-w64 faild:
>>
>> $  sftp dongsheng,docb...@web.sourceforge.net
>> Connected to web.sourceforge.net.
>> sftp> exit
>>
>> $ sftp dongsheng,o...@web.sourceforge.net
>> Connected to web.sourceforge.net.
>> sftp> exit
>>
>> $ sftp dongsheng,mingw-...@web.sourceforge.net
>> Password:
>
> Try frs.sourceforge.net.
>

Still no luck.

$ sftp dongsheng,mingw-...@frs.sourceforge.net
Password:
Password:
Password:

$ sftp dongsheng,docb...@frs.sourceforge.net
Connected to frs.sourceforge.net.
sftp> exit

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[JonY]

On 4/26/2014 13:44, Dongsheng Song wrote:
> On Sat, Apr 26, 2014 at 10:24 AM, niXman  wrote:
>> Dongsheng Song 2014-04-26 06:17:
>>> Not help, still no 'Add File' or 'Add Folder'.
>>
>> I also can't see this buttons(bug?), but I use ShellService:
>> https://sourceforge.net/p/forge/documentation/Shell%20Service/
>>
> 
> Thanks for your information.
> 
> When I use ssh login, then 'sf-help --frs' said I did't have FRS on mingw-w64.
> When I use sftp, 'docbook' and 'osb' is OK, mingw-w64 faild:
> 
> $  sftp dongsheng,docb...@web.sourceforge.net
> Connected to web.sourceforge.net.
> sftp> exit
> 
> $ sftp dongsheng,o...@web.sourceforge.net
> Connected to web.sourceforge.net.
> sftp> exit
> 
> $ sftp dongsheng,mingw-...@web.sourceforge.net
> Password:

Try frs.sourceforge.net.





signature.asc
Description: OpenPGP digital signature
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Adrien Nader]

On Sat, Apr 26, 2014, Dongsheng Song wrote:
> On Sat, Apr 26, 2014 at 12:31 AM, Adrien Nader  wrote:
> > I believe --with-arch=core2 is a big issue for generic toolchains. It
> > will create troubles which will be very annoying to pinpoint.
> >
> > Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
> > already has SSE2 and there is little value in restricting this except in
> > very specific situation which are better dealt on a case-by-case basis.
> >
> > Regards,
> > Adrien Nader
> >
> 
> Do you really meet this issue ? I can not image someone still running
> 64 bit Windows on such old CPU.
> 
> Intel core2 release in July 2006, shutdown in January 2010.
> http://en.wikipedia.org/wiki/Intel_Core_2

I have troubles believing people still run XP but many do. :P 

The issue is rather when you look at the AMD CPUs.
First models with SSE3 are from the end of 2007 (meaning you would still
easily see machines with them at the end of 2008, even beginning of
2009).
The real issue is with SSSE3 (one more 'S') since the first mobile CPUs
with it have been released beginning of 2011 and the first desktop CPUs
with it have been released end of 2011 are are still easily found.

I have a machine without SSE3 in my living room (albeit it needs a new
PSU), along with a machine without SSSE3 which is definitely running
strong (in particular since the rate of CPU speed improvement has
dramatically slowed down in the last few years).

I don't think there is a point in making core2 the default; I don't
think it will bring any improvements except when building multimedia
stuff and even then it's not unlikely they don't provide hand-tuned
assembly but even then, -mtune should do be able to bring the
performance benefits on the newer CPUs while still running on the older
ones.

-- 
Adrien Nader

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 10:24 AM, niXman  wrote:
> Dongsheng Song 2014-04-26 06:17:
>> Not help, still no 'Add File' or 'Add Folder'.
>
> I also can't see this buttons(bug?), but I use ShellService:
> https://sourceforge.net/p/forge/documentation/Shell%20Service/
>

Thanks for your information.

When I use ssh login, then 'sf-help --frs' said I did't have FRS on mingw-w64.
When I use sftp, 'docbook' and 'osb' is OK, mingw-w64 faild:

$  sftp dongsheng,docb...@web.sourceforge.net
Connected to web.sourceforge.net.
sftp> exit

$ sftp dongsheng,o...@web.sourceforge.net
Connected to web.sourceforge.net.
sftp> exit

$ sftp dongsheng,mingw-...@web.sourceforge.net
Password:

Then I assume I have no enough permission on mingw-w64.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 8:32 AM, JonY  wrote:
> On 4/25/2014 22:54, Ruben Van Boxem wrote:
>>>
>>> Add --enable-fully-dynamic-string and
>>>
>>
>> Shouldn't this already be enabled by default (you worked on a patch for
>> that which IIANM I tested back then)?
>>
>>
>
> I can't remember if I did :)
>
>>> --enable-version-specific-runtime-libs and everything is good.
>>>
>>
>> This isn't strictly necessary and in my experience is quite troublesome
>> ("can't find -lgcc_eh" as a result)
>>
>
> This is a long standing bug, it happens with Linux versions also, but
> after moving things into place, you end up with a far tidier install.
> This workaround can be scripted for post-install.
>
> You can drop your libdir with custom headers/libraries into a new
> version of GCC and it'll work without another version of GCC clashing in.
>

In my testing, gcc 4.7 got this error. gcc 4.8, 4.9 and 4.10 is OK.

This only move some version and arch specific files to compiler
specific directory. Since the binary files in the same location and
have same name, I don't think this option have value.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 12:31 AM, Adrien Nader  wrote:
> I believe --with-arch=core2 is a big issue for generic toolchains. It
> will create troubles which will be very annoying to pinpoint.
>
> Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
> already has SSE2 and there is little value in restricting this except in
> very specific situation which are better dealt on a case-by-case basis.
>
> Regards,
> Adrien Nader
>

Do you really meet this issue ? I can not image someone still running
64 bit Windows on such old CPU.

Intel core2 release in July 2006, shutdown in January 2010.
http://en.wikipedia.org/wiki/Intel_Core_2

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Matthew Brett]

Hi,

On Fri, Apr 25, 2014 at 7:17 PM, Dongsheng Song
 wrote:
> On Sat, Apr 26, 2014 at 8:35 AM, JonY  wrote:
>> On 4/25/2014 23:37, Dongsheng Song wrote:
 You may need to use winpthread if you want to use --enable-libgomp.

>>>
>>> Yes. In my situation, we dont't need winpthread. Since we only support
>>> Windows 7.1 and Server 2008 R2 or later, winpthread is too heavy for
>>> us.
>>>
>>
>> Sure, 7.1?
>>
>
> Sorry for typo, it's Windows 7 SP1.
>
 I have now added your login to allow uploads, please upload to somewhere
 like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
>>>
>>> I can see MinGW-w64 in my projects, but I can not see 'Add File' or
>>> 'Add Folder'  in ' /files/Toolchains targetting Win64/Personal
>>> Builds/' or '/files/Toolchains targetting Win32/'.
>>
>> Try logging out and coming back in again? Not sure if that will help.
>>
>
> Not help, still no 'Add File' or 'Add Folder'.

I've had problems with sourceforge before.  It looks like, to allow
people to upload, you have add the person as Developer or Admin, and
then (this for the project 'numpy'):

Go the 'tools' sidebar:
  https://sourceforge.net/p/numpy/admin/tools
Under Files, select Release Technicians:
  https://sourceforge.net/p/numpy/admin/downloads/releasers/
Click the box next to the developer's name.

That seemed to work for other projects at least.

Cheers,

Matthew

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

Dongsheng Song 2014-04-26 06:17:
> Not help, still no 'Add File' or 'Add Folder'.

I also can't see this buttons(bug?), but I use ShellService:
https://sourceforge.net/p/forge/documentation/Shell%20Service/


-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 8:35 AM, JonY  wrote:
> On 4/25/2014 23:37, Dongsheng Song wrote:
>>> You may need to use winpthread if you want to use --enable-libgomp.
>>>
>>
>> Yes. In my situation, we dont't need winpthread. Since we only support
>> Windows 7.1 and Server 2008 R2 or later, winpthread is too heavy for
>> us.
>>
>
> Sure, 7.1?
>

Sorry for typo, it's Windows 7 SP1.

>>> I have now added your login to allow uploads, please upload to somewhere
>>> like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
>>
>> I can see MinGW-w64 in my projects, but I can not see 'Add File' or
>> 'Add Folder'  in ' /files/Toolchains targetting Win64/Personal
>> Builds/' or '/files/Toolchains targetting Win32/'.
>
> Try logging out and coming back in again? Not sure if that will help.
>

Not help, still no 'Add File' or 'Add Folder'.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Sat, Apr 26, 2014 at 12:40 AM, xunxun  wrote:
>
> Did you use any patches or scripts for your build?
>

NO.  Just put build commands in a bash script.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[JonY]

On 4/25/2014 23:37, Dongsheng Song wrote:
>> You may need to use winpthread if you want to use --enable-libgomp.
>>
> 
> Yes. In my situation, we dont't need winpthread. Since we only support
> Windows 7.1 and Server 2008 R2 or later, winpthread is too heavy for
> us.
> 

Sure, 7.1?

>> I have now added your login to allow uploads, please upload to somewhere
>> like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
> 
> I can see MinGW-w64 in my projects, but I can not see 'Add File' or
> 'Add Folder'  in ' /files/Toolchains targetting Win64/Personal
> Builds/' or '/files/Toolchains targetting Win32/'.

Try logging out and coming back in again? Not sure if that will help.






signature.asc
Description: OpenPGP digital signature
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[JonY]

On 4/25/2014 22:54, Ruben Van Boxem wrote:
>>
>> Add --enable-fully-dynamic-string and
>>
> 
> Shouldn't this already be enabled by default (you worked on a patch for
> that which IIANM I tested back then)?
> 
> 

I can't remember if I did :)

>> --enable-version-specific-runtime-libs and everything is good.
>>
> 
> This isn't strictly necessary and in my experience is quite troublesome
> ("can't find -lgcc_eh" as a result)
> 

This is a long standing bug, it happens with Linux versions also, but
after moving things into place, you end up with a far tidier install.
This workaround can be scripted for post-install.

You can drop your libdir with custom headers/libraries into a new
version of GCC and it'll work without another version of GCC clashing in.





signature.asc
Description: OpenPGP digital signature
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Adrien Nader]

On Fri, Apr 25, 2014, LRN wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 25.04.2014 20:31, Adrien Nader wrote:
> > On Fri, Apr 25, 2014, JonY wrote:
> >> On 4/25/2014 21:17, Dongsheng Song wrote:
> >>> On Fri, Apr 25, 2014 at 6:50 PM, JonY  
> >>> wrote:
>  On 4/25/2014 17:47, Dongsheng Song wrote:
> > I'm glad to upload my daily builds to mingw-w64, if someone 
> > intersting and give me (dongsheng) permission.
> > 
>  
>  What is your configuration like? And what exactly do you have in 
>  your download?
>  
> >>> 
> >>> For win64: ${GCC_SRC_ROOT}/configure \ --prefix=${SYS_ROOT} \ 
> >>> --with-sysroot=${SYS_ROOT} \ --build=${BUILD_TRIPLET} 
> >>> --host=${TARGET_TRIPLET} --target=${TARGET_TRIPLET} \ 
> >>> --disable-multilib --disable-nls --disable-win32-registry \ 
> >>> --enable-checking=release --enable-languages=c,c++,fortran \ 
> >>> --with-arch=core2 --with-tune=generic
> >>> 
> >>> For win32: ${GCC_SRC_ROOT}/configure \ --prefix=${SYS_ROOT} \ 
> >>> --with-sysroot=${SYS_ROOT} \ --build=${BUILD_TRIPLET} 
> >>> --host=${TARGET_TRIPLET} --target=${TARGET_TRIPLET} \ 
> >>> --disable-multilib --disable-nls --disable-win32-registry \ 
> >>> --enable-checking=release --enable-languages=c,c++,fortran \ 
> >>> --with-arch=i686 --with-tune=generic
> >>> 
> >> 
> >> Add --enable-fully-dynamic-string and 
> >> --enable-version-specific-runtime-libs and everything is good.
> >> 
> >> You may need to use winpthread if you want to use --enable-libgomp.
> >> 
> >> I have now added your login to allow uploads, please upload to somewhere
> >> like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
> >> probably a good idea to rotate the files weekly to prevent uploads from
> >> getting too big (if there is such a thing as too big).
> >> 
> > 
> > I believe --with-arch=core2 is a big issue for generic toolchains. It
> > will create troubles which will be very annoying to pinpoint.
> > 
> > Any x86_64/amd64/EM64T (I love how Intel always makes up awful names) 
> > already has SSE2 and there is little value in restricting this except in 
> > very specific situation which are better dealt on a case-by-case basis.
> > 
> 
> [un-]related:
> 
> desrt: https://bugzilla.gnome.org/show_bug.cgi?id=722604#c7
> Services: Bug 722604: normal, Normal, ---, gtkdev, NEW, Various tests are
> failing with 2.39.3
> desrt: mclasen: the test is failing because of a gcc bug
> desrt: but gcc is 'buggy by design' according to upstream
> desrt: since following the spec would be expensive on machines that don't
> have SSE instructions
> desrt: (ie: chips made in the 1990s)
> desrt: and since most distros have -march=i686 or worse, gcc has no choice
> but to either (a) be slow or (b) violate spec
> desrt: and they pick (b)
> desrt: imho we should insist on a standards-complying C compiler -- and it's
> quite possible to get gcc to do the right thing with a CFLAG or two...
> desrt: upshot is that we will get distros providing some custom CFLAGS when
> building glib -- but hopefully eventually evaluating their choice of default
> CFLAGS and making changes there
> desrt: either that or they just patch out the failing testcases...
> mclasen: so, you're expecting distros to choose correct over fast, when
> upstream gcc does ?
> mclasen: does not, I should say
> desrt: i'm expecting distros to reevaluate if they still want to support
> chips from the 90s
> desrt: i don't honestly think anyone would want to pick the "let's be slow"
> choice
> desrt: but i also think people are generally unaware of the issue...
> desrt: so mostly i aim to raise the visibility of the problem
> desrt: also making people fully aware of the costs of supporting correct ISO
> C on these old chips...
> LRN: so, -match=i686 is expensive?
> desrt: LRN: expensive or incorrect. take your pick.
> desrt: LRN: gcc picks 'incorrect', for the record
> LRN: i build glib with -march=i686 :(
> desrt: LRN: ya... so do all the distros...
> ***desrt thinks that nobody really knows about this issue
> ***desrt recommends -march=pentium4 -mfpmath=sse
> LRN: no, i mean i *specifically* build *glib* with -march=i686, because it
> won't compile without that (i.e. with the default). At least it didn't back
> when i made a first build
> desrt: LRN: i think we depend on at least -march=i486 for atomic
> compare-and-exchange instructions
> LRN: yes, that's the reason.
> daniels: desrt: ouch, if you have -march=pentium4, you probably want a -mtune
> for a less-horrific microarch
> desrt: daniels: ya.. -mtune=generic might make sense
> desrt: in general, having access to sse/sse2 would be wonderful

I think --with-arch=pentium3 is fine for that and it has SSE. If I
checked correctly last time, you won't find XP machines without at least
that.

-- 
Adrien Nader

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo 

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

xunxun 2014-04-25 21:14:
> Well, I want to ask Dongsheng

Oh, sorry.

-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[LRN]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 25.04.2014 20:31, Adrien Nader wrote:
> On Fri, Apr 25, 2014, JonY wrote:
>> On 4/25/2014 21:17, Dongsheng Song wrote:
>>> On Fri, Apr 25, 2014 at 6:50 PM, JonY  
>>> wrote:
 On 4/25/2014 17:47, Dongsheng Song wrote:
> I'm glad to upload my daily builds to mingw-w64, if someone 
> intersting and give me (dongsheng) permission.
> 
 
 What is your configuration like? And what exactly do you have in 
 your download?
 
>>> 
>>> For win64: ${GCC_SRC_ROOT}/configure \ --prefix=${SYS_ROOT} \ 
>>> --with-sysroot=${SYS_ROOT} \ --build=${BUILD_TRIPLET} 
>>> --host=${TARGET_TRIPLET} --target=${TARGET_TRIPLET} \ 
>>> --disable-multilib --disable-nls --disable-win32-registry \ 
>>> --enable-checking=release --enable-languages=c,c++,fortran \ 
>>> --with-arch=core2 --with-tune=generic
>>> 
>>> For win32: ${GCC_SRC_ROOT}/configure \ --prefix=${SYS_ROOT} \ 
>>> --with-sysroot=${SYS_ROOT} \ --build=${BUILD_TRIPLET} 
>>> --host=${TARGET_TRIPLET} --target=${TARGET_TRIPLET} \ 
>>> --disable-multilib --disable-nls --disable-win32-registry \ 
>>> --enable-checking=release --enable-languages=c,c++,fortran \ 
>>> --with-arch=i686 --with-tune=generic
>>> 
>> 
>> Add --enable-fully-dynamic-string and 
>> --enable-version-specific-runtime-libs and everything is good.
>> 
>> You may need to use winpthread if you want to use --enable-libgomp.
>> 
>> I have now added your login to allow uploads, please upload to somewhere
>> like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
>> probably a good idea to rotate the files weekly to prevent uploads from
>> getting too big (if there is such a thing as too big).
>> 
> 
> I believe --with-arch=core2 is a big issue for generic toolchains. It
> will create troubles which will be very annoying to pinpoint.
> 
> Any x86_64/amd64/EM64T (I love how Intel always makes up awful names) 
> already has SSE2 and there is little value in restricting this except in 
> very specific situation which are better dealt on a case-by-case basis.
> 

[un-]related:

desrt: https://bugzilla.gnome.org/show_bug.cgi?id=722604#c7
Services: Bug 722604: normal, Normal, ---, gtkdev, NEW, Various tests are
failing with 2.39.3
desrt: mclasen: the test is failing because of a gcc bug
desrt: but gcc is 'buggy by design' according to upstream
desrt: since following the spec would be expensive on machines that don't
have SSE instructions
desrt: (ie: chips made in the 1990s)
desrt: and since most distros have -march=i686 or worse, gcc has no choice
but to either (a) be slow or (b) violate spec
desrt: and they pick (b)
desrt: imho we should insist on a standards-complying C compiler -- and it's
quite possible to get gcc to do the right thing with a CFLAG or two...
desrt: upshot is that we will get distros providing some custom CFLAGS when
building glib -- but hopefully eventually evaluating their choice of default
CFLAGS and making changes there
desrt: either that or they just patch out the failing testcases...
mclasen: so, you're expecting distros to choose correct over fast, when
upstream gcc does ?
mclasen: does not, I should say
desrt: i'm expecting distros to reevaluate if they still want to support
chips from the 90s
desrt: i don't honestly think anyone would want to pick the "let's be slow"
choice
desrt: but i also think people are generally unaware of the issue...
desrt: so mostly i aim to raise the visibility of the problem
desrt: also making people fully aware of the costs of supporting correct ISO
C on these old chips...
LRN: so, -match=i686 is expensive?
desrt: LRN: expensive or incorrect. take your pick.
desrt: LRN: gcc picks 'incorrect', for the record
LRN: i build glib with -march=i686 :(
desrt: LRN: ya... so do all the distros...
***desrt thinks that nobody really knows about this issue
***desrt recommends -march=pentium4 -mfpmath=sse
LRN: no, i mean i *specifically* build *glib* with -march=i686, because it
won't compile without that (i.e. with the default). At least it didn't back
when i made a first build
desrt: LRN: i think we depend on at least -march=i486 for atomic
compare-and-exchange instructions
LRN: yes, that's the reason.
daniels: desrt: ouch, if you have -march=pentium4, you probably want a -mtune
for a less-horrific microarch
desrt: daniels: ya.. -mtune=generic might make sense
desrt: in general, having access to sse/sse2 would be wonderful

- -- 
O< ascii ribbon - stop html email! - www.asciiribbon.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (MingW32)

iQEcBAEBAgAGBQJTWptFAAoJEOs4Jb6SI2CwPp8IAJVRs5Q3odRn98km44mm+GCX
xqvXVT0mwT9uc4P66lRzmIcso5QFzoUg47iPFx6U4tmy8C2jefI/Lxbc0dJkaxyS
HXfe4jmcNqslFH4/Vl8evkbE7PqBCIpNFFO9ArFW9VUMEZSe9ixYTmxsIqBv3ScF
utkubg6gJfrQOuDnwd6nGez/g8XdAChnFBOLV5l3y1bKj6kNAWrcw0Wp2ZMDkAsc
F9VZBle4rsz8zMrBfPnAI6Kc8udWTtyPUIjBO2MEVCtaXf0/BMrL6tKN2bAWMMIk
9O+NkHJ6/fsmQAaXxM/dYohuy9S9snDO3kFMuiIloD0ywCieMGH8d87hsox5SBw=
=NGsj
-END PGP SIGNATURE-

-

Re: [Mingw-w64-public] [Project News | New Builds]

[xunxun]

Well, I want to ask Dongsheng
在 2014-4-26 上午1:06，"niXman" 写道：
>
> xunxun 2014-04-25 20:40:
>
> > Did you use any patches <...> for your build?
> Yes:
>
https://github.com/niXman/mingw-builds/blob/develop/scripts/gcc-4.9.0.sh#L50
>
> > Did you use any <...> scripts for your build?
> Yes: https://github.com/niXman/mingw-builds/
>
>
> --
> Regards, niXman
> ___
> Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
> http://sourceforge.net/projects/mingw-w64/
> ___
> Another online IDE: http://liveworkspace.org/
>
>
--
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

xunxun 2014-04-25 20:40:

> Did you use any patches <...> for your build?
Yes: 
https://github.com/niXman/mingw-builds/blob/develop/scripts/gcc-4.9.0.sh#L50

> Did you use any <...> scripts for your build?
Yes: https://github.com/niXman/mingw-builds/


-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[xunxun]

于 2014/4/25 星期五 17:32, Dongsheng Song 写道:
> On Fri, Apr 25, 2014 at 4:39 PM, niXman  wrote:
>> Hi,
>>
>> Just now I uploaded the first builds of MinGW-W64 based on GCC-4.9.0.
>>
>> Links:
>> 32-bit:
>>   posix-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/i686-4.9.0-release-posix-sjlj-rt_v3-rev0.7z
>>   posix-dwarf:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/dwarf/i686-4.9.0-release-posix-dwarf-rt_v3-rev0.7z
>>   win32-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-win32/sjlj/i686-4.9.0-release-win32-sjlj-rt_v3-rev0.7z
>>   win32-dwarf:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-win32/dwarf/i686-4.9.0-release-win32-dwarf-rt_v3-rev0.7z
>>
>> 64-bit:
>>   posix-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/x86_64-4.9.0-release-posix-sjlj-rt_v3-rev0.7z
>>   posix-seh:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/seh/x86_64-4.9.0-release-posix-seh-rt_v3-rev0.7z
>>   win32-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-win32/sjlj/x86_64-4.9.0-release-win32-sjlj-rt_v3-rev0.7z
>>   win32-seh:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-win32/seh/x86_64-4.9.0-release-win32-seh-rt_v3-rev0.7z
>>
>>
>>
>> --
>> Regards, niXman
>>
> Here is GCC daily builds with default configuration:
>
> https://sourceforge.net/projects/osb/files/gcc/
>
> --
> Dongsheng
>
>

Did you use any patches or scripts for your build?

-- 
Best Regards,
xunxun

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Adrien Nader]

On Fri, Apr 25, 2014, Adrien Nader wrote:
> On Fri, Apr 25, 2014, JonY wrote:
> > On 4/25/2014 21:17, Dongsheng Song wrote:
> > > On Fri, Apr 25, 2014 at 6:50 PM, JonY  wrote:
> > >> On 4/25/2014 17:47, Dongsheng Song wrote:
> > >>> I'm glad to upload my daily builds to mingw-w64, if someone intersting
> > >>> and give me (dongsheng) permission.
> > >>>
> > >>
> > >> What is your configuration like? And what exactly do you have in your
> > >> download?
> > >>
> > > 
> > > For win64:
> > > ${GCC_SRC_ROOT}/configure \
> > > --prefix=${SYS_ROOT} \
> > > --with-sysroot=${SYS_ROOT} \
> > > --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> > > --target=${TARGET_TRIPLET} \
> > > --disable-multilib --disable-nls --disable-win32-registry \
> > > --enable-checking=release --enable-languages=c,c++,fortran \
> > > --with-arch=core2 --with-tune=generic
> > > 
> > > For win32:
> > > ${GCC_SRC_ROOT}/configure \
> > > --prefix=${SYS_ROOT} \
> > > --with-sysroot=${SYS_ROOT} \
> > > --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> > > --target=${TARGET_TRIPLET} \
> > > --disable-multilib --disable-nls --disable-win32-registry \
> > > --enable-checking=release --enable-languages=c,c++,fortran \
> > > --with-arch=i686 --with-tune=generic
> > > 
> > 
> > Add --enable-fully-dynamic-string and
> > --enable-version-specific-runtime-libs and everything is good.
> > 
> > You may need to use winpthread if you want to use --enable-libgomp.
> > 
> > I have now added your login to allow uploads, please upload to somewhere
> > like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
> > probably a good idea to rotate the files weekly to prevent uploads from
> > getting too big (if there is such a thing as too big).
> > 
> 
> I believe --with-arch=core2 is a big issue for generic toolchains. It
> will create troubles which will be very annoying to pinpoint.
> 
> Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
> already has SSE2 and there is little value in restricting this except in
> very specific situation which are better dealt on a case-by-case basis.

The additions are SSE3 and SSSE3 specifically.

-- 
Adrien Nader

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Adrien Nader]

On Fri, Apr 25, 2014, JonY wrote:
> On 4/25/2014 21:17, Dongsheng Song wrote:
> > On Fri, Apr 25, 2014 at 6:50 PM, JonY  wrote:
> >> On 4/25/2014 17:47, Dongsheng Song wrote:
> >>> I'm glad to upload my daily builds to mingw-w64, if someone intersting
> >>> and give me (dongsheng) permission.
> >>>
> >>
> >> What is your configuration like? And what exactly do you have in your
> >> download?
> >>
> > 
> > For win64:
> > ${GCC_SRC_ROOT}/configure \
> > --prefix=${SYS_ROOT} \
> > --with-sysroot=${SYS_ROOT} \
> > --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> > --target=${TARGET_TRIPLET} \
> > --disable-multilib --disable-nls --disable-win32-registry \
> > --enable-checking=release --enable-languages=c,c++,fortran \
> > --with-arch=core2 --with-tune=generic
> > 
> > For win32:
> > ${GCC_SRC_ROOT}/configure \
> > --prefix=${SYS_ROOT} \
> > --with-sysroot=${SYS_ROOT} \
> > --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> > --target=${TARGET_TRIPLET} \
> > --disable-multilib --disable-nls --disable-win32-registry \
> > --enable-checking=release --enable-languages=c,c++,fortran \
> > --with-arch=i686 --with-tune=generic
> > 
> 
> Add --enable-fully-dynamic-string and
> --enable-version-specific-runtime-libs and everything is good.
> 
> You may need to use winpthread if you want to use --enable-libgomp.
> 
> I have now added your login to allow uploads, please upload to somewhere
> like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
> probably a good idea to rotate the files weekly to prevent uploads from
> getting too big (if there is such a thing as too big).
> 

I believe --with-arch=core2 is a big issue for generic toolchains. It
will create troubles which will be very annoying to pinpoint.

Any x86_64/amd64/EM64T (I love how Intel always makes up awful names)
already has SSE2 and there is little value in restricting this except in
very specific situation which are better dealt on a case-by-case basis.

Regards,
Adrien Nader

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[xunxun]

于 2014/4/25 星期五 22:54, Ruben Van Boxem 写道:
2014-04-25 16:34 GMT+02:00 JonY >:


On 4/25/2014 21:17, Dongsheng Song wrote:
> On Fri, Apr 25, 2014 at 6:50 PM, JonY
mailto:jo...@users.sourceforge.net>>
wrote:
>> On 4/25/2014 17:47, Dongsheng Song wrote:
>>> I'm glad to upload my daily builds to mingw-w64, if someone
intersting
>>> and give me (dongsheng) permission.
>>>
>>
>> What is your configuration like? And what exactly do you have
in your
>> download?
>>
>
> For win64:
> ${GCC_SRC_ROOT}/configure \
> --prefix=${SYS_ROOT} \
> --with-sysroot=${SYS_ROOT} \
> --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> --target=${TARGET_TRIPLET} \
> --disable-multilib --disable-nls --disable-win32-registry \
> --enable-checking=release --enable-languages=c,c++,fortran \
> --with-arch=core2 --with-tune=generic
>
> For win32:
> ${GCC_SRC_ROOT}/configure \
> --prefix=${SYS_ROOT} \
> --with-sysroot=${SYS_ROOT} \
> --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> --target=${TARGET_TRIPLET} \
> --disable-multilib --disable-nls --disable-win32-registry \
> --enable-checking=release --enable-languages=c,c++,fortran \
> --with-arch=i686 --with-tune=generic
>

Add --enable-fully-dynamic-string and


Shouldn't this already be enabled by default (you worked on a patch 
for that which IIANM I tested back then)?

Should be a default option for MinGW64 target, but not for MinGW target.


--enable-version-specific-runtime-libs and everything is good.


This isn't strictly necessary and in my experience is quite 
troublesome ("can't find -lgcc_eh" as a result)


Cheers,

Ruben


You may need to use winpthread if you want to use --enable-libgomp.

I have now added your login to allow uploads, please upload to
somewhere
like "Toolchains targetting Win{32,64}/Personal
Builds/dongsheng-daily".
probably a good idea to rotate the files weekly to prevent uploads
from
getting too big (if there is such a thing as too big).




--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/mingw-w64-public




--



--
Best Regards,
xunxun
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Fri, Apr 25, 2014 at 10:34 PM, JonY  wrote:
> Add --enable-fully-dynamic-string and
> --enable-version-specific-runtime-libs and everything is good.
>

I will testing with these options.

> You may need to use winpthread if you want to use --enable-libgomp.
>

Yes. In my situation, we dont't need winpthread. Since we only support
Windows 7.1 and Server 2008 R2 or later, winpthread is too heavy for
us.

> I have now added your login to allow uploads, please upload to somewhere
> like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".

I can see MinGW-w64 in my projects, but I can not see 'Add File' or
'Add Folder'  in ' /files/Toolchains targetting Win64/Personal
Builds/' or '/files/Toolchains targetting Win32/'.

> probably a good idea to rotate the files weekly to prevent uploads from
> getting too big (if there is such a thing as too big).
>

Yes, we can delete old files with 0 downloads periodically.

Regards,
Dongsheng

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Ruben Van Boxem]

2014-04-25 16:34 GMT+02:00 JonY :

> On 4/25/2014 21:17, Dongsheng Song wrote:
> > On Fri, Apr 25, 2014 at 6:50 PM, JonY 
> wrote:
> >> On 4/25/2014 17:47, Dongsheng Song wrote:
> >>> I'm glad to upload my daily builds to mingw-w64, if someone intersting
> >>> and give me (dongsheng) permission.
> >>>
> >>
> >> What is your configuration like? And what exactly do you have in your
> >> download?
> >>
> >
> > For win64:
> > ${GCC_SRC_ROOT}/configure \
> > --prefix=${SYS_ROOT} \
> > --with-sysroot=${SYS_ROOT} \
> > --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> > --target=${TARGET_TRIPLET} \
> > --disable-multilib --disable-nls --disable-win32-registry \
> > --enable-checking=release --enable-languages=c,c++,fortran \
> > --with-arch=core2 --with-tune=generic
> >
> > For win32:
> > ${GCC_SRC_ROOT}/configure \
> > --prefix=${SYS_ROOT} \
> > --with-sysroot=${SYS_ROOT} \
> > --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> > --target=${TARGET_TRIPLET} \
> > --disable-multilib --disable-nls --disable-win32-registry \
> > --enable-checking=release --enable-languages=c,c++,fortran \
> > --with-arch=i686 --with-tune=generic
> >
>
> Add --enable-fully-dynamic-string and
>

Shouldn't this already be enabled by default (you worked on a patch for
that which IIANM I tested back then)?


> --enable-version-specific-runtime-libs and everything is good.
>

This isn't strictly necessary and in my experience is quite troublesome
("can't find -lgcc_eh" as a result)

Cheers,

Ruben


>
> You may need to use winpthread if you want to use --enable-libgomp.
>
> I have now added your login to allow uploads, please upload to somewhere
> like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
> probably a good idea to rotate the files weekly to prevent uploads from
> getting too big (if there is such a thing as too big).
>
>
>
>
> --
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[JonY]

On 4/25/2014 21:17, Dongsheng Song wrote:
> On Fri, Apr 25, 2014 at 6:50 PM, JonY  wrote:
>> On 4/25/2014 17:47, Dongsheng Song wrote:
>>> I'm glad to upload my daily builds to mingw-w64, if someone intersting
>>> and give me (dongsheng) permission.
>>>
>>
>> What is your configuration like? And what exactly do you have in your
>> download?
>>
> 
> For win64:
> ${GCC_SRC_ROOT}/configure \
> --prefix=${SYS_ROOT} \
> --with-sysroot=${SYS_ROOT} \
> --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> --target=${TARGET_TRIPLET} \
> --disable-multilib --disable-nls --disable-win32-registry \
> --enable-checking=release --enable-languages=c,c++,fortran \
> --with-arch=core2 --with-tune=generic
> 
> For win32:
> ${GCC_SRC_ROOT}/configure \
> --prefix=${SYS_ROOT} \
> --with-sysroot=${SYS_ROOT} \
> --build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
> --target=${TARGET_TRIPLET} \
> --disable-multilib --disable-nls --disable-win32-registry \
> --enable-checking=release --enable-languages=c,c++,fortran \
> --with-arch=i686 --with-tune=generic
> 

Add --enable-fully-dynamic-string and
--enable-version-specific-runtime-libs and everything is good.

You may need to use winpthread if you want to use --enable-libgomp.

I have now added your login to allow uploads, please upload to somewhere
like "Toolchains targetting Win{32,64}/Personal Builds/dongsheng-daily".
probably a good idea to rotate the files weekly to prevent uploads from
getting too big (if there is such a thing as too big).




signature.asc
Description: OpenPGP digital signature
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Fri, Apr 25, 2014 at 6:50 PM, JonY  wrote:
> On 4/25/2014 17:47, Dongsheng Song wrote:
>> I'm glad to upload my daily builds to mingw-w64, if someone intersting
>> and give me (dongsheng) permission.
>>
>
> What is your configuration like? And what exactly do you have in your
> download?
>

For win64:
${GCC_SRC_ROOT}/configure \
--prefix=${SYS_ROOT} \
--with-sysroot=${SYS_ROOT} \
--build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
--target=${TARGET_TRIPLET} \
--disable-multilib --disable-nls --disable-win32-registry \
--enable-checking=release --enable-languages=c,c++,fortran \
--with-arch=core2 --with-tune=generic

For win32:
${GCC_SRC_ROOT}/configure \
--prefix=${SYS_ROOT} \
--with-sysroot=${SYS_ROOT} \
--build=${BUILD_TRIPLET} --host=${TARGET_TRIPLET}
--target=${TARGET_TRIPLET} \
--disable-multilib --disable-nls --disable-win32-registry \
--enable-checking=release --enable-languages=c,c++,fortran \
--with-arch=i686 --with-tune=generic

All packages have:
version.txt: The 3rd software version and download address, the svn
version of mingw-w64 and gcc.
The binary files of binutils, make, gdb and gcc.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[JonY]

On 4/25/2014 17:47, Dongsheng Song wrote:
> I'm glad to upload my daily builds to mingw-w64, if someone intersting
> and give me (dongsheng) permission.
> 

What is your configuration like? And what exactly do you have in your
download?




signature.asc
Description: OpenPGP digital signature
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Fri, Apr 25, 2014 at 5:32 PM, Dongsheng Song
 wrote:
> On Fri, Apr 25, 2014 at 4:39 PM, niXman  wrote:
>> Hi,
>>
>> Just now I uploaded the first builds of MinGW-W64 based on GCC-4.9.0.
>>
>> Links:
>> 32-bit:
>>  posix-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/i686-4.9.0-release-posix-sjlj-rt_v3-rev0.7z
>>  posix-dwarf:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/dwarf/i686-4.9.0-release-posix-dwarf-rt_v3-rev0.7z
>>  win32-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-win32/sjlj/i686-4.9.0-release-win32-sjlj-rt_v3-rev0.7z
>>  win32-dwarf:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-win32/dwarf/i686-4.9.0-release-win32-dwarf-rt_v3-rev0.7z
>>
>> 64-bit:
>>  posix-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/x86_64-4.9.0-release-posix-sjlj-rt_v3-rev0.7z
>>  posix-seh:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/seh/x86_64-4.9.0-release-posix-seh-rt_v3-rev0.7z
>>  win32-sjlj:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-win32/sjlj/x86_64-4.9.0-release-win32-sjlj-rt_v3-rev0.7z
>>  win32-seh:
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-win32/seh/x86_64-4.9.0-release-win32-seh-rt_v3-rev0.7z
>>
>>
>>
>> --
>> Regards, niXman
>>
>
> Here is GCC daily builds with default configuration:
>
> https://sourceforge.net/projects/osb/files/gcc/
>
> --
> Dongsheng

It seems that mingw-w64 daily builds stopped long ago.

I'm glad to upload my daily builds to mingw-w64, if someone intersting
and give me (dongsheng) permission.

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Fri, Apr 25, 2014 at 4:39 PM, niXman  wrote:
> Hi,
>
> Just now I uploaded the first builds of MinGW-W64 based on GCC-4.9.0.
>
> Links:
> 32-bit:
>  posix-sjlj:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/i686-4.9.0-release-posix-sjlj-rt_v3-rev0.7z
>  posix-dwarf:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/dwarf/i686-4.9.0-release-posix-dwarf-rt_v3-rev0.7z
>  win32-sjlj:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-win32/sjlj/i686-4.9.0-release-win32-sjlj-rt_v3-rev0.7z
>  win32-dwarf:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-win32/dwarf/i686-4.9.0-release-win32-dwarf-rt_v3-rev0.7z
>
> 64-bit:
>  posix-sjlj:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/x86_64-4.9.0-release-posix-sjlj-rt_v3-rev0.7z
>  posix-seh:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/seh/x86_64-4.9.0-release-posix-seh-rt_v3-rev0.7z
>  win32-sjlj:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-win32/sjlj/x86_64-4.9.0-release-win32-sjlj-rt_v3-rev0.7z
>  win32-seh:
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-win32/seh/x86_64-4.9.0-release-win32-seh-rt_v3-rev0.7z
>
>
>
> --
> Regards, niXman
>

Here is GCC daily builds with default configuration:

https://sourceforge.net/projects/osb/files/gcc/

--
Dongsheng

--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Jim Michaels]

building wxconfig causes crashes. also, with ./configure, I get:

 configure: error: C preprocessor "/mingw64h64t/bin/x86_64-w64-mingw32-cpp.exe" 
fails sanity check

https://sourceforge.net/p/mingw-w64/bugs/386/



From: niXman 
To: mingw-w64-public  
Sent: Monday, March 10, 2014 4:59 AM
Subject: [Mingw-w64-public] [Project News | New Builds]
 

>
>
>Hi,
>
>Just now I uploaded new builds based on GCC-4.8.2.
>
>  - MinGW-w64 updated to rev. 6511
>  - GDB updated to version 7.7
>
>
>Links:
>32-bit:
>    posix-sjlj: 
>i686-4.8.2-release-posix-sjlj-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.2/threads-posix/sjlj/i686-4.8.2-release-posix-sjlj-rt_v3-rev3.7z)
>    posix-dwarf: 
>i686-4.8.2-release-posix-dwarf-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.2/threads-posix/dwarf/i686-4.8.2-release-posix-dwarf-rt_v3-rev3.7z)
>    win32-sjlj: 
>i686-4.8.2-release-win32-sjlj-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.2/threads-win32/sjlj/i686-4.8.2-release-win32-sjlj-rt_v3-rev3.7z)
>    win32-dwarf: 
>i686-4.8.2-release-win32-dwarf-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.2/threads-win32/dwarf/i686-4.8.2-release-win32-dwarf-rt_v3-rev3.7z)
>
>64-bit:
>    posix-sjlj: 
>x86_64-4.8.2-release-posix-sjlj-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.2/threads-posix/sjlj/x86_64-4.8.2-release-posix-sjlj-rt_v3-rev3.7z)
>    posix-seh : 
>x86_64-4.8.2-release-posix-seh-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.2/threads-posix/seh/x86_64-4.8.2-release-posix-seh-rt_v3-rev3.7z)
>    win32-sjlj: 
>x86_64-4.8.2-release-win32-sjlj-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.2/threads-win32/sjlj/x86_64-4.8.2-release-win32-sjlj-rt_v3-rev3.7z)
>    win32-seh: 
>x86_64-4.8.2-release-win32-seh-rt_v3-rev3.7z(http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.2/threads-win32/seh/x86_64-4.8.2-release-win32-seh-rt_v3-rev3.7z)
>
>
>-- 
>Regards, niXman
>___
>Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
>http://sourceforge.net/projects/mingw-w64/
>___
>Another online IDE: http://liveworkspace.org/
>
>--
>Learn Graph Databases - Download FREE O'Reilly Book
>"Graph Databases" is the definitive new guide to graph databases and their
>applications. Written by three acclaimed leaders in the field,
>this first edition is now available. Download your free book today!
>http://p.sf.net/sfu/13534_NeoTech
>___
>Mingw-w64-public mailing list
>Mingw-w64-public@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
>--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Ray Donnelly]

Yes, that's what I was after, many thanks.

On Tue, Dec 10, 2013 at 1:43 PM, asmwarrior  wrote:
> On 2013-12-10 20:53, Ray Donnelly wrote:
>> Hi,
>>
>> Would it be possible to point me to these patches you've got? I'd like
>> to take a look.
>>
>> Ray.
> Hi, Ray, do you mean my local patches to GDB when I build it under Windows 
> 32bit?
>
> There are many, currently the most important ones, I think are those two:
> 1, https://sourceware.org/bugzilla/show_bug.cgi?id=15559
> The patch in comment 8 
> (https://sourceware.org/bugzilla/attachment.cgi?id=7227&action=diff)
> With this patch, I can let GDB to simulate a correct inferior call if the 
> inferior(debugee) is built from MinGW GCC version>7.0.
>
> 2,https://sourceware.org/bugzilla/show_bug.cgi?id=12127
> I have a patch to fix this crash issue (see comment 6).
> But I think I don't need this patch because it was fixed in GDB GIT HEAD 
> about two weeks ago(see comment 7).
> If you are still building GDB 7.6.2(release two days ago), I think you need 
> to packport the fix to GDB 7.6.2.
> The fix can be view in this link
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=38e1f2a7d503d8abd788456782287383e0a0cfe8
>
> All other patches are quite minor, such as
> * workaround performance issue 
> http://sourceware.org/bugzilla/show_bug.cgi?id=15412 (patch in comment 3)
> * Pierre Muller's patches to fix display of tabulation character for mingw 
> hosts, see https://sourceware.org/ml/gdb-patches/2013-11/msg00224.html
>
> Yuanhui Zhang
>
>
>
>
> --
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-12-10 20:53, Ray Donnelly wrote:
> Hi,
> 
> Would it be possible to point me to these patches you've got? I'd like
> to take a look.
> 
> Ray.
Hi, Ray, do you mean my local patches to GDB when I build it under Windows 
32bit?

There are many, currently the most important ones, I think are those two:
1, https://sourceware.org/bugzilla/show_bug.cgi?id=15559
The patch in comment 8 
(https://sourceware.org/bugzilla/attachment.cgi?id=7227&action=diff)
With this patch, I can let GDB to simulate a correct inferior call if the 
inferior(debugee) is built from MinGW GCC version>7.0.

2,https://sourceware.org/bugzilla/show_bug.cgi?id=12127
I have a patch to fix this crash issue (see comment 6).
But I think I don't need this patch because it was fixed in GDB GIT HEAD about 
two weeks ago(see comment 7).
If you are still building GDB 7.6.2(release two days ago), I think you need to 
packport the fix to GDB 7.6.2.
The fix can be view in this link 
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=38e1f2a7d503d8abd788456782287383e0a0cfe8

All other patches are quite minor, such as 
* workaround performance issue 
http://sourceware.org/bugzilla/show_bug.cgi?id=15412 (patch in comment 3)
* Pierre Muller's patches to fix display of tabulation character for mingw 
hosts, see https://sourceware.org/ml/gdb-patches/2013-11/msg00224.html

Yuanhui Zhang





--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Ray Donnelly]

Hi,

Would it be possible to point me to these patches you've got? I'd like
to take a look.

Ray.

On Tue, Dec 10, 2013 at 4:57 AM, asmwarrior  wrote:
> On 2013-12-10 12:46, Alexpux wrote:
>> We provide only static library for zlib and it named «libz.a». Try to search…
>>>
>>> So, I guess it was still removed from the tool-chain before the release?
>>>
>> No. It present.
>
> Oh, I found "libz.a" was there:
>
> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32\lib
>
> I'm sorry about my mistake!
>
> Yuanhui Zhang
>
> --
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-12-10 12:46, Alexpux wrote:
> We provide only static library for zlib and it named «libz.a». Try to search…
>>
>> So, I guess it was still removed from the tool-chain before the release?
>>
> No. It present.

Oh, I found "libz.a" was there:

i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32\lib

I'm sorry about my mistake!

Yuanhui Zhang

--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexpux]

10 дек. 2013 г., в 8:46, Alexpux  написал(а):

> 
> 10 дек. 2013 г., в 7:43, asmwarrior  написал(а):
> 
>> On 2013-12-10 11:19, Alexpux wrote:
>>> 
>>> 10 дек. 2013 г., в 7:11, asmwarrior  написал(а):
>>> 
 On 2013-12-10 10:34, Alexpux wrote:
 Question 2:
 I can't find the python header files.
>>> /opt/include/python2.7
>> 
>> Well, I don't see a folder named "include" under the "opt" folder, is 
>> this a package error?
> 
> This stuff is removed from toolchain.
 Thanks. 
 Well this be fixed in the feature release?
>>> yes.
>> 
>> Nice to hear.
>> 
>> 
>>> 
 The shipped GDB in MinGW-Builds is build with -static-libgcc options which 
 do not link to libgcc_s_dw2-1.dll (GDB default build options)
 But the shipped python27.dll was depend on libgcc_s_dw2-1.dll.
 I suggest that the python27.dll built with -static-libgcc too.
 
>>> Need to try.
>> 
>> Ok, hope it will be done in the next release, thanks.
>> 
>> 
>> BTW: Is it possible to include the expat and zlib library in 
>> MinGW-toolchain. If not, I need to build them before build GDB.
> 
> zlib is already in toolchain. Expat you need to build itself.
> 
 I search the "zlib" in MinGW-Build achieves, I get two match files:
 zlib.h under 
 i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32\include
>>> Yes. This is where it place. Also zlib static library libz.a in 
>>> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32/lib
>>> 
 zlib1.dll under \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\bin
 So, this is not enough to pass the configure test on zlib of GDB, I still 
 need to build zlib, and install the import library.
>>> Why not using zlib from 
>>> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32?
 
>> 
>> I would like to if the import zlib library exists, but as I have said 
>> before, there is no such library under:
>> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32/lib
> 
> We provide only static library for zlib and it named «libz.a». Try to search…
>> 
>> So, I guess it was still removed from the tool-chain before the release?
>> 
> No. It present.


For reference, I have many prebuilded packages for mingw-w64 builded with 
i686-gcc-4.8.2-posix-dwarf and x86_64-4.8.2-posix-seh toolchains here:

32-bit: https://sourceforge.net/projects/msys2/files/REPOS/MINGW/i686/

64-bit: https://sourceforge.net/projects/msys2/files/REPOS/MINGW/x86_64/


There are packages that can be extracted by hand or if you use my MSYS2 then it 
can be easily installed/uninstalled/upgraded via pacman package manager.

Regards,
Alexey.
> 
>> Thanks.
>> 
> Regards,
> Alexey.
>> 
>> 
>> 
>> 
>> 
>> --
>> Sponsored by Intel(R) XDK 
>> Develop, test and display web and hybrid apps with a single code base.
>> Download it for free now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>> ___
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexpux]

10 дек. 2013 г., в 7:43, asmwarrior  написал(а):

> On 2013-12-10 11:19, Alexpux wrote:
>> 
>> 10 дек. 2013 г., в 7:11, asmwarrior  написал(а):
>> 
>>> On 2013-12-10 10:34, Alexpux wrote:
>>> Question 2:
>>> I can't find the python header files.
>> /opt/include/python2.7
> 
> Well, I don't see a folder named "include" under the "opt" folder, is 
> this a package error?
 
 This stuff is removed from toolchain.
>>> Thanks. 
>>> Well this be fixed in the feature release?
>> yes.
> 
> Nice to hear.
> 
> 
>> 
>>> The shipped GDB in MinGW-Builds is build with -static-libgcc options which 
>>> do not link to libgcc_s_dw2-1.dll (GDB default build options)
>>> But the shipped python27.dll was depend on libgcc_s_dw2-1.dll.
>>> I suggest that the python27.dll built with -static-libgcc too.
>>> 
>> Need to try.
> 
> Ok, hope it will be done in the next release, thanks.
> 
> 
> BTW: Is it possible to include the expat and zlib library in 
> MinGW-toolchain. If not, I need to build them before build GDB.
 
 zlib is already in toolchain. Expat you need to build itself.
 
>>> I search the "zlib" in MinGW-Build achieves, I get two match files:
>>> zlib.h under 
>>> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32\include
>> Yes. This is where it place. Also zlib static library libz.a in 
>> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32/lib
>> 
>>> zlib1.dll under \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\bin
>>> So, this is not enough to pass the configure test on zlib of GDB, I still 
>>> need to build zlib, and install the import library.
>> Why not using zlib from 
>> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32?
>>> 
> 
> I would like to if the import zlib library exists, but as I have said before, 
> there is no such library under:
> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32/lib

We provide only static library for zlib and it named «libz.a». Try to search…
> 
> So, I guess it was still removed from the tool-chain before the release?
> 
No. It present.

> Thanks.
> 
Regards,
Alexey.
> 
> 
> 
> 
> 
> --
> Sponsored by Intel(R) XDK 
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-12-10 11:19, Alexpux wrote:
> 
> 10 дек. 2013 г., в 7:11, asmwarrior  написал(а):
> 
>> On 2013-12-10 10:34, Alexpux wrote:
>> Question 2:
>> I can't find the python header files.
> /opt/include/python2.7

 Well, I don't see a folder named "include" under the "opt" folder, is this 
 a package error?
>>>
>>> This stuff is removed from toolchain.
>> Thanks. 
>> Well this be fixed in the feature release?
> yes.

Nice to hear.


> 
>> The shipped GDB in MinGW-Builds is build with -static-libgcc options which 
>> do not link to libgcc_s_dw2-1.dll (GDB default build options)
>> But the shipped python27.dll was depend on libgcc_s_dw2-1.dll.
>> I suggest that the python27.dll built with -static-libgcc too.
>>
> Need to try.

Ok, hope it will be done in the next release, thanks.


 BTW: Is it possible to include the expat and zlib library in 
 MinGW-toolchain. If not, I need to build them before build GDB.
>>>
>>> zlib is already in toolchain. Expat you need to build itself.
>>>
>> I search the "zlib" in MinGW-Build achieves, I get two match files:
>> zlib.h under 
>> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32\include
> Yes. This is where it place. Also zlib static library libz.a in 
> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32/lib
> 
>> zlib1.dll under \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\bin
>> So, this is not enough to pass the configure test on zlib of GDB, I still 
>> need to build zlib, and install the import library.
> Why not using zlib from 
> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32?
>>

I would like to if the import zlib library exists, but as I have said before, 
there is no such library under:
i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32/lib

So, I guess it was still removed from the tool-chain before the release?

Thanks.






--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexpux]

10 дек. 2013 г., в 7:11, asmwarrior  написал(а):

> On 2013-12-10 10:34, Alexpux wrote:
> Question 2:
> I can't find the python header files.
 /opt/include/python2.7
>>> 
>>> Well, I don't see a folder named "include" under the "opt" folder, is this 
>>> a package error?
>> 
>> This stuff is removed from toolchain.
> Thanks. 
> Well this be fixed in the feature release?
yes.

> The shipped GDB in MinGW-Builds is build with -static-libgcc options which do 
> not link to libgcc_s_dw2-1.dll (GDB default build options)
> But the shipped python27.dll was depend on libgcc_s_dw2-1.dll.
> I suggest that the python27.dll built with -static-libgcc too.
> 
Need to try.
>>> 
>>> BTW: Is it possible to include the expat and zlib library in 
>>> MinGW-toolchain. If not, I need to build them before build GDB.
>> 
>> zlib is already in toolchain. Expat you need to build itself.
>> 
> I search the "zlib" in MinGW-Build achieves, I get two match files:
> zlib.h under 
> i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32\include
Yes. This is where it place. Also zlib static library libz.a in 
i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32/lib

> zlib1.dll under \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\bin
> So, this is not enough to pass the configure test on zlib of GDB, I still 
> need to build zlib, and install the import library.
Why not using zlib from 
i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32?
> 
> 
> Thanks.
> 
> 
> 
> --
> Sponsored by Intel(R) XDK 
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-12-10 10:34, Alexpux wrote:
 Question 2:
 I can't find the python header files.
>>> /opt/include/python2.7
>>
>> Well, I don't see a folder named "include" under the "opt" folder, is this a 
>> package error?
> 
> This stuff is removed from toolchain.
Thanks. 
Well this be fixed in the feature release?
The shipped GDB in MinGW-Builds is build with -static-libgcc options which do 
not link to libgcc_s_dw2-1.dll (GDB default build options)
But the shipped python27.dll was depend on libgcc_s_dw2-1.dll.
I suggest that the python27.dll built with -static-libgcc too.

>>
>> BTW: Is it possible to include the expat and zlib library in 
>> MinGW-toolchain. If not, I need to build them before build GDB.
> 
> zlib is already in toolchain. Expat you need to build itself.
> 
I search the "zlib" in MinGW-Build achieves, I get two match files:
zlib.h under 
i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\i686-w64-mingw32\include
zlib1.dll under \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\bin
So, this is not enough to pass the configure test on zlib of GDB, I still need 
to build zlib, and install the import library.

Thanks.



--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexpux]

10 дек. 2013 г., в 5:01, asmwarrior  написал(а):

> On 2013-12-9 23:01, Alexpux wrote:
>> 
>> 09 дек. 2013 г., в 18:48, asmwarrior 
>> > > написал(а):
>> 
>>> 
>>> Hi, thanks for your work.
>>> I just download this one: i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z
>>> 
>>> I would like to use this GCC toolchain to build GDB with Python support.
>> 
>> Our toolchain has GDB builded with Python support.
> 
> Thanks for the reply, but I just want to build GDB myself, because I have 
> several local GDB patches (against GDB git head) to workaround some GDB issue 
> under Windows.
> 
>>> 
>>> I was using the official Python Windows installer, and build GDB against 
>>> the official Python dll, since the official Python was build with MSVC, and 
>>> link against msvcr90.dll. The result GDB will have both link to msvcrt.dll 
>>> and msvcr90.dll(indirectly through python27.dll), this may cause some 
>>> potential problems since they have different c-run-time libraries.
>>> 
>>> Now, I would try to link against the Python import library shipped with the 
>>> MinGW-Build i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z.
>>> 
>>> Question 1:
>>> I found that there are two .a files: libpython2.7.a and libpython2.7.dll.a, 
>>> both under: 
>>> \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\lib\python2.7\config 
>>> folder.
>>> So, which should I use?
>>> 
>> dll.a
> 
> OK.
> 
>> 
>>> Question 2:
>>> I can't find the python header files.
>> /opt/include/python2.7
> 
> Well, I don't see a folder named "include" under the "opt" folder, is this a 
> package error?

This stuff is removed from toolchain. 
> 
>>> 
>>> Question 3:
>>> When build GDB against official python installation, I just add some option 
>>> to GDB toplevel configure like:
>>> --with-python=/python/python
>>> Where under MSYS, I have a mount that 
>>> E:\code\python27/python
>>> (More details on how to build GDB can be found my own wiki page [1])
>>> Note that E:\code\python27 is the folder I install the official python 
>>> 2.7.x, so if I would like to link to the shipped python, what is the 
>>> correct configure option?
>>> 
>> https://github.com/Alexpux/mingw-builds/blob/develop/scripts/gdb.sh#L55-L78
>> 
>> To link with our Python you MUST add «-D__USE_MINGW_ANSI_STDIO=1» to CFLAGS 
>> and CXXFLAGS
> 
> Thanks, I see, the related option is: 
> --with-python=$PREFIX/opt/bin/python-config.sh
> 
>>> Question 4:
>>> What does 
>>> https://github.com/niXman/mingw-builds/blob/master/sources/gdb-wrapper/gdb-wrapper.c
>>>  used for? I vaguely remember you have some script code to rename the 
>>> GDB.exe to some other name, and renamed gdb-wrapper.exe to GDB.exe. It does 
>>> some PYTHONPATH related changes, but refer to Ruben's post here [2], it is 
>>> quite safe to put the python27.dll along side the gdb.exe and put all the 
>>> python script files under bin folder too.
>> 
>> This is wrapper to start GDB with Python from opt subfolder.
> OK, I see.
> 
> BTW: Is it possible to include the expat and zlib library in MinGW-toolchain. 
> If not, I need to build them before build GDB.

zlib is already in toolchain. Expat you need to build itself.

> 
> Thanks.
> 
> 
> 
> 
> 
> --
> Sponsored by Intel(R) XDK 
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public


--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-12-9 23:01, Alexpux wrote:
> 
> 09 дек. 2013 г., в 18:48, asmwarrior 
>  > написал(а):
>  
>>
>> Hi, thanks for your work.
>> I just download this one: i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z
>>
>> I would like to use this GCC toolchain to build GDB with Python support.
> 
> Our toolchain has GDB builded with Python support.

Thanks for the reply, but I just want to build GDB myself, because I have 
several local GDB patches (against GDB git head) to workaround some GDB issue 
under Windows.

>>
>> I was using the official Python Windows installer, and build GDB against the 
>> official Python dll, since the official Python was build with MSVC, and link 
>> against msvcr90.dll. The result GDB will have both link to msvcrt.dll and 
>> msvcr90.dll(indirectly through python27.dll), this may cause some potential 
>> problems since they have different c-run-time libraries.
>>
>> Now, I would try to link against the Python import library shipped with the 
>> MinGW-Build i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z.
>>
>> Question 1:
>> I found that there are two .a files: libpython2.7.a and libpython2.7.dll.a, 
>> both under: 
>> \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\lib\python2.7\config 
>> folder.
>> So, which should I use?
>>
> dll.a

OK.

> 
>> Question 2:
>> I can't find the python header files.
> /opt/include/python2.7

Well, I don't see a folder named "include" under the "opt" folder, is this a 
package error?

>>
>> Question 3:
>> When build GDB against official python installation, I just add some option 
>> to GDB toplevel configure like:
>> --with-python=/python/python
>> Where under MSYS, I have a mount that 
>> E:\code\python27/python
>> (More details on how to build GDB can be found my own wiki page [1])
>> Note that E:\code\python27 is the folder I install the official python 
>> 2.7.x, so if I would like to link to the shipped python, what is the correct 
>> configure option?
>>
> https://github.com/Alexpux/mingw-builds/blob/develop/scripts/gdb.sh#L55-L78
> 
> To link with our Python you MUST add «-D__USE_MINGW_ANSI_STDIO=1» to CFLAGS 
> and CXXFLAGS

Thanks, I see, the related option is: 
--with-python=$PREFIX/opt/bin/python-config.sh

>> Question 4:
>> What does 
>> https://github.com/niXman/mingw-builds/blob/master/sources/gdb-wrapper/gdb-wrapper.c
>>  used for? I vaguely remember you have some script code to rename the 
>> GDB.exe to some other name, and renamed gdb-wrapper.exe to GDB.exe. It does 
>> some PYTHONPATH related changes, but refer to Ruben's post here [2], it is 
>> quite safe to put the python27.dll along side the gdb.exe and put all the 
>> python script files under bin folder too.
> 
> This is wrapper to start GDB with Python from opt subfolder.
OK, I see.

BTW: Is it possible to include the expat and zlib library in MinGW-toolchain. 
If not, I need to build them before build GDB.

Thanks.






--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexpux]

09 дек. 2013 г., в 18:48, asmwarrior  написал(а):

> On 2013-12-6 16:42, niXman wrote:
>> Hi guys!
>> 
>> I'm pleased to announce the new builds of MinGW-W64 based on the 
>> GCC-4.8.2 at rev.1.
>> Changes from rev.0 is:
>>  - Binutils updated to 2.24
>>  - MinGW-w64 v3 rev.6391
>>  - Backport MinGW-w64 runtime commits from trunk to stable version:
>>  6303: Fixed conflicts with xmmintrin.h.
>>  6332: Install libvfw32.a once again
>>  6385: Update shlwapi.def for Win7 32-bit
>>  6386: Update shlwapi.def for Win7 64-bit
>>  6390: Update shell32.def from Win7
>>  - Update make to latest from git.
>>  - Fix installing gcc libraries for Python
>>  - Relocate c++ headers to /include/c++
>> 
>> Links:  
> 
> Hi, thanks for your work.
> I just download this one: i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z
> 
> I would like to use this GCC toolchain to build GDB with Python support.

Our toolchain has GDB builded with Python support.
> 
> I was using the official Python Windows installer, and build GDB against the 
> official Python dll, since the official Python was build with MSVC, and link 
> against msvcr90.dll. The result GDB will have both link to msvcrt.dll and 
> msvcr90.dll(indirectly through python27.dll), this may cause some potential 
> problems since they have different c-run-time libraries.
> 
> Now, I would try to link against the Python import library shipped with the 
> MinGW-Build i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z.
> 
> Question 1:
> I found that there are two .a files: libpython2.7.a and libpython2.7.dll.a, 
> both under: 
> \i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\lib\python2.7\config 
> folder.
> So, which should I use?
> 
dll.a

> Question 2:
> I can't find the python header files.
/opt/include/python2.7
> 
> Question 3:
> When build GDB against official python installation, I just add some option 
> to GDB toplevel configure like:
> --with-python=/python/python
> Where under MSYS, I have a mount that 
> E:\code\python27/python
> (More details on how to build GDB can be found my own wiki page [1])
> Note that E:\code\python27 is the folder I install the official python 2.7.x, 
> so if I would like to link to the shipped python, what is the correct 
> configure option?
> 
https://github.com/Alexpux/mingw-builds/blob/develop/scripts/gdb.sh#L55-L78

To link with our Python you MUST add «-D__USE_MINGW_ANSI_STDIO=1» to CFLAGS and 
CXXFLAGS

> Question 4:
> What does 
> https://github.com/niXman/mingw-builds/blob/master/sources/gdb-wrapper/gdb-wrapper.c
>  used for? I vaguely remember you have some script code to rename the GDB.exe 
> to some other name, and renamed gdb-wrapper.exe to GDB.exe. It does some 
> PYTHONPATH related changes, but refer to Ruben's post here [2], it is quite 
> safe to put the python27.dll along side the gdb.exe and put all the python 
> script files under bin folder too.

This is wrapper to start GDB with Python from opt subfolder.
> 
> Thanks.
> Yuanhui Zhang
> 
> 
> 
> [1] https://sourceforge.net/p/gdbmingw/wiki/Build%20GDB%20under%20MSYS/
> [2] https://groups.google.com/d/msg/comp.lang.python/-DE5LmBbAC0/xv6q059ez-oJ
> 
> 
> 
> --
> Sponsored by Intel(R) XDK 
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-12-6 16:42, niXman wrote:
> Hi guys!
> 
> I'm pleased to announce the new builds of MinGW-W64 based on the 
> GCC-4.8.2 at rev.1.
> Changes from rev.0 is:
>   - Binutils updated to 2.24
>   - MinGW-w64 v3 rev.6391
>   - Backport MinGW-w64 runtime commits from trunk to stable version:
>   6303: Fixed conflicts with xmmintrin.h.
>   6332: Install libvfw32.a once again
>   6385: Update shlwapi.def for Win7 32-bit
>   6386: Update shlwapi.def for Win7 64-bit
>   6390: Update shell32.def from Win7
>   - Update make to latest from git.
>   - Fix installing gcc libraries for Python
>   - Relocate c++ headers to /include/c++
> 

Another issue is that 32 bit GDB can't handle a inferior call of a non-static 
member function, so even a simple "p v[0]" command will fail if v is a 
std::vector.
See this bug: GDB Bug 15559–Method call and calling convention 
https://sourceware.org/bugzilla/show_bug.cgi?id=15559
I have a nasty patch to handle/workaround this there(in the comment 8 of the 
above Bug report), hope it wil be helpful.

Yuanhui Zhang


--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-12-6 16:42, niXman wrote:
> Hi guys!
> 
> I'm pleased to announce the new builds of MinGW-W64 based on the 
> GCC-4.8.2 at rev.1.
> Changes from rev.0 is:
>   - Binutils updated to 2.24
>   - MinGW-w64 v3 rev.6391
>   - Backport MinGW-w64 runtime commits from trunk to stable version:
>   6303: Fixed conflicts with xmmintrin.h.
>   6332: Install libvfw32.a once again
>   6385: Update shlwapi.def for Win7 32-bit
>   6386: Update shlwapi.def for Win7 64-bit
>   6390: Update shell32.def from Win7
>   - Update make to latest from git.
>   - Fix installing gcc libraries for Python
>   - Relocate c++ headers to /include/c++
> 
> Links:  

Hi, thanks for your work.
I just download this one: i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z

I would like to use this GCC toolchain to build GDB with Python support.
 
I was using the official Python Windows installer, and build GDB against the 
official Python dll, since the official Python was build with MSVC, and link 
against msvcr90.dll. The result GDB will have both link to msvcrt.dll and 
msvcr90.dll(indirectly through python27.dll), this may cause some potential 
problems since they have different c-run-time libraries.

Now, I would try to link against the Python import library shipped with the 
MinGW-Build i686-4.8.2-release-posix-dwarf-rt_v3-rev1.7z.

Question 1:
I found that there are two .a files: libpython2.7.a and libpython2.7.dll.a, 
both under: 
\i686-4.8.2-release-posix-dwarf-rt_v3-rev1\mingw32\opt\lib\python2.7\config 
folder.
So, which should I use?

Question 2:
I can't find the python header files.

Question 3:
When build GDB against official python installation, I just add some option to 
GDB toplevel configure like:
--with-python=/python/python
Where under MSYS, I have a mount that 
E:\code\python27/python
(More details on how to build GDB can be found my own wiki page [1])
Note that E:\code\python27 is the folder I install the official python 2.7.x, 
so if I would like to link to the shipped python, what is the correct configure 
option?

Question 4:
What does 
https://github.com/niXman/mingw-builds/blob/master/sources/gdb-wrapper/gdb-wrapper.c
 used for? I vaguely remember you have some script code to rename the GDB.exe 
to some other name, and renamed gdb-wrapper.exe to GDB.exe. It does some 
PYTHONPATH related changes, but refer to Ruben's post here [2], it is quite 
safe to put the python27.dll along side the gdb.exe and put all the python 
script files under bin folder too.

Thanks.
Yuanhui Zhang
 


[1] https://sourceforge.net/p/gdbmingw/wiki/Build%20GDB%20under%20MSYS/
[2] https://groups.google.com/d/msg/comp.lang.python/-DE5LmBbAC0/xv6q059ez-oJ



--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexey Pavlov]

2013/10/19 Alexey Pavlov :
> ANNOUNCING first  GCC-4.8.2 builds with latest stable mingw-w64 runtime v3.
>
> Program versions in builds:
>
> GCC-4.8.2.
> binutils-2.23.2.
> mingw-w64 runtime rev.6346.
> gdb-7.6.1.
> python-2.7.5.
> GNU Make 4.0 from git.
>
> GCC-4.8.2 builded with bootstrap and next languages support:
> c,c++,ada,fortran,objc,obj-c++.
>
> Links:
>
> 32-bit:
>   posix-sjlj:i686-4.8.2-release-posix-sjlj-rt_v3-rev0.7z
>   posix-dwarf:i686-4.8.2-release-posix-dwarf-rt_v3-rev0.7z
>   win32-sjlj:i686-4.8.2-release-win32-sjlj-rt_v3-rev0.7z
>   win32-dwarf:i686-4.8.2-release-win32-dwarf-rt_v3-rev0.7z
>
> 64-bit:
>   posix-sjlj:x86_64-4.8.2-release-posix-sjlj-rt_v3-rev0.7z
>   posix-seh :  x86_64-4.8.2-release-posix-seh-rt_v3-rev0.7z
>   win32-sjlj:x86_64-4.8.2-release-win32-sjlj-rt_v3-rev0.7z
>   win32-seh:   x86_64-4.8.2-release-win32-seh-rt_v3-rev0.7z
>
>
> Toolchains sources: src-4.8.2-release-rt_v3-rev0.tar.7z
>
> Build scripts: https://github.com/niXman/mingw-builds
>

Today I repack GCC-4.8.2-rev0 toolchains with fixed mingw32-make.
All archives are reloaded now.

>
> Regards,
> Alexey.
>

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

asmwarrior 2013-10-20 19:22:
> Please write a note in the site:
> http://sourceforge.net/projects/mingwbuilds/, saying something like:
> the mingw-builds site is not updated any more, the new builds will be
> hold in mingw-w64 site...
> So new users can quickly find the newest builds in
> http://sourceforge.net/projects/mingw-w64

Done, in description.


-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-10-20 17:46, niXman wrote:
> Hi,
> 
>> > So, in the feature, all the mingw-builds packages will be hold in
>> > http://sourceforge.net/projects/mingw-w64/files instead of
>> > mingw-builds site?
> Yes.
> 
>> > Or is this an alternative mingw-builds release?
> Read please:
> https://sourceforge.net/mailarchive/message.php?msg_id=31436507
> https://sourceforge.net/mailarchive/message.php?msg_id=31538921
> 
> 
> -- Regards, niXman
Hi, thanks for the reply.

Please write a note in the site: http://sourceforge.net/projects/mingwbuilds/, 
saying something like:
the mingw-builds site is not updated any more, the new builds will be hold in 
mingw-w64 site...
So new users can quickly find the newest builds in 
http://sourceforge.net/projects/mingw-w64 

Thanks.
Yuanhui Zhang

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[niXman]

Hi,

> So, in the feature, all the mingw-builds packages will be hold in
> http://sourceforge.net/projects/mingw-w64/files instead of
> mingw-builds site?
Yes.

> Or is this an alternative mingw-builds release?
Read please:
https://sourceforge.net/mailarchive/message.php?msg_id=31436507
https://sourceforge.net/mailarchive/message.php?msg_id=31538921


-- 
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64/
___
Another online IDE: http://liveworkspace.org/

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[asmwarrior]

On 2013-10-20 3:29, Alexey Pavlov wrote:
> *ANNOUNCING* first  GCC-4.8.2 builds with latest stable mingw-w64 runtime v3.
> 
> Program *versions* in builds:
> 
>  1. /GCC-4.8.2.
> /
>  2. /binutils-2.23.2.
> /
>  3. /mingw-w64 runtime rev.6346.
> /
>  4. /gdb-7.6.1.
> /
>  5. /python-2.7.5./
>  6. /GNU Make 4.0 from git./
> 
> *GCC-4.8.2 *builded with bootstrap and next languages support: 
> c,c++,ada,fortran,objc,obj-c++.
> 
> *Links:*
> 
> *32-bit:*
>   posix-sjlj:i686-4.8.2-release-posix-sjlj-rt_v3-rev0.7z 
> 
>   posix-dwarf:i686-4.8.2-release-posix-dwarf-rt_v3-rev0.7z 
> 
>   win32-sjlj:i686-4.8.2-release-win32-sjlj-rt_v3-rev0.7z 
> 
>   win32-dwarf:i686-4.8.2-release-win32-dwarf-rt_v3-rev0.7z 
> 
> 
> *64-bit:*
>   posix-sjlj:x86_64-4.8.2-release-posix-sjlj-rt_v3-rev0.7z 
> 
>   posix-seh :  x86_64-4.8.2-release-posix-seh-rt_v3-rev0.7z 
> 
>   win32-sjlj:x86_64-4.8.2-release-win32-sjlj-rt_v3-rev0.7z 
> 
>   win32-seh:   x86_64-4.8.2-release-win32-seh-rt_v3-rev0.7z 
> 
> 
> 
> *Toolchains sources:* src-4.8.2-release-rt_v3-rev0.tar.7z 
> 
> 
> *Build scripts:* https://github.com/niXman/mingw-builds
> 
> 
> Regards,
> Alexey.
> 
Hi, Thanks. 

So, in the feature, all the mingw-builds packages will be hold in 
http://sourceforge.net/projects/mingw-w64/files instead of mingw-builds site?
Or is this an alternative mingw-builds release?

Yuanhui Zhang




--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexey Pavlov]

*ANNOUNCING* new GCC-4.8.1 builds with latest stable mingw-w64 runtime v3.

GCC-4.8.1 has been rebuild with rev2.

Program *versions* in builds:

   1. *GCC-4.8.1.
   *
   2. *binutils-2.23.2.
   *
   3. *mingw-w64 runtime rev.6311.
   *
   4. *gdb-7.6.1.
   *
   5. *python-2.7.5.*
   6. *GNU Make from git.*

*Changes* since rev1:

   - update mingw-w64 runtime to v3 rev.6311.
   - update GNU Make to 3.99.92


*Links:*

*32-bit:*
  posix-sjlj:
i686-4.8.1-release-posix-sjlj-rt_v3-rev2.7z
  posix-dwarf:
i686-4.8.1-release-posix-dwarf-rt_v3-rev2.7z
  win32-sjlj:
i686-4.8.1-release-win32-sjlj-rt_v3-rev2.7z
  win32-dwarf:
i686-4.8.1-release-win32-dwarf-rt_v3-rev2.7z

*64-bit:*
  posix-sjlj:
x86_64-4.8.1-release-posix-sjlj-rt_v3-rev2.7z
  posix-seh :
x86_64-4.8.1-release-posix-seh-rt_v3-rev2.7z
  win32-sjlj:
x86_64-4.8.1-release-win32-sjlj-rt_v3-rev2.7z
  win32-seh:
x86_64-4.8.1-release-win32-seh-rt_v3-rev2.7z
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Derek Buitenhuis]

On 9/19/2013 4:26 AM, Alexey Pavlov wrote:
> /GNU Make from git./

Particularly happy about this bit. It fixes a long standing bug with CRLF
line endings.

- Derek

--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Alexey Pavlov]

2013/9/19 Dongsheng Song 

> On Thu, Sep 19, 2013 at 11:26 AM, Alexey Pavlov  wrote:
>
>> *ANNOUNCING* new GCC-4.8.1 builds before mingw-w64 runtime v3 are
>> released.
>>
>> GCC-4.8.1 has been rebuild with rev1.
>>
>> Program *versions* in builds:
>>
>>1. *GCC-4.8.1.
>>*
>>2. *binutils-2.23.2.
>>*
>>3. *
>>
>>mingw-w64 runtime rev. 6288.
>>*
>>4. *gdb-7.6.1.
>>*
>>5. *python-2.7.5.*
>>6. *GNU Make from git.*
>>
>> *Changes* since rev0:
>>
>>- update mingw32-make to rev.6288.
>>
>>
> Typo, should be 
>
> 'mingw-w64 runtime rev. 6288.' ?
> 
> 
>
Yeah! This is my copy/paste mistake :)

>
>>- update GNU Make to 3.99.91
>>
>>
>> *Links:*
>>
>> *32-bit:*
>>   posix-sjlj:
>> i686-4.8.1-release-posix-sjlj-rev1.7z
>>   posix-dwarf:
>> i686-4.8.1-release-posix-dwarf-rev1.7z
>>   win32-sjlj:
>> i686-4.8.1-release-win32-sjlj-rev1.7z
>>   win32-dwarf:
>> i686-4.8.1-release-win32-dwarf-rev1.7z
>>
>> *64-bit:*
>>   posix-sjlj:
>> x86_64-4.8.1-release-posix-sjlj-rev1.7z
>>   posix-seh :  
>> x86_64-4.8.1-release-posix-seh-rev1.7z
>>   win32-sjlj:
>> x86_64-4.8.1-release-win32-sjlj-rev1.7z
>>   win32-seh:   
>> x86_64-4.8.1-release-win32-seh-rev1.7z
>>
>>
>> --
>> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
>> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
>> SharePoint
>> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
>> includes
>> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>> ___
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>
>>
>
>
> --
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
> SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
> includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] [Project News | New Builds]

[Dongsheng Song]

On Thu, Sep 19, 2013 at 11:26 AM, Alexey Pavlov  wrote:

> *ANNOUNCING* new GCC-4.8.1 builds before mingw-w64 runtime v3 are
> released.
>
> GCC-4.8.1 has been rebuild with rev1.
>
> Program *versions* in builds:
>
>1. *GCC-4.8.1.
>*
>2. *binutils-2.23.2.
>*
>3. *
>​​
>mingw-w64 runtime rev. 6288.
>*
>4. *gdb-7.6.1.
>*
>5. *python-2.7.5.*
>6. *GNU Make from git.*
>
> *Changes* since rev0:
>
>- update mingw32-make to rev.6288.
>
>
​Typo, should be ​

​'mingw-w64 runtime rev. 6288.​' ?
​
​

>
>- update GNU Make to 3.99.91
>
>
> *Links:*
>
> *32-bit:*
>   posix-sjlj:
> i686-4.8.1-release-posix-sjlj-rev1.7z
>   posix-dwarf:
> i686-4.8.1-release-posix-dwarf-rev1.7z
>   win32-sjlj:
> i686-4.8.1-release-win32-sjlj-rev1.7z
>   win32-dwarf:
> i686-4.8.1-release-win32-dwarf-rev1.7z
>
> *64-bit:*
>   posix-sjlj:
> x86_64-4.8.1-release-posix-sjlj-rev1.7z
>   posix-seh :  
> x86_64-4.8.1-release-posix-seh-rev1.7z
>   win32-sjlj:
> x86_64-4.8.1-release-win32-sjlj-rev1.7z
>   win32-seh:   
> x86_64-4.8.1-release-win32-seh-rev1.7z
>
>
> --
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
> SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
> includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public