Re: [Mingw-w64-public] win-builds config options
On Wed, Jan 08, 2014, wynfi...@gmail.com wrote: I brought up a MS CMD console and ran the followingm, which I think is what you meant by the corresponding exe files. C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\fc-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\pango-querymodules.exe C:\cygwin\opt\windows_32\etc\pango\pango.modules C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\gdk-pixbuf-query-loaders --update-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\gdk-query-immodules-2.0 --update-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\gtk-query-immodules-2.0 --update-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundle --- Since no error messages were displayed I assume that these ran o.k., but they ran very fast, so I can't guarantee successfull completion. Does Microsoft Windows have a return code code variable, like we do in the Unix world -- $? ? If the above were successfull, then I'd say that the problem was most likely a cygwin environment conflict. How does it look to you? Thanks for the test. You can easily test that these commands succeed by running gtk-demo and elementary-config (or elementary-test). Without these commands, gtk-demo is unable to display any character and will instead show squares. As for elementary-config, it would take a longer time to start (that one might be difficult to assess since on windows XP, it's actually fast and you can't compare before/after). Another thing you can do is run these: fc-cache -v pango-querymodules gdk-pixbuf-query-loaders gtk-query-immodules If you get output on screen, you're good: the --update-cache argument is mostly equivalent to redirecting their output to a given file. Without it, you will get the output on stdout. -- Adrien Nader -- 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=84349831iu=/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] win-builds config options
Adrien Nader adr...@notk.org wrote: On Wed, Jan 08, 2014, wynfi...@gmail.com wrote: I brought up a MS CMD console and ran the followingm, which I think is what you meant by the corresponding exe files. C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\fc-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\pango-querymodules.exe C:\cygwin\opt\windows_32\etc\pango\pango.modules C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\gdk-pixbuf-query-loaders --update-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\gdk-query-immodules-2.0 --update-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundleC:\cygwin\opt\windows_32\bin\gtk-query-immodules-2.0 --update-cache C:\win-apps\yypkg\win-builds-bundle\win-builds-bundle --- Since no error messages were displayed I assume that these ran o.k., but they ran very fast, so I can't guarantee successfull completion. Does Microsoft Windows have a return code code variable, like we do in the Unix world -- $? ? If the above were successfull, then I'd say that the problem was most likely a cygwin environment conflict. How does it look to you? Thanks for the test. You can easily test that these commands succeed by running gtk-demo and elementary-config (or elementary-test). Without these commands, gtk-demo is unable to display any character and will instead show squares. As for elementary-config, it would take a longer time to start (that one might be difficult to assess since on windows XP, it's actually fast and you can't compare before/after). Another thing you can do is run these: fc-cache -v pango-querymodules gdk-pixbuf-query-loaders gtk-query-immodules If you get output on screen, you're good: the --update-cache argument is mostly equivalent to redirecting their output to a given file. Without it, you will get the output on stdout. -- Adrien Nader -- I ran all four of the commands you mentioned above. Three were successfull from cygwin consoles and the gdk-pixbuf-query-loaders causes a seg-fault. $ ./gdk-pixbuf-query-loaders zsh: segmentation fault ./gdk-pixbuf-query-loaders $ ./gdk-pixbuf-query-loaders ../lib/gdk-pixbuf-2.0/2.10.0/loaders.cache zsh: segmentation fault ./gdk-pixbuf-query-loaders ../lib/gdk-pixbuf-2.0/2.10.0/loaders.cache # BUT C:\cygwin\opt\windows_32\bingdk-pixbuf-query-loaders C:\cygwin\opt\windows_32\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache Appears to run successfully in a MS command cosole. -- Also good news is that the gtk-demo ran successfully. The first time it did give me a message to run ?X to init ?y (Sorry lost screen shot). But, thereafter it runs well each time I tried it for about 3 tries. Cheers -- 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=84349831iu=/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] win-builds config options
Adrien Nader adr...@notk.org wrote:
skipped
I've installed pango in my cygwin installation and, combined with an
older version of the msys-install.sh script, I can see the issue.
Basically,
Can you try with this file instead:
http://cgit.notk.org/adrien/yypkg/win-builds.git/plain/msys-install.sh
You will have to edit it and replace '@@VERSION@@' with '1.3-rc1'.
I've done quite a lot of changes to it and it should be much smoother
under cygwin now. I still need to check a couple things to detect
whether the OS is 64b-capable or not but besides that, everything works.
While at it, you can grab the latest version of 'win-builds-switch.sh'
too:
http://cgit.notk.org/adrien/yypkg/win-builds.git/plain/win-builds-switch.sh
Regards,
Adrien Nader
I downloaded both the msys-install.sh and manually changed VERSION as directed
and ran it.
It segment faults on my platform. Here is the output
Installing zlib-1.2.8-1-i686-w64-mingw32.txz... DONE
Fatal error: exception Sys_error(Invalid argument)
Called from file pervasives.ml, line 444, characters 30-33
Called from file std_exit.ml, line 16, characters 8-20
Updating fontconfig's cache (this is slow and uses lots of RAM on Windows = 7).
Fatal error: exception Sys_error(Invalid argument)
Called from file pervasives.ml, line 444, characters 30-33
Called from file std_exit.ml, line 16, characters 8-20
Updating pango's module cache.
Fatal error: exception Sys_error(Invalid argument)
Called from file pervasives.ml, line 444, characters 30-33
Called from file std_exit.ml, line 16, characters 8-20
Updating gdk's pixbuf cache.
./msys-install.sh: line 22: 440 Segmentation fault
gdk-pixbuf-query-loaders --update-cache
$? = 139
--
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=84349831iu=/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] win-builds config options
Hi, On Fri, Dec 27, 2013, jdhenman wrote: Thanks Adrian. I downloaded the bundled then overwrote the two files specified with the versions you created. Changed to the proper directory, but wget which is ran from the script received a 404 file not found error. Here 's the output: $ ./msys-install.sh i686t Installing win-builds for i686t in C:/cygwin/opt/windows_. Downloading and installing packages. Downloading package_list.el...Command `C:\win-apps\msys\win-builds-bundle\wget.exe -O - -nv http://win-builds.org/1.3-rc1/packages/windows_/package_list.el' failed. Here is the content of stderr: http://win-builds.org/1.3-rc1/packages/windows_/package_list.el: 2013-12-27 13:09:40 ERROR 404: Not Found. Fatal error: exception Lib.ProcessFailed(_) prc[2]:win-apps/msys/win-builds-bundle $ The below text is just for reference. There is no new comments in it. That's because you made a typo and I haven't put enough checks in the script. :) You wrote i686t below instead of i686: $ ./msys-install.sh i686t I've added a check in git. Regards, Adrien Nader -- 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=84349831iu=/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] win-builds config options
On Sat, Jan 04, 2014, Adrien Nader wrote: On Mon, Dec 30, 2013, jdhenman wrote: wynfield wrote: The following error occurs when runing msys-install.sh md5sum 57efcca7eedbec35dd2496d3aa23193e *msys-install.sh $ ./msys-install.shmsys-install.sh i686 ... Installing x264-20131101-1-i686-w64-mingw32.txz... DONE Installing xz-5.0.5-1-i686-w64-mingw32.txz... DONE Installing zlib-1.2.8-1-i686-w64-mingw32.txz... DONE Updating GDK, GTK, Pango and font caches (this may take a while). Failed to create file '/usr/lib/pango/1.8.0/modules.cache.04I98W': No such file or directory ?? Any idea why the failure occurs above on creation fail? Upon reflection, the above error message Failed to create file '/usr/lib/pango/1.8.0/modules.cache.04I98W': No such file or directory, brings forth the following question. Shouldn't the path be: /opt/windows_32/lib/pango/1.8.0 instead? Since it is in the tree structure created by running: ./msys-install.shmsys-install.sh i686 That one is fairly weird. Do you have another installation of pango on your system? Like something from cygwin? I've installed pango in my cygwin installation and, combined with an older version of the msys-install.sh script, I can see the issue. Basically, Can you try with this file instead: http://cgit.notk.org/adrien/yypkg/win-builds.git/plain/msys-install.sh You will have to edit it and replace '@@VERSION@@' with '1.3-rc1'. I've done quite a lot of changes to it and it should be much smoother under cygwin now. I still need to check a couple things to detect whether the OS is 64b-capable or not but besides that, everything works. While at it, you can grab the latest version of 'win-builds-switch.sh' too: http://cgit.notk.org/adrien/yypkg/win-builds.git/plain/win-builds-switch.sh Regards, Adrien Nader -- 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=84349831iu=/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] win-builds config options
wynfield wrote: The following error occurs when runing msys-install.sh md5sum 57efcca7eedbec35dd2496d3aa23193e *msys-install.sh $ ./msys-install.shmsys-install.sh i686 ... Installing x264-20131101-1-i686-w64-mingw32.txz... DONE Installing xz-5.0.5-1-i686-w64-mingw32.txz... DONE Installing zlib-1.2.8-1-i686-w64-mingw32.txz... DONE Updating GDK, GTK, Pango and font caches (this may take a while). Failed to create file '/usr/lib/pango/1.8.0/modules.cache.04I98W': No such file or directory ?? Any idea why the failure occurs above on creation fail? Upon reflection, the above error message Failed to create file '/usr/lib/pango/1.8.0/modules.cache.04I98W': No such file or directory, brings forth the following question. Shouldn't the path be: /opt/windows_32/lib/pango/1.8.0 instead? Since it is in the tree structure created by running: ./msys-install.shmsys-install.sh i686 Thanks -- 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=84349831iu=/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] win-builds config options
Thanks Adrian. I downloaded the bundled then overwrote the two files specified with the versions you created. Changed to the proper directory, but wget which is ran from the script received a 404 file not found error. Here 's the output: $ ./msys-install.sh i686t Installing win-builds for i686t in C:/cygwin/opt/windows_. Downloading and installing packages. Downloading package_list.el...Command `C:\win-apps\msys\win-builds-bundle\wget.exe -O - -nv http://win-builds.org/1.3-rc1/packages/windows_/package_list.el' failed. Here is the content of stderr: http://win-builds.org/1.3-rc1/packages/windows_/package_list.el: 2013-12-27 13:09:40 ERROR 404: Not Found. Fatal error: exception Lib.ProcessFailed(_) prc[2]:win-apps/msys/win-builds-bundle $ The below text is just for reference. There is no new comments in it. Regards. Adrien Nader wrote: Hi, On Thu, Dec 26, 2013, wynfield: What is the package you are trying to compile ? I eventually want to build the Linphone application. (https://www.linphone.org/) It's current MS Windows port is out of date, crashes spuriously, and is not current. I do not wish to use Skype and consider it's use of private data is not desirable. However, I am starting with a simple GNU library, readline, to get the hang of using MinGW64 Win-Builds environment. Since many applications and lbraries from the *nix platform use a configure script, a shell is needed to run it. Does such a shell exist which uses Microsfot pathname formats? The difference between cygwin and msys (which is a fork of cygwin) is roughly that msys will test whether it is going to run a regular native windows application or an msys one and if it's a regular native one, it will automatically translate posix-style paths to windows ones. Cygwin is also much more comprehensive and therefore bigger; this makes some people prefer msys. I did a few changes and now I've mostly ported the msys install and environment setup scripts to cygwin. You need to download the bundle: http://win-builds.org/1.3-rc1/win-builds-bundle-1.3-rc1.zip and overwrite two of its files with these ones: http://notk.org/~adrien/win-builds-cygwin/msys-install.sh http://notk.org/~adrien/win-builds-cygwin/win-builds-switch.sh Then it's a matter of running these commands from a cygwin shell (you only need to cd into the bundle directory): ./msys-install.sh i686 ./msys-install.sh x86_64 After that you can set your environment with one of these commands: . win-builds-switch 32 . win-builds-switch 64 (note the leading . ) This will set the YYPREFIX and PKG_CONFIG_LIBDIR environment variables on both msys and cygwin (on msys it will also change PATH). That is all for win-builds; then you need to install the rest through cygwin's setup.exe. This is a rough list and you will add or remove packages related to these as you see fit and as you need them: mingw64-i686-gcc mingw64-x86_64-gcc pkg-config After that, I'm able to build a dummy program and link it to libvorbis with: i686-w64-mingw32 $(pkg-config --libs --cflags vorbis) test.c The command above is running in a cygwin shell, i686-w64-mingw32 and pkg-config are cygwin binaries, libvorbis comes from win-builds and a windows native executable is created. I hope the above solves your issues and is clear. I will be a bit harder to reach for roughly one week as I'm going to 30c3 in Hamburg and not taking my laptop with me. :) Regards, Adrien Nader -- 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=84349831iu=/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] win-builds config options
Hi, On Thu, Dec 26, 2013, wynfi...@gmail.com wrote: What is the package you are trying to compile ? I eventually want to build the Linphone application. (https://www.linphone.org/) It's current MS Windows port is out of date, crashes spuriously, and is not current. I do not wish to use Skype and consider it's use of private data is not desirable. However, I am starting with a simple GNU library, readline, to get the hang of using MinGW64 Win-Builds environment. Since many applications and lbraries from the *nix platform use a configure script, a shell is needed to run it. Does such a shell exist which uses Microsfot pathname formats? The difference between cygwin and msys (which is a fork of cygwin) is roughly that msys will test whether it is going to run a regular native windows application or an msys one and if it's a regular native one, it will automatically translate posix-style paths to windows ones. Cygwin is also much more comprehensive and therefore bigger; this makes some people prefer msys. I did a few changes and now I've mostly ported the msys install and environment setup scripts to cygwin. You need to download the bundle: http://win-builds.org/1.3-rc1/win-builds-bundle-1.3-rc1.zip and overwrite two of its files with these ones: http://notk.org/~adrien/win-builds-cygwin/msys-install.sh http://notk.org/~adrien/win-builds-cygwin/win-builds-switch.sh Then it's a matter of running these commands from a cygwin shell (you only need to cd into the bundle directory): ./msys-install.sh i686 ./msys-install.sh x86_64 After that you can set your environment with one of these commands: . win-builds-switch 32 . win-builds-switch 64 (note the leading . ) This will set the YYPREFIX and PKG_CONFIG_LIBDIR environment variables on both msys and cygwin (on msys it will also change PATH). That is all for win-builds; then you need to install the rest through cygwin's setup.exe. This is a rough list and you will add or remove packages related to these as you see fit and as you need them: mingw64-i686-gcc mingw64-x86_64-gcc pkg-config After that, I'm able to build a dummy program and link it to libvorbis with: i686-w64-mingw32 $(pkg-config --libs --cflags vorbis) test.c The command above is running in a cygwin shell, i686-w64-mingw32 and pkg-config are cygwin binaries, libvorbis comes from win-builds and a windows native executable is created. I hope the above solves your issues and is clear. I will be a bit harder to reach for roughly one week as I'm going to 30c3 in Hamburg and not taking my laptop with me. :) Regards, Adrien Nader -- 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=84349831iu=/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] win-builds config options
hey Basically, I installed MSYS (and only it, not MinGW) with the installer from MinGW.org, then i installed win-builds. See : http://win-builds.org/stable/#_from_windows_for_msys (I'm the one who provided to Adrien the first draft of the installation of win-builds in MSYS. So, no Cygwin at all :) and about the libraries : the Enlightenment Fundation Libraries (see http://www.enlightenment.org/ ) or the autotools :) What is the package you are trying to compile ? regards Vincent On Wed, Dec 25, 2013 at 1:29 AM, wynfi...@gmail.com wrote: Vincent Torri wrote: Hey Note that I have no problem to compile libraries using MSYS and Win-Builds. Vincent Torri That's nice Vicent. Please tell us what libraries or kinds of libraries are you talking about? And... are you invoking the MSYS/Win-Builds configure build chain from within a Cygwin environment or not? Are you using provided configure shell scripts with the libraries? What I'm am trying for find out how to do, is complile a package which was originally developed on Linux to a Microsoft Windows platform, using the standard toolchain provided with the Win-Builds' environment. Please let us know. Thanks REF: On Tue, Dec 24, 2013 at 9:32 AM, Adrien Nader wrote: Hi, On Tue, Dec 24, 2013, wrote: I need some advice on configuration options for building the GNU readline library. I am new to win-builds and mingw64 Platform is: MS Windows XP SP3. I have the latest cygwin installed and the new win-builds separately installed. When invoking the configure script which comes with GNU readline source I do the following: wb=/cgydrive/c/win-builds-w32 PATH=$wb/bin:.:$wb/local/bin:/bin:/usr/local/bin:$wds:$s PKG_CONFIG_LIBDIR=/cygdrive/c/win-builds-32/lib/pkgconfig I don't think you can use the compilers provided by win-builds directly under cygwin. As you've already seen, they expect windows-style paths while cygwin will hand them posix-style ones. I haven't checked yet but you should be able to use the cross-compilers provided by cygwin as mingw64-i686-gcc(-g++) or with x86_64 instead of i686. This means you wouldn't prepend $wb/bin to your PATH and probably not put $wb/local/bin either. The restriction is that the compilers from win-builds and from cygwin must have compatible configurations, especially for C++. This mostly means sjlj exception on 32b and SEH ones on 64b; which are the default settings. Your current pkg-config and libdir settings seem good. To sum up, you need the cygwin compiler (installed and default value for PATH) and the win-builds binaries (set PKG_CONFIG_LIBDIR and --libdir). ./configure --host=i686-w64-mingw32 --prefix=$wb/local --libexecdir=$wb/sbin --libdir=$wb/lib --includedir=$wb/include You probably don't need to set all these paths (in particular libexecdir); configure should set most of them properly by itself. Start with only --host, --prefix and --libdir. Add --includedir if some includes are not found while they're in this directory. I am not sure if the --host=i686-w64-mingw32 is valide for the win-builds distribution. It is the right triplet for 32 bits. The configure script is finding and using the Cygwin environment, which I think is not want should be done. I guess it tries to use the win-builds-provided GCC but fails to do so because of paths and fallbacks to the cygwin one. I am attaching the full output the configure script as a file. If you continue to have issues, could you send me the config.log file? Don't send it on the mailing-list since it is usually a fairly big file which makes up for a fair amount of data when multiplied by the number of list subscribers. Regards, Adrien nader -- 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=84349831iu=/4140/ostg.clktrk ___ #EOM -- 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=84349831iu=/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] win-builds config options
Vincent Torri vincent.to...@gmail.com wrote: hey Basically, I installed MSYS (and only it, not MinGW) with the installer from MinGW.org, then i installed win-builds. See : http://win-builds.org/stable/#_from_windows_for_msys (I'm the one who provided to Adrien the first draft of the installation of win-builds in MSYS. So, no Cygwin at all :) Why do you express that statement as a smiley ? Cygwin and the tools it provides are very helpful for many computational needs. and about the libraries : the Enlightenment Fundation Libraries (see http://www.enlightenment.org/ ) or the autotools :) Thanks for the URL. I will check it out. What is the package you are trying to compile ? I eventually want to build the Linphone application. (https://www.linphone.org/) It's current MS Windows port is out of date, crashes spuriously, and is not current. I do not wish to use Skype and consider it's use of private data is not desirable. However, I am starting with a simple GNU library, readline, to get the hang of using MinGW64 Win-Builds environment. Since many applications and lbraries from the *nix platform use a configure script, a shell is needed to run it. Does such a shell exist which uses Microsfot pathname formats? regards Vincent Cheers -- 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=84349831iu=/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] win-builds config options
Hi, On Tue, Dec 24, 2013, wynfi...@gmail.com wrote: I need some advice on configuration options for building the GNU readline library. I am new to win-builds and mingw64 Platform is: MS Windows XP SP3. I have the latest cygwin installed and the new win-builds separately installed. When invoking the configure script which comes with GNU readline source I do the following: wb=/cgydrive/c/win-builds-w32 PATH=$wb/bin:.:$wb/local/bin:/bin:/usr/local/bin:$wds:$s PKG_CONFIG_LIBDIR=/cygdrive/c/win-builds-32/lib/pkgconfig I don't think you can use the compilers provided by win-builds directly under cygwin. As you've already seen, they expect windows-style paths while cygwin will hand them posix-style ones. I haven't checked yet but you should be able to use the cross-compilers provided by cygwin as mingw64-i686-gcc(-g++) or with x86_64 instead of i686. This means you wouldn't prepend $wb/bin to your PATH and probably not put $wb/local/bin either. The restriction is that the compilers from win-builds and from cygwin must have compatible configurations, especially for C++. This mostly means sjlj exception on 32b and SEH ones on 64b; which are the default settings. Your current pkg-config and libdir settings seem good. To sum up, you need the cygwin compiler (installed and default value for PATH) and the win-builds binaries (set PKG_CONFIG_LIBDIR and --libdir). ./configure --host=i686-w64-mingw32 --prefix=$wb/local --libexecdir=$wb/sbin --libdir=$wb/lib --includedir=$wb/include You probably don't need to set all these paths (in particular libexecdir); configure should set most of them properly by itself. Start with only --host, --prefix and --libdir. Add --includedir if some includes are not found while they're in this directory. I am not sure if the --host=i686-w64-mingw32 is valide for the win-builds distribution. It is the right triplet for 32 bits. The configure script is finding and using the Cygwin environment, which I think is not want should be done. I guess it tries to use the win-builds-provided GCC but fails to do so because of paths and fallbacks to the cygwin one. I am attaching the full output the configure script as a file. If you continue to have issues, could you send me the config.log file? Don't send it on the mailing-list since it is usually a fairly big file which makes up for a fair amount of data when multiplied by the number of list subscribers. Regards, Adrien nader -- 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=84349831iu=/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] win-builds config options
Hey Note that I have no problem to compile libraries using MSYS and Win-Builds. Vincent Torri On Tue, Dec 24, 2013 at 9:32 AM, Adrien Nader adr...@notk.org wrote: Hi, On Tue, Dec 24, 2013, wynfi...@gmail.com wrote: I need some advice on configuration options for building the GNU readline library. I am new to win-builds and mingw64 Platform is: MS Windows XP SP3. I have the latest cygwin installed and the new win-builds separately installed. When invoking the configure script which comes with GNU readline source I do the following: wb=/cgydrive/c/win-builds-w32 PATH=$wb/bin:.:$wb/local/bin:/bin:/usr/local/bin:$wds:$s PKG_CONFIG_LIBDIR=/cygdrive/c/win-builds-32/lib/pkgconfig I don't think you can use the compilers provided by win-builds directly under cygwin. As you've already seen, they expect windows-style paths while cygwin will hand them posix-style ones. I haven't checked yet but you should be able to use the cross-compilers provided by cygwin as mingw64-i686-gcc(-g++) or with x86_64 instead of i686. This means you wouldn't prepend $wb/bin to your PATH and probably not put $wb/local/bin either. The restriction is that the compilers from win-builds and from cygwin must have compatible configurations, especially for C++. This mostly means sjlj exception on 32b and SEH ones on 64b; which are the default settings. Your current pkg-config and libdir settings seem good. To sum up, you need the cygwin compiler (installed and default value for PATH) and the win-builds binaries (set PKG_CONFIG_LIBDIR and --libdir). ./configure --host=i686-w64-mingw32 --prefix=$wb/local --libexecdir=$wb/sbin --libdir=$wb/lib --includedir=$wb/include You probably don't need to set all these paths (in particular libexecdir); configure should set most of them properly by itself. Start with only --host, --prefix and --libdir. Add --includedir if some includes are not found while they're in this directory. I am not sure if the --host=i686-w64-mingw32 is valide for the win-builds distribution. It is the right triplet for 32 bits. The configure script is finding and using the Cygwin environment, which I think is not want should be done. I guess it tries to use the win-builds-provided GCC but fails to do so because of paths and fallbacks to the cygwin one. I am attaching the full output the configure script as a file. If you continue to have issues, could you send me the config.log file? Don't send it on the mailing-list since it is usually a fairly big file which makes up for a fair amount of data when multiplied by the number of list subscribers. Regards, Adrien nader -- 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=84349831iu=/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=84349831iu=/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] win-builds config options
Vincent Torri wrote: Hey Note that I have no problem to compile libraries using MSYS and Win-Builds. Vincent Torri That's nice Vicent. Please tell us what libraries or kinds of libraries are you talking about? And... are you invoking the MSYS/Win-Builds configure build chain from within a Cygwin environment or not? Are you using provided configure shell scripts with the libraries? What I'm am trying for find out how to do, is complile a package which was originally developed on Linux to a Microsoft Windows platform, using the standard toolchain provided with the Win-Builds' environment. Please let us know. Thanks REF: On Tue, Dec 24, 2013 at 9:32 AM, Adrien Nader wrote: Hi, On Tue, Dec 24, 2013, wrote: I need some advice on configuration options for building the GNU readline library. I am new to win-builds and mingw64 Platform is: MS Windows XP SP3. I have the latest cygwin installed and the new win-builds separately installed. When invoking the configure script which comes with GNU readline source I do the following: wb=/cgydrive/c/win-builds-w32 PATH=$wb/bin:.:$wb/local/bin:/bin:/usr/local/bin:$wds:$s PKG_CONFIG_LIBDIR=/cygdrive/c/win-builds-32/lib/pkgconfig I don't think you can use the compilers provided by win-builds directly under cygwin. As you've already seen, they expect windows-style paths while cygwin will hand them posix-style ones. I haven't checked yet but you should be able to use the cross-compilers provided by cygwin as mingw64-i686-gcc(-g++) or with x86_64 instead of i686. This means you wouldn't prepend $wb/bin to your PATH and probably not put $wb/local/bin either. The restriction is that the compilers from win-builds and from cygwin must have compatible configurations, especially for C++. This mostly means sjlj exception on 32b and SEH ones on 64b; which are the default settings. Your current pkg-config and libdir settings seem good. To sum up, you need the cygwin compiler (installed and default value for PATH) and the win-builds binaries (set PKG_CONFIG_LIBDIR and --libdir). ./configure --host=i686-w64-mingw32 --prefix=$wb/local --libexecdir=$wb/sbin --libdir=$wb/lib --includedir=$wb/include You probably don't need to set all these paths (in particular libexecdir); configure should set most of them properly by itself. Start with only --host, --prefix and --libdir. Add --includedir if some includes are not found while they're in this directory. I am not sure if the --host=i686-w64-mingw32 is valide for the win-builds distribution. It is the right triplet for 32 bits. The configure script is finding and using the Cygwin environment, which I think is not want should be done. I guess it tries to use the win-builds-provided GCC but fails to do so because of paths and fallbacks to the cygwin one. I am attaching the full output the configure script as a file. If you continue to have issues, could you send me the config.log file? Don't send it on the mailing-list since it is usually a fairly big file which makes up for a fair amount of data when multiplied by the number of list subscribers. Regards, Adrien nader -- 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=84349831iu=/4140/ostg.clktrk ___ #EOM -- 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=84349831iu=/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] win-builds config options
I need some advice on configuration options for building the GNU readline
library.
I am new to win-builds and mingw64
Platform is: MS Windows XP SP3. I have the latest cygwin installed and the
new win-builds separately installed.
When invoking the configure script which comes with GNU readline source I do
the following:
wb=/cgydrive/c/win-builds-w32
PATH=$wb/bin:.:$wb/local/bin:/bin:/usr/local/bin:$wds:$s
PKG_CONFIG_LIBDIR=/cygdrive/c/win-builds-32/lib/pkgconfig
./configure --host=i686-w64-mingw32 --prefix=$wb/local --libexecdir=$wb/sbin
--libdir=$wb/lib --includedir=$wb/include
I am not sure if the --host=i686-w64-mingw32 is valide for the win-builds
distribution.
The configure script is finding and using the Cygwin environment, which I think
is not want should be done.
I am attaching the full output the configure script as a file.
checking build system type... i686-pc-cygwin
checking host system type... i686-w64-mingw32
Beginning configuration for readline-6.2 for i686-w64-mingw32
checking whether make sets $(MAKE)... yes
checking for i686-w64-mingw32-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether gcc needs -traditional... no
checking for a BSD-compatible install... /bin/install -c
checking for ar... ar
checking for i686-w64-mingw32-ranlib... no
checking for ranlib... ranlib
checking for an ANSI C-conforming const... yes
checking for function prototypes... yes
checking whether char is unsigned... no
checking for working volatile... yes
checking return type of signal handlers... void
checking for size_t... yes
checking for ssize_t... yes
checking for ANSI C header files... (cached) yes
checking whether stat file-mode macros are broken... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for fcntl... yes
checking for kill... yes
checking for lstat... yes
checking for memmove... yes
checking for putenv... yes
checking for select... yes
checking for setenv... yes
checking for setlocale... yes
checking for strcasecmp... yes
checking for strpbrk... yes
checking for tcgetattr... yes
checking for vsnprintf... yes
checking for isascii... yes
checking for isxdigit... yes
checking for getpwent... yes
checking for getpwnam... yes
checking for getpwuid... yes
checking for working strcoll... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for unistd.h... (cached) yes
checking for stdlib.h... (cached) yes
checking varargs.h usability... no
checking varargs.h presence... no
checking for varargs.h... no
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking for memory.h... (cached) yes
checking termcap.h usability... no
checking termcap.h presence... no
checking for termcap.h... no
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking termio.h usability... yes
checking termio.h presence... yes
checking for termio.h... yes
checking sys/pte.h usability... no
checking sys/pte.h presence... no
checking for sys/pte.h... no
checking sys/stream.h usability... no
checking sys/stream.h presence... no
checking for sys/stream.h... no
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking for sys/ptem.h... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
