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] winpthreads kill

[Alexpux]

09 дек. 2013 г., в 23:42, Victor Bombi  написал(а):

> ok. I have got msys and I need to build a debug version of winpthreads for 
> debugging a program that is hanging on exit (only the windows version)
> I do ./configure --help but I cant understand how to build a debug version.
> Any hints?

You can see how we build it for our toolchain
https://github.com/Alexpux/mingw-builds/blob/develop/scripts/winpthreads.sh#L54-L65

To build debug version you can guid with CFLAGS="-O0 -g»

Regards,
Alexey.
> 
> victor
> 
> - Original Message - 
> From: "Victor Bombi" 
> To: 
> Sent: Thursday, November 28, 2013 3:04 PM
> Subject: Re: [Mingw-w64-public] winpthreads kill
> 
> 
>> I dont know how to build. I always use CMake to create makefiles without
>> mysys.
>> Do I need mysys? where do I get configure?
>> 
>> - Original Message - 
>> From: "JonY" 
>> To: 
>> Sent: Wednesday, November 27, 2013 11:10 PM
>> Subject: Re: [Mingw-w64-public] winpthreads kill
>> 
>> 
>>> --
>>> Rapidly troubleshoot problems before they affect your business. Most IT
>>> organizations don't have a clear picture of how application performance
>>> affects their revenue. With AppDynamics, you get 100% visibility into 
>>> your
>>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
>>> Pro!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
>> 
>> 
>> 
>> 
>> 
>>> ___
>>> Mingw-w64-public mailing list
>>> Mingw-w64-public@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>> 
>> 
>> 
>> --
>> Rapidly troubleshoot problems before they affect your business. Most IT
>> organizations don't have a clear picture of how application performance
>> affects their revenue. With AppDynamics, you get 100% visibility into your
>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics 
>> Pro!
>> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&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


--
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] winpthreads kill

[Victor Bombi]

ok. I have got msys and I need to build a debug version of winpthreads for 
debugging a program that is hanging on exit (only the windows version)
I do ./configure --help but I cant understand how to build a debug version.
Any hints?

victor

- Original Message - 
From: "Victor Bombi" 
To: 
Sent: Thursday, November 28, 2013 3:04 PM
Subject: Re: [Mingw-w64-public] winpthreads kill


>I dont know how to build. I always use CMake to create makefiles without
> mysys.
> Do I need mysys? where do I get configure?
>
> - Original Message - 
> From: "JonY" 
> To: 
> Sent: Wednesday, November 27, 2013 11:10 PM
> Subject: Re: [Mingw-w64-public] winpthreads kill
>
>
>> --
>> Rapidly troubleshoot problems before they affect your business. Most IT
>> organizations don't have a clear picture of how application performance
>> affects their revenue. With AppDynamics, you get 100% visibility into 
>> your
>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
>> Pro!
>> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
>
>
> 
>
>
>> ___
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>
>
>
> --
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics 
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&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] configure options

[Ruben Van Boxem]

2013/12/9 

>
>
> I tried to configure ffmpeg-2.1.1 simple with
>
>   $  $ lv configure
>  ...src/ffmpeg/ffmpeg-2.1.1 $ ./configure --host=i686-w64-mingw32
>  Unknown option "--host=i686-w64-mingw32".
>  See ./configure --help for available options.
>
> In the configure file it shows these options:
>   --host-cc=HOSTCC use host C compiler HOSTCC
>   --host-cflags=HCFLAGSuse HCFLAGS when compiling for host
>   --host-cppflags=HCPPFLAGS use HCPPFLAGS when compiling for host
>   --host-ld=HOSTLD use host linker HOSTLD
>   --host-ldflags=HLDFLAGS  use HLDFLAGS when linking for host
>   --host-libs=HLIBSuse libs HLIBS when linking for host
>   --host-os=OS compiler host OS [$target_os]
>
>
> The first one looks to be th same so I tried it and it works or appears to.
>   $ ./configure --host-cc=i686-w64-mingw32
>
> This is the first time I ran into the --host= not working, but I'd like to
> hear if anyone else has seen this an if --host-cc=...  an only it the right
> choice, because the option
>
> --host-ld=HOSTLD use host linker HOSTLD
>
> also looks important. But, I only want to set the minimum if possible.
>
>
> I know that ffmpeg binaries are already available, but I want to build it,
> so the developement files will be available.
>

People have done the job for you, there's a popular build script. Maybe
that can help you:
http://ffmpeg.zeranoe.com/blog/?p=242
See also:
http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=5&t=1681#p5993
which contains the configure options one user used.
It looks like
--enable-memalign-hack --arch=x86 --target-os=mingw32
--cross-prefix=i686-w64-mingw32-
works for 32-bit. I'm not sure what should be used for 64-bit.

Ruben


>
> 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

[Mingw-w64-public] configure options

[wynfield]

I tried to configure ffmpeg-2.1.1 simple with

  $  $ lv configure
 ...src/ffmpeg/ffmpeg-2.1.1 $ ./configure --host=i686-w64-mingw32
 Unknown option "--host=i686-w64-mingw32".
 See ./configure --help for available options.

In the configure file it shows these options:
  --host-cc=HOSTCC use host C compiler HOSTCC
  --host-cflags=HCFLAGSuse HCFLAGS when compiling for host
  --host-cppflags=HCPPFLAGS use HCPPFLAGS when compiling for host
  --host-ld=HOSTLD use host linker HOSTLD
  --host-ldflags=HLDFLAGS  use HLDFLAGS when linking for host
  --host-libs=HLIBSuse libs HLIBS when linking for host
  --host-os=OS compiler host OS [$target_os]


The first one looks to be th same so I tried it and it works or appears to.
  $ ./configure --host-cc=i686-w64-mingw32

This is the first time I ran into the --host= not working, but I'd like to hear 
if anyone else has seen this an if --host-cc=...  an only it the right choice, 
because the option

--host-ld=HOSTLD use host linker HOSTLD

also looks important. But, I only want to set the minimum if possible.


I know that ffmpeg binaries are already available, but I want to build it, so 
the developement files will be available.

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] quadmath.h's expq() crashes at runtime.

[JonY]

On 10/6/2013 21:00, JonY wrote:
> 
> Confirmed:
> 
> Program received signal SIGSEGV, Segmentation fault.
> fesetenv (envp=envp@entry=0x28fe40) at ../misc/fesetenv.c:59
> 59  __asm__ volatile ("ldmxcsr %0" : : "m" (_mxcsr));
> (gdb) list
> 54env.__unused1 = 0x;
> 55__asm__ volatile ("fldenv %0" : : "m" (env)
> 56  : "st", "st(1)", "st(2)", "st(3)", "st(4)",
> 57  "st(5)", "st(6)", "st(7)");
> 58if (__mingw_has_sse ())
> 59  __asm__ volatile ("ldmxcsr %0" : : "m" (_mxcsr));
> 60  }
> 61
> 62return 0;
> 63  }
> (gdb) p _mxcsr
> $1 = -1
> 

Kai, ping.





signature.asc
Description: OpenPGP digital signature
--
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