[Mingw-w64-public] Win-builds 1.3 RC1
Hi, I'm happy to release the 1.3 RC1 version of the win-builds.org project. This project creates a system to build and distribute for Windows from almost any system: *native* Windows, MSYS*, Cygwin and Linux. Everything is done through a portable package manager for easy installation, maintenance and update. As with previous versions, this one mostly brings fixes and documentation updates. The most important changes are: - stop relying on mklink.exe to create directory junctions - fixed mingw symlink in the root dir on windows (combined with the previous change, this fixes installation on Windows XP/2k3) - fix wrong mirror in the Linux chroot - remove extra symlinks to non-existent gfortran binaries - missing .exe extension for some GCC binaries - some files weren't removed when removing a package - libjpeg update to fix CVE-2013-6629 ( http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6629 ) - introduce an .bat file to automate installation steps; its use is described at http://win-builds.org/1.3-rc1/#_from_windows (full GUI installer a bit later) The hope is that besides minor tweaks, 1.3 RC1 can be promoted to 1.3 stable. As a reminder, some highlights of the 1.3 version: - updated GCC, mingw-w64 and other packages - new packages: winpthreads, dbus, x264 - fallbacks for POSIX symlink on Windows - almost exhaustive documentation - stabilization of the build system along with speed improvements - maintained for security updates For all issues, you can use the bugtracker at: Website: http://win-builds.org Bug Tracker: http://win-builds.org/bugs/ -- 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] crtdll.dll missing from 4.9.0 experimental?
On 23 December 2013 08:21, Jim Michaels jmich...@yahoo.com wrote: I am trying to call _getcwd() which apparently is only found in crtdll.dll which is not included, or a specific version of windows or a microsoft compiler's msvcrt*.dll any solution for this? I am using d:\x86_64-4.8.2-release-posix-sjlj-rt_v3-rev0 d:\i686-4.8.2-release-posix-sjlj-rt_v3-rev0 was that something found in win98? I would have to check I guess, but curious about this dll, never seen it before. there is a libcrtdll.a file for it. _getcwd() is exported from msvcrt.dll as well. crtdll.dll is a pre-msvcrt.dll 32-bit-only MSVC runtime. According to my observations, it is found in all Windows NT and 9x versions. -- 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] clang on Windows
You have to compile Clang with MinGW, otherwise Clang will use VS's toolchain. 2013/12/23 Baruch Burstein bmburst...@gmail.com I apologize if this is not the right place for this. If so, letme know and I will not post more questions about clang to here. This question is really targeted towards Ruben and others on this list who have built clang toolchains for Windows. I just tried building clang myself (nothing fancy, just following the step-by-step instructions on their site for building with VS) and discovered the the resulting clang.exe uses the VS linker. There is an executable llvm-link.exe, though I am not sure it is a linker (just guessing from the name). What did you do in your toolchains? Did you include the mingw64 linker, or did you get it to use the llvm linker somehow? Thanks, Baruch -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -- 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
[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
