From: Ralph E. <ral...@gm...> - 2011-09-11 18:41:16
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bit stuck i need someone with good knowladge of gnu makefiles to adjust the remaining stuff to accept the Msys structure. Been at it for days now. Somehow i get a feeling that my gcc version 4.3.4 fails to export __MSYS__ as i noticed it totally ignores #ifdef __MSYS__ in the sources. But without a gcc version of atleast 4 its impossible to build argh!. Teemu supplied me with a version built for standard Msys but it was missing cc1.exe cc1plus.exe and collect2.exe besides the gcc dll so i had to make cruel hack to rebuild a new version using the parts he sent me but it seems to be broken in regards to the above. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObQEfAAoJEIjGvG7Y4HU8FF8H/jtrSqIpw4RZqT02AUKaAZQy ENtfUewRkGAtz9SYkOjkvok87M1J3NYq7CQoS5ejvxUDO5H5p8FjpOt/Y7wd2fOK 2wi3TSO3eqLgTWIIx0ItFAO0OWmsgkbX4TDp/FPr12nrCGaeHczzQD+voUUKogT0 01mYQTJc/1INbegmtZobDwFbunD61xRTacf6AytgZm6mSM2nvhV+TMFGfO011vjB u3CvTh57tpXgooW1rHOWV8YPv2rl0s35iqW1YlQdR2/vtxnrafoJulWV7BvZsW8k GOtZqVMLAG+YUekdf25zZHIjdIsGCDycw3ertbkiJgpz7iAvLTuC3IvEmaBfI7g= =dG3Y -----END PGP SIGNATURE----- |
From: Ralph E. <ral...@gm...> - 2011-09-27 17:16:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok i was not aware of that, allthough i noticed that cygwin symlinks looked differently than standard nt junction points i had the thought it worked a bit like these. Seems we have to remove them then or atleast turn them of for mingw. Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOggUgAAoJEIjGvG7Y4HU8eNsIAKNxg7ATcbK9iHIRYDN+oarQ MlLGNfPdsaUZgt6gEga6C6EH2jTv1qfojDif3RjEnNupXutgNBcOd0ac9SJgQhlT YaOj6z53PKyUK+COcgCkx7wHwQxMewjm3CzIHYqpGkyqQn1Ra4lRXwaWwqjMgAHH spCW1onUiLVdHBELX4eS6UjDH8UuQZRSVLFtgyj8WsxwI4G1WMUoPrJfvQuDAqKf z8pbFDW6yMvm2mde14+0d/iu2IeaRDQ07eAm/XC8+MPc3+U7ktx2zzbedt29aeKf R13rOgL6xK9w3sEEybPJ+kBnlzdsz2VqWakWuv8pIeRhRu3DakGw8ZZuJg/T6E0= =Nwhv -----END PGP SIGNATURE----- |
From: xunxun <xun...@gm...> - 2011-10-17 17:50:05
|
Hi, reckless 于 2011/9/28 1:17, Ralph Engels 写道: > Ok i was not aware of that, allthough i noticed that cygwin symlinks > looked differently than standard nt junction points i had the thought > it worked a bit like these. > > Seems we have to remove them then or atleast turn them of for mingw. Has msys2 been completed? -- Best Regards, xunxun |
From: Teemu N. <sti...@ya...> - 2011-09-11 19:00:47
|
On 11.9.2011 21:42, Ralph Engels wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bit stuck i need someone with good knowladge of gnu makefiles to > adjust the remaining stuff to accept the Msys structure. Been at it > for days now. Somehow i get a feeling that my gcc version 4.3.4 fails > to export __MSYS__ as i noticed it totally ignores #ifdef __MSYS__ in > the sources. Can you post gcc -dumpspecs? > But without a gcc version of atleast 4 its impossible to build argh!. > Teemu supplied me with a version built for standard Msys but it was > missing cc1.exe cc1plus.exe and collect2.exe besides the gcc dll so i > had to make cruel hack to rebuild a new version using the parts he > sent me but it seems to be broken in regards to the above. Like I said, it is *very* hacky. |
From: Ralph E. <ral...@gm...> - 2011-09-11 20:00:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 11-09-2011 21:00, Teemu Nätkinniemi skrev: > On 11.9.2011 21:42, Ralph Engels wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Bit stuck i need someone with good knowladge of gnu makefiles to >> adjust the remaining stuff to accept the Msys structure. Been at >> it for days now. Somehow i get a feeling that my gcc version >> 4.3.4 fails to export __MSYS__ as i noticed it totally ignores >> #ifdef __MSYS__ in the sources. > > Can you post gcc -dumpspecs? > >> But without a gcc version of atleast 4 its impossible to build >> argh!. Teemu supplied me with a version built for standard Msys >> but it was missing cc1.exe cc1plus.exe and collect2.exe besides >> the gcc dll so i had to make cruel hack to rebuild a new version >> using the parts he sent me but it seems to be broken in regards >> to the above. > > Like I said, it is *very* hacky. > > ------------------------------------------------------------------------------ > > Using storage to extend the benefits of virtualization and iSCSI > Virtualization increases hardware utilization and delivers a new > level of agility. Learn what those decisions are and how to > modernize your storage and backup environments for virtualization. > http://www.accelacomm.com/jaw/sfnl/114/51434361/ > _______________________________________________ Mingw-msys mailing > list Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys oh crud seems it returns __CYGWIN__ instead of __MSYS__ i thought i replaced all ocurrences of that :x damn hope i can make a new version. Ok patched 4.3.4 with cygwin patches and replaced the cygwin frag with an msys specific one + replaced all occurences of __CYGWIN__ with __MSYS__ (tripple checked this time) crossing fingers it will build. Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObROeAAoJEIjGvG7Y4HU8OmwH/A4bwPZwc1Y9zTmZVap+JCsu zCGc77rjW2vU6vBy4k1lIOLeaLZHlDdK7lB1ZQJ+uzVBB7gl4glZ+bPX5rPET5uM Q7pBGDi2smuCMvvlqosD93KPimQpZdxN/cNsuSYR/mHO7Bok10BQcFNOlHxX7ioD q+FxTT9VkcFzZ/mSPGWLGc/dV8hmHVcc561rZvttqojF8dPD4Ag0UrCViMTntMC1 9HVH5afivQYEV2U1kPjHES4IZOFXHW30HCjkKgLyZrxfvlSpaJYTqmAGXIFRwRv2 /pIb7F3S56Qtg0QqhEEqo025emB9dHMQl0MJsC1BNRTAx66+JOzeyokWiuapMxY= =zy61 -----END PGP SIGNATURE----- |
From: Teemu N. <sti...@ya...> - 2011-09-11 20:03:05
|
On 11.9.2011 23:01, Ralph Engels wrote: > oh crud seems it returns __CYGWIN__ instead of __MSYS__ i thought i > replaced all ocurrences of that :x damn hope i can make a new version. > Ok patched 4.3.4 with cygwin patches and replaced the cygwin frag with > an msys specific one + replaced all occurences of __CYGWIN__ with > __MSYS__ (tripple checked this time) crossing fingers it will build. Could you post your progress so far with GCC, Binutils and MSYS? |
From: Ralph E. <ral...@gm...> - 2011-09-11 21:08:31
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 11-09-2011 22:03, Teemu Nätkinniemi skrev: > On 11.9.2011 23:01, Ralph Engels wrote: > >> oh crud seems it returns __CYGWIN__ instead of __MSYS__ i thought >> i replaced all ocurrences of that :x damn hope i can make a new >> version. Ok patched 4.3.4 with cygwin patches and replaced the >> cygwin frag with an msys specific one + replaced all occurences >> of __CYGWIN__ with __MSYS__ (tripple checked this time) crossing >> fingers it will build. > > Could you post your progress so far with GCC, Binutils and MSYS? > > ------------------------------------------------------------------------------ > > Using storage to extend the benefits of virtualization and iSCSI > Virtualization increases hardware utilization and delivers a new > level of agility. Learn what those decisions are and how to > modernize your storage and backup environments for virtualization. > http://www.accelacomm.com/jaw/sfnl/114/51434361/ > _______________________________________________ Mingw-msys mailing > list Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys Building a new version of gcc now actually. I stayed with the old binutils package for now because the broken gcc i used before caused the new binutils to dump stack space, besides the old binutils works ok it seems. Runtime builds and works ok so far but havent got to reimplementing the msys mount system yet because of some rather hefty code changes (tbh im a bit afraid of breaking it so someone who has been closer to the inneries of the msys runtime should probably take over that part). Besides that i fixed up uname to return the correct MSYSTEM name allthough the added 64 bit check chops of the 4 from WOW64 but it does the same on cygwins it seems so its not something i broke atleast. Still in progress of manipulating the makefiles to accept the msys structure with some succes. Only tools not building are cygcheck and cygserver + cyglsa, but that seems related to my broken gcc as they bitch about missing stdc++ functions. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObSOiAAoJEIjGvG7Y4HU8PVAH/iUmxk51VyEpK0kfhw3jRtbh D8nS9E7gV9pb1mNAEA59q6MngxRJUoMeL0hI8OBmhTXBCHxU2MRmU6kRQNEaodhD OjImAH7tAriYkzZ955bDE7q+55F5wMamOevtXOGz3Kw5U8thx0MfJhC2tACrvnCm Bk3AbN1MKQ11cJk+hHz80JPTrse03LJQ31ximJDO20zJGAC+JHaCQHg9a57woJGZ 6Z/OkzLan5bSVHV2giOfzbRGQrS0TVaks/D7QizA6K5KsG+sObS2Ih+3+ijbPE0o PYQ9lvqXPA+23fhb3a5zXro3Jn7pi42+pWwLQhaS0Kttx1ubBAQ++BESjgtn26M= =eS++ -----END PGP SIGNATURE----- |
From: Teemu N. <sti...@ya...> - 2011-09-11 21:49:13
|
On 12.9.2011 0:09, Ralph Engels wrote: > Building a new version of gcc now actually. I stayed with the old > binutils package for now because the broken gcc i used before caused > the new binutils to dump stack space, besides the old binutils works > ok it seems. > Runtime builds and works ok so far but havent got to reimplementing > the msys mount system yet because of some rather hefty code changes > (tbh im a bit afraid of breaking it so someone who has been closer to > the inneries of the msys runtime should probably take over that part). > Besides that i fixed up uname to return the correct MSYSTEM name > allthough the added 64 bit check chops of the 4 from WOW64 but it does > the same on cygwins it seems so its not something i broke atleast. > Still in progress of manipulating the makefiles to accept the msys > structure with some succes. Only tools not building are cygcheck and > cygserver + cyglsa, but that seems related to my broken gcc as they > bitch about > missing stdc++ functions. Could you post diffs as well? |
From: Ralph E. <ral...@gm...> - 2011-09-11 23:19:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 patch for gcc-4.3.4 was attached but needs admin approval, i guess it should be availiable later. Gcc built but not without some trouble. Seems a few flags dont get propagated correctly to auto-host.h so i added the buggers to CFLAGS etc. build commandline here if you want to give it a go. It builds with the old 3.4.4 with this. CFLAGS="-I/usr/include -I/usr/include/w32api -O2 -g -pipe - -funroll-loops -DHAVE_CLOCK_T -DHAVE_STRUCT_TMS - -DENABLE_DECIMAL_FLOAT=0 -DENABLE_DECIMAL_BID_FORMAT=0" CXXFLAGS="-I/usr/include -I/usr/include/w32api -O2 -g -pipe - -funroll-loops -DHAVE_CLOCK_T -DHAVE_STRUCT_TMS - -DENABLE_DECIMAL_FLOAT=0 -DENABLE_DECIMAL_BID_FORMAT=0" Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObUJGAAoJEIjGvG7Y4HU8kgoIAJ7s4JUt/N2ZjcU/hQb92m1Q cDfB+r8xRB2BTugvJSdw/DlhkwuSCPplPR5hwwlLvxEOyRt+kxv8cXyZECUNp9qW s1FUL/HXq9XRtUv20sgipzFu5TLstiqqXJk8iLVxmYBwAxQKE0FMocS0j+5eg1vc VqcPvtFDpR1WS9L7WYinFobQ2MzIIFsRj1YDahx195epc8elMtmhhH+8Dti04jkB QM/1GGwl1UAiQkskETQk4wfzETBJNPM459fwj3DCAtS7pNclbw/O5NpNSvkzzLRA NGeLqOz+25yJvAVmbQ1vRQVrkDteKH/J/Cjr8F4Ho20Kz1XUEFkJegzIQeD29F8= =EOLS -----END PGP SIGNATURE----- |
From: Ralph E. <ral...@gm...> - 2011-09-12 10:01:10
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok finally found the culprit. I had C_INCLUDE_FLAGS set to a tool in /opt which was overwriting gcc vars. Built binutils 2.21.51 to go with gcc-4.3.4. they wont work for the old runtime unfortunatly. AFter removing the above everything just started working so finally some progress where i can look at code instead of env vars. Strace now builts and also cygwin_console_helper. I use the External MinGW compiler for this. Still need to fix cygserver and cygcheck but i have a feeling it will get a bit easier now that the compiler actually works. If you like i can upload the runtime + binutils + gcc and sources to my site so you can try them yourself. If youre used to cygwin it should be easy enough using it. I also got coreutils 8.10 compiled for it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObdijAAoJEIjGvG7Y4HU88NwIAKLkXGniiNnZJlPKMYFn5tFg cFP5IiuNQMBorPT57fwWTiqV1N1Y0ZoLaF571V6EBMHk3XrMdLlPYfpSkk7pM5fv USa+Cg6PuKR5NPxNC+M3LjP6EF/oEoUGQThUXIO8M8EfJofgBjPgH79/uDp0jtu0 30awPxjMlv1bpP4+qPq8HIKq1rAjuu6GeUNO5FPsNByvF5V6yOX8tha+DnX+aHVO d36R33QevgYeF44fvq621pQgw0yCMuxcvGL6k3CrrqiRnz/yQqHAF1ZSZhz1Eb9Z Nmk8BlWK2AWCL+qEbYWidq0yT2egIo5Xy2xFykAVvH4fJkhk63Pg2HSeBCMulD8= =Mwxm -----END PGP SIGNATURE----- |
From: Teemu N. <sti...@ya...> - 2011-09-12 10:07:06
|
On 12.9.2011 13:02, Ralph Engels wrote: > actually works. If you like i can upload the runtime + binutils + gcc > and sources to my site so you can try them yourself. If youre used to > cygwin it should be easy enough using it. I also got coreutils 8.10 > compiled for it. Please upload everything (binaries + sources). |
From: Ralph E. <ral...@gm...> - 2011-09-12 10:09:39
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 12-09-2011 12:07, Teemu Nätkinniemi skrev: > On 12.9.2011 13:02, Ralph Engels wrote: > >> actually works. If you like i can upload the runtime + binutils + >> gcc and sources to my site so you can try them yourself. If youre >> used to cygwin it should be easy enough using it. I also got >> coreutils 8.10 compiled for it. > > Please upload everything (binaries + sources). > > ------------------------------------------------------------------------------ > > Doing More with Less: The Next Generation Virtual Desktop > What are the key obstacles that have prevented many mid-market > businesses from deploying virtual desktops? How do > next-generation virtual desktops provide companies an > easier-to-deploy, easier-to-manage and more affordable virtual > desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > _______________________________________________ Mingw-msys mailing > list Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys Ok will pack it up and drop some links in a short while :). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObdq4AAoJEIjGvG7Y4HU870AH/3bJmVGgxXrYEWjxBbUijzOz OI0W+7byIm0IDxZB1rJ+6/JkdCsphzc+RIBlAtaF7MBiCIImfZivGuTYszUVzRTy xteIHCQI5+2gkZ5yCsHXf7Ais6LbUalEeZ7vOFeXZ30INh2OdZa7D0cwlT6vGzXR WxFiymAxUEmDl6GOW91s1s+eLiTD/zz+9zGAnck1ODCSAME2nXMI+bafFUuEv/ex JHQmqljAin236dteJ+tYISOa2uUppAkYy7nkZb2hDC/Tcjjkmhkz4PcOMQBGt2kh W+vnB6M3QEHyS3O95KoPeG1uhsj9SiHrXhI+IsGRuk1reqxdjIKG/0shiCQhclk= =Gstf -----END PGP SIGNATURE----- |
From: Ralph E. <ral...@gm...> - 2011-09-12 10:44:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 12-09-2011 12:07, Teemu Nätkinniemi skrev: > On 12.9.2011 13:02, Ralph Engels wrote: > >> actually works. If you like i can upload the runtime + binutils + >> gcc and sources to my site so you can try them yourself. If youre >> used to cygwin it should be easy enough using it. I also got >> coreutils 8.10 compiled for it. > > Please upload everything (binaries + sources). > > ------------------------------------------------------------------------------ > > Doing More with Less: The Next Generation Virtual Desktop > What are the key obstacles that have prevented many mid-market > businesses from deploying virtual desktops? How do > next-generation virtual desktops provide companies an > easier-to-deploy, easier-to-manage and more affordable virtual > desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > _______________________________________________ Mingw-msys mailing > list Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys Ok heres the compiled runtime + coreutils/binutils and dependencies. http://sourceforge.net/projects/cbadvanced/files/Tools/Msys2-runtime%2Butils.7z/download Gcc and Source shortly. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJObeL+AAoJEIjGvG7Y4HU8+UEH/0KbUJUn7PRNzllYH6Afk1Zp NIkDU4MiNyd5cH3EVyObVrXjO9TxwCYvPo0rbcwWIA5zb7SzNVZLvW5wrv579X4M m3iFLftX/5bm3Qv17FhXzhsQCWknCn5zKTw4L/0aksaHaBgFELWDODrot1QQuiao FhI+z+40soLWCmD69VOgKWYQuJmLan2GSBd4/iDyKaYJ7iNCVZUc3PeQwV2o5TPn xyY8BJWKRDoQ8QhH0z6DK8B0SeTf2S+bkCKslXc01ixzstg9ZrhL46nb3p4PTHEJ txxsWGLlPYhoqVXcC+d19itsrQJ5aNSt9nQwCuJxurM2447SWwlFy9Fcn9BFe4s= =Earw -----END PGP SIGNATURE----- |
From: Teemu N. <sti...@ya...> - 2011-09-12 14:29:25
|
On 12.9.2011 13:46, Ralph Engels wrote: > Ok heres the compiled runtime + coreutils/binutils and dependencies. > > http://sourceforge.net/projects/cbadvanced/files/Tools/Msys2-runtime%2Butils.7z/download Everything seems to be working without crashing. I am trying to compile GCC 4.3.4 natively just to see if it can be done. One problem: at the moment MSYS2 is as slow as Cygwin is which in my mind makes it unusable. |
From: Charles W. <cwi...@us...> - 2011-09-12 15:40:32
|
On 9/12/2011 10:29 AM, Teemu Nätkinniemi wrote: > Everything seems to be working without crashing. I am trying to compile > GCC 4.3.4 natively just to see if it can be done. One problem: at the > moment MSYS2 is as slow as Cygwin is which in my mind makes it unusable. Guys, TANSTAAFL. You can't get something for nothing: cygwin-1.7 (and 1.5, before it) adds a LOT more posix compatibility functionality and new features -- like unicode support -- than older versions. MSYS-1.0 is only SLIGHTLY faster than cygwin *of its day* -- e.g. 1.3.4 -- and that is only because msys skipped a lot of the permission checking and user/access emulation stuff that cygwin did. Cygwin has become more processor hungry to support the new features. The same will be true of msys-2: it will be only slightly faster than the cygwin it is based on, and only if you short-circuit a lot of the permission/access handling. -- Chuck |
From: Teemu N. <sti...@ya...> - 2011-09-12 16:01:29
|
On 12.9.2011 18:40, Charles Wilson wrote: > On 9/12/2011 10:29 AM, Teemu Nätkinniemi wrote: > >> Everything seems to be working without crashing. I am trying to compile >> GCC 4.3.4 natively just to see if it can be done. One problem: at the >> moment MSYS2 is as slow as Cygwin is which in my mind makes it unusable. > > Guys, TANSTAAFL. You can't get something for nothing: cygwin-1.7 (and > 1.5, before it) adds a LOT more posix compatibility functionality and > new features -- like unicode support -- than older versions. MSYS-1.0 > is only SLIGHTLY faster than cygwin *of its day* -- e.g. 1.3.4 -- and > that is only because msys skipped a lot of the permission checking and > user/access emulation stuff that cygwin did. > > Cygwin has become more processor hungry to support the new features. The > same will be true of msys-2: it will be only slightly faster than the > cygwin it is based on, and only if you short-circuit a lot of the > permission/access handling. This has been the exact reason I've started patching MSYS from the beginning and the ultimate goal being getting better support for threading and unicode. I still like the idea of MSYS2 if only to get to know Cygwin better and to see if there is any way to speed up MSYS2 when compared to Cygwin. |
From: Vincent T. <vt...@un...> - 2011-09-12 16:06:55
|
On Mon, 12 Sep 2011, Teemu Nätkinniemi wrote: > On 12.9.2011 18:40, Charles Wilson wrote: >> On 9/12/2011 10:29 AM, Teemu Nätkinniemi wrote: >> >>> Everything seems to be working without crashing. I am trying to compile >>> GCC 4.3.4 natively just to see if it can be done. One problem: at the >>> moment MSYS2 is as slow as Cygwin is which in my mind makes it unusable. >> >> Guys, TANSTAAFL. You can't get something for nothing: cygwin-1.7 (and >> 1.5, before it) adds a LOT more posix compatibility functionality and >> new features -- like unicode support -- than older versions. MSYS-1.0 >> is only SLIGHTLY faster than cygwin *of its day* -- e.g. 1.3.4 -- and >> that is only because msys skipped a lot of the permission checking and >> user/access emulation stuff that cygwin did. >> >> Cygwin has become more processor hungry to support the new features. The >> same will be true of msys-2: it will be only slightly faster than the >> cygwin it is based on, and only if you short-circuit a lot of the >> permission/access handling. > > This has been the exact reason I've started patching MSYS from the > beginning and the ultimate goal being getting better support for > threading and unicode. I still like the idea of MSYS2 if only to get to > know Cygwin better and to see if there is any way to speed up MSYS2 when > compared to Cygwin. i would just like an msys2 faster for configure scripts than msys 1. Configuring gettext, gnutls, etc... are too long with msys1. If msys 2 is not faster than msys 1, i don't see the benefits of msys 2 for me. Vincent |
From: Ralph E. <ral...@gm...> - 2011-09-15 11:30:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey Teemu. Just a small question i hope you can help me with. Its allmost there but im banging my head on getting MinGW to work with it. I checked the original patch to find out how it was initially done getting cygwin to accept using the mingw compiler externally, but besides bugfixes the only code part i can see makes a difference is the msys_p2w function. A rather big part of the code that it changes was modified so im a bit scared of trying to add the function because i dont want to break it (not while im not sure its the part that makes it tick). MinGW gcc reports no input no matter what i mount it as (even unmounted from inside the Msys2 /usr dir) so for MinGW development its broken :/. Im not sure who did the initial port (charles wilson ?) but i need to get a hold on whoever so we can work this last part out. Best Wishes. Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOceIVAAoJEIjGvG7Y4HU8qLAH/jvPXX6Fgk3qDRjwM34izRcR gJ3Cwm7IBaj7vzWlCosJlmuLHcA+SZ8CglvB9YDyTXrivPZjV/iPP1R518pNhbgS uli0rjCzBeNuqyU751S6v1ARbcsHicdpZf2OKB6xjoQRfxjXuwxGxylK5WqIlW0l PerYblkHrMPY4HQ6MNysilHDzW84Gm7y+5/E1qaPI/6+mJ27iJTuLR7ntGjf+lDF onk9RUj1/Ia5B3yE4RqiR1XtQyEIZ6ocsoEP58Ycc2827pq66+Bx12sCtmMExKuk LgLnjhCzRjN58EVqRtPOXuVrKwrRkUx+uhJ65q+bs5J62bGrU8EXrdtKti2pRVQ= =pMOx -----END PGP SIGNATURE----- |
From: Rinrin <ri...@im...> - 2011-09-16 09:11:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 于 2011/9/16 4:37, Ralph Engels 写道: > Got hold on Earnie and things might resolve shortly :) with some > luck it will be added to the mingw-msys work tree. I have a bad > habit of being unclear of my intents if it was a bit unclear im > sorry. The work i have uploaded is for skipping the crosscompiling > phase making it possible for the developers to start right away > with the nessesary changes instead of having to use linux or cygwin > for the initial port. So in short to save some work :). > > And thanks for your help its appreciated. > > Ralph Hi Ralph: after review msys-1.7.9.patch from your sf site I have some comments 1) Changelog should not be patched by replacing cygwin to msys, it will break history tracking. 2) I suggest to add hostname or osname like MSYS* or i?86*-*-msys* but not delete cygwin defs in m4 scripts. for example: [snip] diff -Naurd source.orig/config/dfp.m4 source/config/dfp.m4 - --- source.orig/config/dfp.m4 2010-10-02 16:42:48 +0200 +++ source/config/dfp.m4 2011-09-08 07:37:11 +0200 @@ -22,7 +22,7 @@ case $1 in powerpc*-*-linux* | i?86*-*-linux* | x86_64*-*-linux* | s390*-*-linux* | \ i?86*-*-mingw* | x86_64*-*-mingw* | \ - - i?86*-*-cygwin*) + i?86*-*-cygwin* | i?86*-*-msys*) enable_decimal_float=yes ;; *) [/snip] 3) config.guess, config.path, libtool.m4,ltoptions.m4, configure could not be included in the patch, it will be replaced after running libtoolize/autoconf 4) maybe it's not necessary for replace macro __CYGWIN__ to __MSYS__, AFAIK, msys-gcc has been add builtin macro __CYGWIN__ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOcxK8AAoJEIopQjIpgMdEOoUH/iSKe6lGxCZgiCM4EYynQXnN eCfWXvIjkIc+HXjAy5IaPQH8x0lv6O6wedFuuYJw3KruEvnTHk2HhQwwBQIA4KCl 5UtkGPN3bV/OIbgcsAEozRNll/SiGChnn/1X42/eSnNdJH+cDEA0uT0/OxbbaW2A wXsFPp8Pp2ohnM6p5xKCT4NKclhXE3uncqW/pUoy+NYzL8zdhdApPHev5Dlsya3s f9ZreD6uvtYDXtgAuWShxlf1jePRytzEpaRsGpcJxB7O1Bcfv0Z7E7BL3Fu1UBgG oI0ymyJI8ejd0LyxCrBblIr6ZVWIf+45zBGCeV3qXq3+8Dqw09AdDwLd05jQqPc= =beFd -----END PGP SIGNATURE----- |
From: Ralph E. <ral...@gm...> - 2011-09-16 09:35:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Den 16-09-2011 11:11, Rinrin skrev: > 于 2011/9/16 4:37, Ralph Engels 写道: >> Got hold on Earnie and things might resolve shortly :) with some >> luck it will be added to the mingw-msys work tree. I have a bad >> habit of being unclear of my intents if it was a bit unclear im >> sorry. The work i have uploaded is for skipping the >> crosscompiling phase making it possible for the developers to >> start right away with the nessesary changes instead of having to >> use linux or cygwin for the initial port. So in short to save >> some work :). > >> And thanks for your help its appreciated. > >> Ralph > Hi Ralph: after review msys-1.7.9.patch from your sf site I have > some comments 1) Changelog should not be patched by replacing > cygwin to msys, it will break history tracking. 2) I suggest to add > hostname or osname like MSYS* or i?86*-*-msys* but not delete > cygwin defs in m4 scripts. for example: [snip] diff -Naurd > source.orig/config/dfp.m4 source/config/dfp.m4 --- > source.orig/config/dfp.m4 2010-10-02 16:42:48 +0200 +++ > source/config/dfp.m4 2011-09-08 07:37:11 +0200 @@ -22,7 +22,7 @@ > case $1 in powerpc*-*-linux* | i?86*-*-linux* | x86_64*-*-linux* | > s390*-*-linux* | \ i?86*-*-mingw* | x86_64*-*-mingw* | \ - > i?86*-*-cygwin*) + i?86*-*-cygwin* | i?86*-*-msys*) > enable_decimal_float=yes ;; *) [/snip] > > 3) config.guess, config.path, libtool.m4,ltoptions.m4, configure > could not be included in the patch, it will be replaced after > running libtoolize/autoconf > > 4) maybe it's not necessary for replace macro __CYGWIN__ to > __MSYS__, AFAIK, msys-gcc has been add builtin macro __CYGWIN__ > > ------------------------------------------------------------------------------ > > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > http://p.sf.net/sfu/rim-devcon-copy2 > _______________________________________________ Mingw-msys mailing > list Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys I think i might have replaced those by mistake when i did a regex search and replace for occurences of cygwin. Ill copy back the original changelogs. And ill take your advise :) it was actually on my planner but i concentrated on getting it working first. Thanks for the head up. Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOcxi/AAoJEIjGvG7Y4HU8Dv4IAIlqH49ghF+nxLsNBex1W8e4 ITn3hfmUn5h7bL6AHf0wvI5R0F0klatm945powjhXLO/m4FbEKwbsUaONV0r+S78 aoUWQM7nMsSi2coiwCxGCr5o+SmcpNBvZmu/75GzVyT2pSehG0cNVQMtqLVq/JIB /B/OO9tLhnApsn9+jtd5VJa3EIsy91KfEsIFz7e/PKzg80gTG/gIIFJuaAgdgbGn aG6HdocYEcmBAaGevhVdZrGiut0OqxQtCP7Kjj1D+XjK/VEsT7VpjjtzHnlCbdrf 6QmQtGYbFneaGcjYgfT/5fHFKyCXLd85O3LAZ5B8+wnVrpmUN/ERDT+I/Ce6Q0c= =k0O1 -----END PGP SIGNATURE----- |
From: Ralph E. <ral...@gm...> - 2011-09-17 17:41:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I added whats still missing (msys_p2w etc.) to the readme on my site, and left a pointer on how to compile it on windows. Also started backporting the accidental changes to changelogs etc. Im taking a few days of work as im completely exhausted (im not the youngest fellow around anymore). The initial work (how ever small it was) took me several days without sleep, and with normal work on the side it took quite a toll on me, so im going to be on the backburner for some days while i recover. Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOdNwFAAoJEIjGvG7Y4HU8xqMIAIQh5YffGlZ0TUnMxlGEpbCV Ayc5WF9MIERpr9mcV4HCzrquQG+cvEPfEeVQD1CQpO3kFdcnzTeDCjFfjFGUYe8L F/Yf2/ml6eSXo4AvXB5EuUVkC7lcrtaqS8EoWAl15HgGKFK4keu9NWxMdgetGuI8 qjvJQfZ3IFxdpIC4dR6/+Yr+wcyoTLByYuI9UESjo6Q7I7dXpFUYPyaTh5eSKTfo Os4tPjmU7yrhKHWWX99LYo0hvCC9qMe/hZPruWCkjYkdUHwMAdXsj94v+MnXJlDM 3XqeKW29Milqlrir3wCIkWUJcVgguesrYNH+zEE0YLjhZf70EGPCatAhrm2MtRk= =FDcR -----END PGP SIGNATURE----- |
From: Charles W. <cwi...@us...> - 2011-09-26 17:29:07
|
On 9/25/2011 4:39 AM, Rinrin wrote: > Hi all: I have been doing an initial work on cygwin which supports > msys-like path conversion. just do a little testing but when using > mingw/mingw-w64 gcc to compile native program it works. Some parts > of msys changes were not ported, like /etc/fstab support( new > cygwin support it). And here was not take care of symlinks(seems > that cygwin have been deal with it) Please review and give me some > advices, thanks. https://github.com/rinrin-/cygwin-alternative How does this differ from Ralph Engels' ongoing work for an msys v2.0? Are you attempting to create a third project distinct from both msys and cygwin? If not, and you're also doing a proto-msys-2.0 implementation based on modern cygwin, why can't you work with Ralph? Why a separate project? I'm okay with competition; odds are we'd end up taking bits of each for the "official" msys-$next. I just want to understand the goals and motivation of your project, as compared to Ralph's. -- Chuck |
From: Rinrin <ri...@im...> - 2011-09-27 01:17:00
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 于 2011/9/27 1:29, Charles Wilson 写道: > How does this differ from Ralph Engels' ongoing work for an msys > v2.0? Are you attempting to create a third project distinct from > both msys and cygwin? If not, and you're also doing a > proto-msys-2.0 implementation based on modern cygwin, why can't you > work with Ralph? Why a separate project? > > I'm okay with competition; odds are we'd end up taking bits of > each for the "official" msys-$next. I just want to understand the > goals and motivation of your project, as compared to Ralph's. > This is just another try of msys-method from the different direction. I'm willing to keep the modification as small as possible, then it can be easily merged into future cygwin releases and take advantage of the new features. I'm not sure why the msys 1.0 used a new system triplet(i686-pc-msys), and Earnie is not willing to add this triplet to the upstream. But this odd triplet brings some additional works isn't it? I like to keep it as same as cygwin. Because of modifications are small enough, It will be very easy to integrate into Ralph's project. There is no repeat work between them. Currently I'm considering how to deal with symbolic links in msys2. modern cygwin has the ability of reading native symbolic links but due to some posix incompatible reason it will not create them. IMO I have 3 choices: 1. disable symlinks support like msys1 2. support native symlinks creation by merging a patch made for msys. but why it's not posix compatible? I have been search cygwin mail list but not get the answer. 3. support native symlinks creation by a ln script wrapper but disable it in the core. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOgSP+AAoJEIopQjIpgMdEpecIAJlv+ge1ujIYBmg1gI4cvJBI tXs9GoArY4WGVOUhYz/hpNqTFUr7p2VjK6KcQ8e3mfb9IDOn0+YoKz/tK2HjB0CJ zjbG2WeAd6bBlYfRhUG63BrvJqC7uHkQkjwaeIzmeT+J2tKYg1s23Txx015lNQNF HjmUHufofo/NHGFZgrNLZAeT0oxhnLyOE3yANBVqSyP4abbbtZMYkb0F8vt3QVDg n+e41NnZ9xw7OJ1Rm2z7CXFf+hQwJ6TbLDNs34GhGHdGoCMTGgfteZnezLLXZwwK nBldHrT9zmqIHEwATGiMFFjwjRXc0+YG7Z0MKzSoDmq2bLScnmfXARp1U5ogTEE= =m+5w -----END PGP SIGNATURE----- |
From: Ralph E. <ral...@gm...> - 2011-09-26 19:22:22
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Feel free to integrate the two if it's any help :) I been on the backburner for a while because i needed a break, so not much new to report yet. Also Earnie was pretty tight for time atm but else i think he would pitch in helping on the remaining changes. A merge would definatly be easier for all implied to work on. Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOgNFOAAoJEIjGvG7Y4HU8lPAH/iTdEAhNd/MW/4mJflKgI2vP AKzub70B8Z8wHIsVKftij3XdeocSqqaRkhm0oOS0uzZqRW/sdwqPmqScxNnxKHkm V5RUvpWtAeRcQxBZxABf1Vw/5jTVSX3WI2C4LBhSgnBMi4f5Y6BAWl3JF7D1Ba1k pTPx4VLRTzpgiwV9QjlNEF69Xogckc6lT1n9MUCQ387Gnmz0bKYLf6fTxOlhbXb0 bDhj+FK/AyIyy9axb0BtR3CqgkSFMp2b+88fyDOckbi49wOR4Qf71epVexVpg42L iGs8nAzIhe5cKLjIFH/emAzmhJIt2+c6e1Q5gjZYFHMvQKS3V4uUey8gLD7r9oQ= =G/uJ -----END PGP SIGNATURE----- |
From: Charles W. <cwi...@us...> - 2011-09-27 07:21:00
|
On 9/27/2011 2:26 AM, Ralph Engels wrote: > As for native symlinks id propose to keep them as they do come in > handy, but support for older OS such as win9x would not be able to > use this advantage, but i hope noone uses these for anything > besides retro gaming boxes theses days anyway :). MSYS no longer supports Win9x (it uses some functions available only on W2k+ IIRC) so that's not really an issue. The real issue is that (1) native symlinks don't really work exactly like posix symlinks, (2) they are only supported on NTFS filesystems, not FAT -- and some 2k/xp systems still use FAT, and (3) IIRC you have to have Administrator privilege to create native symlinks. Since there are /so many cases/ where native symlinks just won't work, it seems that it would be better to train developers to avoid them whenever possible, when porting to mingw/msys rather than to half-way kinda-maybe support them sometimes. -- Chuck |