Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.5 (2010-07-11)
On Mon, Jul 12, 2010 at 3:40 PM, Wolfgang Glas wrote: > On 2010-07-12 13:25, Ozkan Sezer wrote: >> On Sun, Jul 11, 2010 at 10:06 PM, Ozkan Sezer wrote: > > [snip] > >>> --- >>> - Wolfgang Glas previously reported that the "dllwrap" tool is broken. I >>> haven't tested myself to confirm the breakage and not done anything in >>> this build to fix it yet, either. >> >> Just uploaded a tiny update package for win64-targeting toolchains >> fixing this particular issue: sezero_20100711_w64_dllwrap_update.zip > > Ozkan, I knew that this low-hanging fruit for you and you will fix this thing > ;-) > Actually it is Kai's fix ;) I just provided made the update binaries and upoaded. > I just came across it, because I tried to build zlib using historic > makefiles... > > Wolfgang > -- Ozkan -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.5 (2010-07-11)
On 2010-07-12 13:25, Ozkan Sezer wrote: > On Sun, Jul 11, 2010 at 10:06 PM, Ozkan Sezer wrote: [snip] >> --- >> - Wolfgang Glas previously reported that the "dllwrap" tool is broken. I >> haven't tested myself to confirm the breakage and not done anything in >> this build to fix it yet, either. > > Just uploaded a tiny update package for win64-targeting toolchains > fixing this particular issue: sezero_20100711_w64_dllwrap_update.zip Ozkan, I knew that this low-hanging fruit for you and you will fix this thing ;-) I just came across it, because I tried to build zlib using historic makefiles... Wolfgang -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.5 (2010-07-11)
On Sun, Jul 11, 2010 at 10:06 PM, Ozkan Sezer wrote: > I updated my custom w32/w64 native and cross-compiler build with gcc-4.4 > with several backports and fixes from mainstream, and put them under the > mingw-w64 sf.net file release system under the subdirectories: > - Toolchain sources -> Personal Builds, > - Toolchains targetting Win32 -> Personal Builds and > - Toolchains targetting Win64 -> Personal Builds > > Build July 11, 2010: > > Changes since 2010-07-02 build: > --- > - Updated mingw-w64 crt and headers to svn rev. 2823: A couple of header > updates and import library fixes. > - Binutils updated to fix a symbol quotation problem. > - GCC updated to 4.4.5-prerelease rev. 162041 to catch up with several > upstream fixes. > - Added fixes for GCC PR/44703 and PR/43888. Added a symbol quotation fix > for the aligncomm problem from trunk. > - Make CVS snapshot updated to catch up with several upstream fixes. > > Full ChangeLog: > --- > - See attached file ChangeLog. > > Changes in included software from mainline versions: > --- > - See attached file ChangeLog.sezero. > > Known problems: > --- > - Wolfgang Glas previously reported that the "dllwrap" tool is broken. I > haven't tested myself to confirm the breakage and not done anything in > this build to fix it yet, either. Just uploaded a tiny update package for win64-targeting toolchains fixing this particular issue: sezero_20100711_w64_dllwrap_update.zip -- Ozkan > - The /include path "problem" of the native builds is not > looked into, yet. Maybe in the future builds. > > Compatibility Notice: ** No leading underscore ** > --- > Unlike the other builds from mingw-w64 up to 2010-04-27, these new win64 > targetting toolchains do *not* prepend an undersocore to the symbols and > follows the MSVC x64 convention. Therefore, any of the link libraries > from previous toolchains are incompatible with the ones created by these > new builds. > > > Included software versions: > --- > > Common in both cross- and native-toolchains: > > - gcc : svn rev. 162041 (4.4.5 prerelease with many patches) > - binutils : 2.20.51 (cvs, 2010-07-11 / 09:25 GMT) with patches. > - mingw-w64-crt : svn revision 2823 (2010-07-08) > - mingw-w64-headers : svn revision 2820 (2010-07-08) with a few of patches > - glext headers: 2010-06-17 (from the Khronos Group) > - pthreads-win32: 2.9.0 (CVS 2010-02-28 20:00 GMT) with w64 patch applied. > > In native-toolchains only: > > - gmp : 4.3.2 (with w64 patch applied) > - mpfr: 2.4.2-p3 > - mpc : 0.8.2 > - gdb : 7.1.50 (CVS 2010-07-11 / 09:25 GMT, with minor w64 patches applied) > - make: 3.81.90 (CVS 2010-07-09 / 14:20 GMT, with patches applied according > to savannah bug item 27809.) > - gendef, libmangle: from mingw-w64 svn/trunk > > > File names: > --- > > * Source: > > - mingw-w64-src_20100711_sezero.tar.gz > > > * Targetting Win64: > > - mingw-w64-bin_x86_64-mingw_20100711_sezero.zip > native compiler toolchain for running on x64-windows > host and creating x64-windows binaries. > > - mingw-w64-bin_i686-mingw_20100711_sezero.zip > cross compiler toolchain for running on x86-windows > host but creating x64-windows binaries. > > - mingw-w64-bin_i686-linux_20100711_sezero.tar.gz > cross compiler toolchain for running on a i686-linux > host and creating x64-windows binaries. > > - mingw-w64-bin_x86_64-linux_20100711_sezero.tar.gz > cross compiler toolchain for running on a x86_64-linux > host and creating x64-windows binaries. > > > * Targetting Win32: > > - mingw-w32-bin_i686-mingw_20100711_sezero.zip > native compiler toolchain for running on x86-windows > host and creating x86-windows binaries. > > - mingw-w32-bin_i686-linux_20100711_sezero.tar.gz > cross compiler toolchain for running on a i686-linux > host and creating x86-windows binaries. > > - mingw-w32-bin_x86_64-linux_20100711_sezero.tar.gz > cross compiler toolchain for running on a x86_64-linux > host and creating x86-windows binaries. > > -- > Ozkan > -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Using mingw-w32-bin_i686-cygwin packages
2010/7/9 Angelo Graziosi :
> It is some time I am using these mingw-w32-bin_i686-cygwin packages on
> Cygwin, but recently it seems that there are some problems.
>
> The last useful package wich works for me is:
> mingw-w32-bin_i686-cygwin-1.7.5-1_20100617.tar.bz2. All packages
> released after (...20100704, 20100708) do not work: I can build
> executables but they do not produce any output. For example:
>
> $ tar -xvof mingw-w32-bin_i686-cygwin-1.7.5-1_20100708.tar.bz2 -C
> /usr/local/mingw-w64
>
> $ cd /usr/local/bin
>
> $ ln -sf /usr/local/mingw-w64/bin/i686-w64-mingw32-g++.exe mingw32-g++
>
> $ export PATH="/usr/local/mingw-w64/bin:$PATH"
>
> $ cat /tmp/hello.cpp
> /* hello.c */
> #include
>
> using namespace std;
>
> int main()
> {
> cout << "Hello World" << endl;
> return 0;
> }
>
> $ mingw32-g++ hello.cpp
>
> $ ./a.exe &
> [1] 3504
>
> $
> [1]+ Exit 127 ./a.exe
>
>
> If I remember correctly, 'Exit 127' means 'missing DLL'. What? Why then
>
> mingw-w32-bin_i686-cygwin-1.7.5-1_20100615.tar.bz2
> mingw-w32-bin_i686-cygwin-1.7.5-1_20100617.tar.bz2
>
> work just fine?
>
> I have also tried this:
>
> $ cygcheck ./a.exe
> C:\cygwin-2\tmp\a.exe
> C:\WINDOWS\system32\KERNEL32.dll
> C:\WINDOWS\system32\ntdll.dll
> C:\WINDOWS\system32\msvcrt.dll
> C:\cygwin-2\usr\local\mingw-w64\bin\libstdc++-6.dll
> C:\cygwin-2\usr\local\mingw-w64\bin\libgcc_s_sjlj-1.dll
> C:\WINDOWS\system32\USER32.dll
> C:\WINDOWS\system32\GDI32.dll
>
> $ ldd ./a.exe
> ntdll.dll => /cygdrive/c/WINDOWS/system32/ntdll.dll (0x7c91)
> kernel32.dll => /cygdrive/c/WINDOWS/system32/kernel32.dll
> (0x7c80)
> msvcrt.dll => /cygdrive/c/WINDOWS/system32/msvcrt.dll (0x77be)
> libstdc++-6.dll => /usr/local/mingw-w64/bin/libstdc++-6.dll
> (0x6fc4)
> libgcc_s_sjlj-1.dll =>
> /usr/local/mingw-w64/bin/libgcc_s_sjlj-1.dll (0x6cec)
> USER32.dll => /cygdrive/c/WINDOWS/system32/USER32.dll (0x7e39)
> GDI32.dll => /cygdrive/c/WINDOWS/system32/GDI32.dll (0x77e4)
>
>
> which, apparently, do not flag any missed DLL
>
> Any idea?
>
> Thanks,
> Angelo.
>
> (NightStrike, JonY, sorry if I have added you... I am not subscribed to
> mingw-w64-public list... :()
Hello Angelo,
First, please subscribe to list before posting to it. Otherwise it can
be likely that a message gets unnecessary delayed or even deleted by
accident.
To your issue. Yes indeed the the failure-code seems to be a missing
DLL, or a wrong DLL with missing exports. I assume that not all
gcc-related DLL files are in your search path. You can try to use here
option '-static' to see, if it works without DLL files.
I hope I could help,
Kai
PS: Please subscribe to this list before replying, thanks.
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Using mingw-w32-bin_i686-cygwin packages
It is some time I am using these mingw-w32-bin_i686-cygwin packages on
Cygwin, but recently it seems that there are some problems.
The last useful package wich works for me is:
mingw-w32-bin_i686-cygwin-1.7.5-1_20100617.tar.bz2. All packages
released after (...20100704, 20100708) do not work: I can build
executables but they do not produce any output. For example:
$ tar -xvof mingw-w32-bin_i686-cygwin-1.7.5-1_20100708.tar.bz2 -C
/usr/local/mingw-w64
$ cd /usr/local/bin
$ ln -sf /usr/local/mingw-w64/bin/i686-w64-mingw32-g++.exe mingw32-g++
$ export PATH="/usr/local/mingw-w64/bin:$PATH"
$ cat /tmp/hello.cpp
/* hello.c */
#include
using namespace std;
int main()
{
cout << "Hello World" << endl;
return 0;
}
$ mingw32-g++ hello.cpp
$ ./a.exe &
[1] 3504
$
[1]+ Exit 127./a.exe
If I remember correctly, 'Exit 127' means 'missing DLL'. What? Why then
mingw-w32-bin_i686-cygwin-1.7.5-1_20100615.tar.bz2
mingw-w32-bin_i686-cygwin-1.7.5-1_20100617.tar.bz2
work just fine?
I have also tried this:
$ cygcheck ./a.exe
C:\cygwin-2\tmp\a.exe
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\msvcrt.dll
C:\cygwin-2\usr\local\mingw-w64\bin\libstdc++-6.dll
C:\cygwin-2\usr\local\mingw-w64\bin\libgcc_s_sjlj-1.dll
C:\WINDOWS\system32\USER32.dll
C:\WINDOWS\system32\GDI32.dll
$ ldd ./a.exe
ntdll.dll => /cygdrive/c/WINDOWS/system32/ntdll.dll (0x7c91)
kernel32.dll => /cygdrive/c/WINDOWS/system32/kernel32.dll
(0x7c80)
msvcrt.dll => /cygdrive/c/WINDOWS/system32/msvcrt.dll (0x77be)
libstdc++-6.dll => /usr/local/mingw-w64/bin/libstdc++-6.dll
(0x6fc4)
libgcc_s_sjlj-1.dll =>
/usr/local/mingw-w64/bin/libgcc_s_sjlj-1.dll (0x6cec)
USER32.dll => /cygdrive/c/WINDOWS/system32/USER32.dll (0x7e39)
GDI32.dll => /cygdrive/c/WINDOWS/system32/GDI32.dll (0x77e4)
which, apparently, do not flag any missed DLL
Any idea?
Thanks,
Angelo.
(NightStrike, JonY, sorry if I have added you... I am not subscribed to
mingw-w64-public list... :()
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
