MinGW - Minimalist GNU for Windows

On 9/7/2011 3:30 PM, Ralph Engels wrote:
> Been hammering for some time on an updated Msys Core based on cygwin
> 1.5.

If you check the mailing list archives in the last year (mingw-dvlpr and
mingw-users) you'll see that some discussion about "MSYS 2" has occurred
-- but along these lines:

"hey, the cygwin folks implemented self-install-location-detection, the
ability for multiple 'cygwins' to coexist, and /etc/fstab support.
Since that was one of the most intrusive changes made to create msys
from cygwin-1.3.4, I bet it would be a LOT easier to recreate msys now,
using modern cygwin as a base"

But, in this context, "modern" means "cygwin-1.7+" -- not 1.5.x

Basically, the major abi breaking "improvement" you get from 1.5.x is
support for large files (>4GB), and the normal set of assorted bugfixes
and minor improvements.

However, with cygwin-1.7 you get unicode/i18n support, and extremely
long pathname support (32KB, rather than 260 chars) [since, internally,
cygwin-1.7 now uses the *W() w32api functions exclusively].  I've
actually hit that smaller limit compiling java code...

So...while I appreciate the work you've put into msys-cygwin-1.5, I'd
suggest perusing those old mailing list discussions, and using what you
have learned so far to accelerate a reimplementation of msys based on
cygwin-1.7.9 or cvs HEAD.

--
Chuck

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok ill see if i can port Cygwin 1.7.
I came as far as getting 1.5 to compile with the old Msys but 1.7
would probably need cygwin for the initial boot i guess.
Is there a place to get the changes to the Msys core ? i did my work
by sifting through the source and consulting the Msys Changes doc but
its rather timeconsuming.

Best Wishes.

Ralph Engels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaE/6AAoJEIjGvG7Y4HU8y2MH/0CSc7hL+5JZOYmbtNhoBEA4
swQIqthWksEIWVhD0f1tUrcFPPjBtsw8lqTGCEpZTqzPiA1viC6aA2x6rQXkbhfr
Phl/RiwG0YBXRykDCN9mXCLLqbFwYhoCihE/ZoH9Wv6j+PKX9xhHiYvcYREchHRj
DHLfb5+sYieXpLNn8WFYAYRt9doFXhLz26lZVhtQQ31z6n1EK0oNbMUeIHvlaI0l
hCYQdGzEjX6g7xykrPQAzI1W0oMMmoL7H8wGGcbBuaaWM6IA7YVC1WZFEPj9xR6X
W9ANT9AFd1Umx718mL4O5Ayw8saTwq4O19kkSORGygVQXJGSrmUINdWvuYwPygY=
=ZS+h
-----END PGP SIGNATURE-----

On 8.9.2011 8:17, Ralph Engels wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ok ill see if i can port Cygwin 1.7.
> I came as far as getting 1.5 to compile with the old Msys but 1.7
> would probably need cygwin for the initial boot i guess.
> Is there a place to get the changes to the Msys core ? i did my work
> by sifting through the source and consulting the Msys Changes doc but
> its rather timeconsuming.

This is the diff between Cygwin 1.3.3 and Msys 1.0.17:

http://teemun.x10.mx/cygwin133-msys1017.diff.gz

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 08-09-2011 07:19, Teemu Nätkinniemi skrev:
> On 8.9.2011 8:17, Ralph Engels wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Ok ill see if i can port Cygwin 1.7. I came as far as getting 1.5
>> to compile with the old Msys but 1.7 would probably need cygwin
>> for the initial boot i guess. Is there a place to get the changes
>> to the Msys core ? i did my work by sifting through the source
>> and consulting the Msys Changes doc but its rather
>> timeconsuming.
> 
> This is the diff between Cygwin 1.3.3 and Msys 1.0.17:
> 
> http://teemun.x10.mx/cygwin133-msys1017.diff.gz
> 
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Thank you. That will make it a bit easier :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaFj/AAoJEIjGvG7Y4HU8u60H/1vTo6YvTbWTpBCIWLFBrUgl
TP4ycseFL/d67FYJ4/2mLZDUXoPy9pMlfj1fiMWjHhUkPWtcJFt5mxsJ+s1sQ26H
J2pv627eMMTFysWYf5UYWAbBGlZYkjGf2LK3jikLnfu2/xLF1a8qm+IxfeRZU1Qp
igXKwMffxLsi0hRQu8nVmxoQrqHcYGWoCTmt9ajhNO5lBzEd1SoUI/1WKKBcBeBH
4kHHXp2UH6p/fs+ehSpjZYqGiP0G69829kj5aVC6CT5uztN26AfYVItN6WiAn5bb
AzmWSD8+zkpFg5lYizdUIbqE8hGkwBtYQ+qMTBuMjqB4KYHQqtzea6Aeq2SUTRk=
=EmgJ
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Ok dll is build and i can start bash but theres some rather hefty
changes in path.cc and mount.cc in regards to cygdrive
the change from CYGWIN_INFO_CYGDRIVE_DEFAULT_PREFIX "/cygdrive" to "/"
makes it unable to chdir and looking closer i noticed its allready set
to "/" in mount.cc. Guess ill have to hack about some more to get it
to accept msys paths. Only complaint from bash atm is /tmp does not
exist please create so something is up.
I skipped the AbsDllPath etc from msys.cc as it seems cygwin allready
had something similar. I wonder if any tools actually use these
exports ? or are they just for internal use.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaJUOAAoJEIjGvG7Y4HU8zYMIALNycgOi5xIfdTegi24qFvCg
6FcZQurFd2mBNBxLoL7A0IDI3iajIf/14B6ezOu0oamDEXoU/Hj7tCNt+/TgY25l
p5PUOi8Abaa44a9xGAqkK/IJZvpcHnHazGP64CuqxkQffu9Jv+XIU1IH0CzF7BeK
UuDJqEaYqZF8xzZXbvV6WU/r4+nYhtYtJRzcZneI4Q2ARnYkb4xJykL3AgHonyJe
12XWwBXS4/D24HnZmoUNVVkem0j6AMmliNp3jv2DUZFYTIeuHpTLxCu43/EsnQYR
1wt2Rs1N47tXz/eogFbBpLMJbqSI4vH1cDvaYi+5aQmIG1GWQI8KLmrvoy8C4Sk=
=K11v
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 08-09-2011 07:19, Teemu Nätkinniemi skrev:
> On 8.9.2011 8:17, Ralph Engels wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Ok ill see if i can port Cygwin 1.7. I came as far as getting 1.5
>> to compile with the old Msys but 1.7 would probably need cygwin
>> for the initial boot i guess. Is there a place to get the changes
>> to the Msys core ? i did my work by sifting through the source
>> and consulting the Msys Changes doc but its rather
>> timeconsuming.
> 
> This is the diff between Cygwin 1.3.3 and Msys 1.0.17:
> 
> http://teemun.x10.mx/cygwin133-msys1017.diff.gz
> 
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys

Well i be damned that diff helped a lot initial working version
allready done using cygwin now recompiling it with the new Msys
version :) lets hope it goes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaLe9AAoJEIjGvG7Y4HU837EIAIOGCGGkB+J+9U2WhSfY7xzd
hSYsZmFWxIl9RaKsVIagBj862Q4vQoUmtxAjf8G5gMh3605KGDTe0cV7bwWqbvoW
fvC+RudNxtP53K/ttl06m33VqkXPLz+xNIVsuXwCrPCfbsEe6+N99n9+W81hJd2Q
HVQfpdwLNXy1xdt6CSwNHkZU72gY7QHspDHN5qyLXdJGjC5+oarB9xvDQwcWcgj1
ATqJ3KbU5+zBrF0ImWoYDPsECwQ2Wrllk/MIb+501RN/l5Z9q6t4xSjj3J+S88Hh
z3vmGYgF0rPxPB1cG/NoD6D+rwCAnFSAlY4gwqczR0WDQuLK42v1OPm6irNjpEE=
=nTYq
-----END PGP SIGNATURE-----

On 9/8/2011 8:40 AM, Ralph Engels wrote:
> Well i be damned that diff helped a lot initial working version 
> allready done using cygwin now recompiling it with the new Msys 
> version :) lets hope it goes.

PLEASE take my advice, and search for the earlier discussions of this.
Not all of the "stuff" in that patch needs to be (re)implemented in a
new msys - since the underlying cygwin now supports it directly. Also,
some of the compromises we made to support Win9x are no longer
necessary, since (as of MSYS-1.0.17) msys no longer supports 9x anyway.

-- 
Chuck

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 08-09-2011 15:29, Charles Wilson skrev:
> On 9/8/2011 8:40 AM, Ralph Engels wrote:
>> Well i be damned that diff helped a lot initial working version 
>> allready done using cygwin now recompiling it with the new Msys 
>> version :) lets hope it goes.
> 
> PLEASE take my advice, and search for the earlier discussions of
> this. Not all of the "stuff" in that patch needs to be
> (re)implemented in a new msys - since the underlying cygwin now
> supports it directly. Also, some of the compromises we made to
> support Win9x are no longer necessary, since (as of MSYS-1.0.17)
> msys no longer supports 9x anyway.
> 
Aye i figured as much after checking the source so i took great care.
Actually i can report a complete succes it works :) i started
rebuilding newer binutils and gcc for it since the old 3.4.4 gcc seems
to break with some of the new stuff in 1.7.
Ill make a system builder availiable once i got enough tools going on it.

Regards Ralph Engels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaOgYAAoJEIjGvG7Y4HU8D/4H/2P0tqWJGaNi5XxQVKjh8GsN
3MV5ENZdlqh5AbWYM0XT/nJkp2aB1kneyvcyzjYAFcMSsJ6LiGZO9sPZSqeEIFqb
NjF4MLoqn8kzqWjylwAT7AXnTFU9ZUHF3TQ1UY9kj9F04XDUxCMMadFlGLEMoYWa
pkT4NMLezBRn4giO0SJ/6JSxkmbGtMjtAsKNRh8JJIyRyTf3ELAN/SleK0zTuml7
16QMWVMiy9gzQtVZ7JcY6dLYyZX76kn1FGXrW28JWeBg9BglFEEfKS92D82fTspM
jo926UWSOitQASTBjU8Lj+hLHPO4I/FBPVtiK6A9NnGcnWib6umF9822gucLN7o=
=rfLZ
-----END PGP SIGNATURE-----

On 8.9.2011 19:06, Ralph Engels wrote:

> Actually i can report a complete succes it works :) i started
> rebuilding newer binutils and gcc for it since the old 3.4.4 gcc seems
> to break with some of the new stuff in 1.7.
> Ill make a system builder availiable once i got enough tools going on it.

I think Cygwin 1.7 needs GCC 4.X to compile. Please share your patches 
and sources as soon as you can.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 08-09-2011 21:01, Teemu Nätkinniemi skrev:
> On 8.9.2011 19:06, Ralph Engels wrote:
> 
>> Actually i can report a complete succes it works :) i started 
>> rebuilding newer binutils and gcc for it since the old 3.4.4 gcc
>> seems to break with some of the new stuff in 1.7. Ill make a
>> system builder availiable once i got enough tools going on it.
> 
> I think Cygwin 1.7 needs GCC 4.X to compile. Please share your
> patches and sources as soon as you can.
> 
> 
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Still a few oddities that needs to be ironed out but ill make a
patchset of the current work.

The makefiles need a workover btw since it installs things like it was
a cygwin tree. Also you are correct about it needing a newer gcc i
tried with Msys gcc and it failed. So im trying to compile a newer
version. (gcc-4.6.1) atm it gets as far as libstdc++ before failing :/.
Ill see if i can fix it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaS8nAAoJEIjGvG7Y4HU8NG8H/3K+RwnWTU8tRhTlJ5KDXkhV
8vRGFFK+a2eNk6h2Qy/iouwrDOVg6We3qsqF/84p2kYDeJI1aMtVPK1wKnYhei/U
pk3NUgWgm2cQQZGs7PfNziHGgWwg7DYt/ZgKL+Sw+RkF9zs1/JNASj8bTPLCiJET
H+aPv4LAm34N42PVUs9VFOHEz+OacVImRELTplRNqsUuXXPILhU4Md1w+F3u0OnE
t5jFuaZhIFCmrHkuHOoK3Vs/64nymjDLPIrCaqfFTKvN1BWzs3lvRN81lmL675m0
vKJntHQFZuWB46POjgRvvao3BabhIhEwozOTv9yJWHCUwllFFzxiyd5TgpZ6K+M=
=Ry3F
-----END PGP SIGNATURE-----

On 9.9.2011 0:10, Ralph Engels wrote:

> The makefiles need a workover btw since it installs things like it was
> a cygwin tree. Also you are correct about it needing a newer gcc i
> tried with Msys gcc and it failed. So im trying to compile a newer
> version. (gcc-4.6.1) atm it gets as far as libstdc++ before failing :/.
> Ill see if i can fix it.

Here's a somewhat working GCC 4.3.4 for MSYS, based on Cygwin's version:

http://teemun.x10.mx/gcc-msys/gcc-4.3.4-msys-bin.tar.lzma

Compiling GCC 4.x with MSYS is very difficult (especially libstdc++) as 
MSYS' Newlib is missing some essential things.

A recommendation: use Cygwin's sources for GCC and Binutils as a base 
when compiling a new toolchain for MSYS2.

On 9/8/2011 3:01 PM, Teemu Nätkinniemi wrote:
> 
> I think Cygwin 1.7 needs GCC 4.X to compile. Please share your patches 
> and sources as soon as you can.

This is true. I was always under the impression that we would have to
take the traditional approach:

  1) build a linux->msys gcc-4 toolchain
  2) Do all the mods to create msys-2 from cygwin-1.7 ON linux, until it
     compiles...also, build msys-2::bash and msys-2::coreutils with
     that toolchain.
  3) Then test the result on win32....repeat #2 and #3 until happy.
  4) THEN, build a "native" msys-2 toolchain using the linux->msys
     cross compiler.
  5) Install THAT on win32, and try to "self-host" (that is, build
     msys-2) USING the compiler under msys-2.
  6) Repeat #4 and #5 until happy.
  7) Try to build the msys-2 compiler using the compiler from #4.
  8) And...FINALLY, self-host the msys dll build using the toolchain
     from #7.  Repeat #7 and #8 until happy.

Ralph jumped straight to #7.

--
Chuck

On 9/8/2011 5:47 PM, Teemu Nätkinniemi wrote:

> Compiling GCC 4.x with MSYS is very difficult (especially libstdc++) as 
> MSYS' Newlib is missing some essential things.
> 
> A recommendation: use Cygwin's sources for GCC and Binutils as a base 
> when compiling a new toolchain for MSYS2.

Oh, yes, I forgot to mention: when you "update" your tree to modern
cygwin-1.7 sources, you ALSO have to update the underlying newlib -- and
apply all necessary msys-ization patches to IT.  cygwin-1.7 requires a
lot of stuff from "modern" newlib.

--
Chuck

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 08-09-2011 23:47, Teemu Nätkinniemi skrev:
> On 9.9.2011 0:10, Ralph Engels wrote:
> 
>> The makefiles need a workover btw since it installs things like
>> it was a cygwin tree. Also you are correct about it needing a
>> newer gcc i tried with Msys gcc and it failed. So im trying to
>> compile a newer version. (gcc-4.6.1) atm it gets as far as
>> libstdc++ before failing :/. Ill see if i can fix it.
> 
> Here's a somewhat working GCC 4.3.4 for MSYS, based on Cygwin's
> version:
> 
> http://teemun.x10.mx/gcc-msys/gcc-4.3.4-msys-bin.tar.lzma
> 
> Compiling GCC 4.x with MSYS is very difficult (especially
> libstdc++) as MSYS' Newlib is missing some essential things.
> 
> A recommendation: use Cygwin's sources for GCC and Binutils as a
> base when compiling a new toolchain for MSYS2.
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Your a lifesaver thanks :)
Allmost done, makefiles adjusted patch will be huge though as i spent
48 hours without sleep hacking about in the sources etc.
I will upload the patchset tomorrow i guess need some sleep now.

Best Wishes Ralph Engels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaUucAAoJEIjGvG7Y4HU8Lb8IAKm+4LPTw5FcY/zDmY55cDcS
LMRCKnCcMOpC6Leswl25PQIXJhLRSMByir3coCxerIz6N0ODHOlXhgbNrgTObJvf
VCtCl9VabNm/brRBuTlFFAJ2MvRrWxABKwH/PiDK5GA33ZOee3g1hxbdg8xqZG+I
EeRGynOE1vQNui/PBVqt2uCIfq+ATwGsaue1IP3wPFra+wV9a6TggMZqY5hjfmJz
9qXEsGKoDPeX/4m7hXjxy5zmK2pGQ+YBAtF6zUXxveG17LTqWRCXkHajIm2Nbc2O
U9slFWPrsPhAwcJXzik72Tl2ZqVoKpv1ztKVqE/NW7OovzZcx42QrJoC0HxJx60=
=5EyA
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 08-09-2011 23:55, Charles Wilson skrev:
> On 9/8/2011 3:01 PM, Teemu Nätkinniemi wrote:
>> 
>> I think Cygwin 1.7 needs GCC 4.X to compile. Please share your
>> patches and sources as soon as you can.
> 
> This is true. I was always under the impression that we would have
> to take the traditional approach:
> 
> 1) build a linux->msys gcc-4 toolchain 2) Do all the mods to create
> msys-2 from cygwin-1.7 ON linux, until it compiles...also, build
> msys-2::bash and msys-2::coreutils with that toolchain. 3) Then
> test the result on win32....repeat #2 and #3 until happy. 4) THEN,
> build a "native" msys-2 toolchain using the linux->msys cross
> compiler. 5) Install THAT on win32, and try to "self-host" (that
> is, build msys-2) USING the compiler under msys-2. 6) Repeat #4 and
> #5 until happy. 7) Try to build the msys-2 compiler using the
> compiler from #4. 8) And...FINALLY, self-host the msys dll build
> using the toolchain from #7.  Repeat #7 and #8 until happy.
> 
> Ralph jumped straight to #7.
> 
> -- Chuck
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Thanks well tbh. my Msys build environment had some rather hefty
patching to allow me to build some stuff that normally wouldnt build
at all so that might explain it. Well that and lack of sleep hehe i
been at it for two days straight with only pauses to take a step in
natures direction or to get another cup of coffe :).
I intend to post my patchset tomorrow sometime i really need some
sleep now :/ it will be pretty huge im afraid.

Best Wishes Ralph Engels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaUzqAAoJEIjGvG7Y4HU8U6sH/jOH6N1kdIzTJ2Rk4NDI75m4
aZsMisGpLFja/es/drmL2TkB323h7IVuR41fcxDRir8crWOfI/wyQ3+ytZAFz5BT
6FznkbncXI8kdBHpiAqAvicFvFxdN9ci+gThQUIVFx+iDLy1gfFP3cVPvNptPFMB
2mbSLmuKkd8SQrot1CEOKBWyxMWLt4Omx3R8Rx5slVSDB5mVsO9X5zI3NxaDFAfR
J+5B1fr8HzA2Ilhu+gTP8HBwSwOgVoWpbDXHMQOABpFKrccYgq4ko4KUGZDWqQ3j
pp7QiQzSdxrEKj3deuxPJV2wMUYHs3AKWFuiMbCXz2g5aH0R2X1fa/oa6BJLz4g=
=TVlE
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 08-09-2011 23:57, Charles Wilson skrev:
> On 9/8/2011 5:47 PM, Teemu Nätkinniemi wrote:
> 
>> Compiling GCC 4.x with MSYS is very difficult (especially
>> libstdc++) as MSYS' Newlib is missing some essential things.
>> 
>> A recommendation: use Cygwin's sources for GCC and Binutils as a
>> base when compiling a new toolchain for MSYS2.
> 
> Oh, yes, I forgot to mention: when you "update" your tree to
> modern cygwin-1.7 sources, you ALSO have to update the underlying
> newlib -- and apply all necessary msys-ization patches to IT.
> cygwin-1.7 requires a lot of stuff from "modern" newlib.
> 
> -- Chuck
> 
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Allready done :) much to my pleasure the standard msys tools work fine
with the new dll also, but bootstrapping gcc 4 from the old gcc was to
say the least a pain so the one you sent me spares me a load of work.
Allmost completed an msys developer package for testing ill upload it
to my sourceforge site tomorrow + patches.

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaU4VAAoJEIjGvG7Y4HU8FVUH/2EFD5Aaf5MBDoj2X3qXmPaD
MlP102kOuL1UwSVqw9Tow+nQ/1XLuNpsuUbKzbyjF+BFA9223LRXEeIPWLkGXFi2
e7bviYhXYREjkA8H982LKzo2WzK8ZPVTfz9L8Q6auFAVQnqNsyO1J9GnPIy7s7P/
a0A3x8Tf0asEqaPBC45tKyH7fsGxU6kwLikZBfcVi24/E/gpvmDRMoYdgPD/4z+k
HjDmX/T1L5RzXmbXHK8s4xz35IGEApXv9VV0kYKhSDmHwkDYRfUIW7fykzabP+4C
FJNkUnfiTTMjMPvFayd2N9i/oB3shylIWTpSgJESa4iN88PsueBrYOMqP1vNKgE=
=p1FI
-----END PGP SIGNATURE-----

On 9/8/2011 7:16 PM, Ralph Engels wrote:
> I intend to post my patchset tomorrow sometime i really need some 
> sleep now :/ it will be pretty huge im afraid.

This surprises me. I would have thought, since a large portion of
msys-1.0's changes are now part of stock cygwin, that the changes
would be /smaller/ not larger...

I'm fighting the flu or something, so I may not be able to properly
analyze your patch until next week or later.

-- 
Chuck

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 09-09-2011 03:03, Charles Wilson skrev:
> On 9/8/2011 7:16 PM, Ralph Engels wrote:
>> I intend to post my patchset tomorrow sometime i really need some
>>  sleep now :/ it will be pretty huge im afraid.
> 
> This surprises me. I would have thought, since a large portion of 
> msys-1.0's changes are now part of stock cygwin, that the changes 
> would be /smaller/ not larger...
> 
> I'm fighting the flu or something, so I may not be able to
> properly analyze your patch until next week or later.
> 
I might have gone a little overboard porting pretty much all the tools
besides the mingw specific ones (only missing cygcheck and strace atm
will see if i can adjust the makefile to accept the same vars as in
msyscore) else i got pretty much all the cygwin tools from the 1.7
package. The mount system is rather different from the old one so i
added some default mount points for the /usr dir to make the old tools
work untill i can upgrade them so far it seem's to work just fine.
One weird bugger i ran into is even after changing every environment
variable to report MSYS if MSYSTEM=MSYS it still reports MINGW hmm one
to track down later.
And sorry to hear you got the flu :/ Best Wishes for quick recovery
from here.

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaWsuAAoJEIjGvG7Y4HU8bNoIALQJNtytT3uOuEvl/hf/LLyC
XlsoE4fVspOvUmVx4kfCNlabtF1lO9DGt3sFInjWMIKT6vQPqfP2MgWwgS7uGqjS
FYy+kG6infM85iDBiYIz/95qZSCrEltnjnDzE/gXZbus6V+j9/xHfDLilspMaFAQ
4+utIyYvcvfef0/x+Mvz3Fy7XkKMHBOasxor8dN8tuCsJW5te8wgQs2Bdo4ejTpn
msg/SmO4lfEsa+1pf//4F/tiRtZm/boPWfTx6aWqmbUaMn5IYwGPoMDmFu59YNCA
1ddR13WlC69LZ+pwJ0Olo7xTHhJfz72FPGYoNsmJmObVNe9Lx9bsm8hg2k8Uz6s=
=nCLE
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Beta Msys2 environment uploaded.
Source also awailiable there.
Consult the readme in the beta if something is unclear.

https://sourceforge.net/projects/cbadvanced/files/Sources/?

Sleepy head uploaded both the beta and the source to sources :X

Ill do patches a bit later only got 2 hours sleep this night.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOab0VAAoJEIjGvG7Y4HU8jlAIAKZbD1ArwOpQ+rgWLts/PYE2
pXjCVOyFaWaPuWWPVkqFmAkQ7GcjUWdMeIluCXwXSsYkFWayByWzKHAJf+Ky6NsL
FAyUyVrl/4XXHjWbhN4HmgTT/LUziDYL4VzSJT4jOzuRdRFtjtvtf+LJCKWnA67X
/0okP6b6n/bjgkV6I4YbxHtcmLWLZK5okb6oIZB4qcqo6RlcBQ33XahPZ3/BalX6
MiV5PWUQt3LWWnP6dLfHf/Ha7xhwyuC53jz1vH6QEeMk8SoDMjtiUSkey3g8g2Yo
3OtCwlFQjnoUNlaQhtSmCS0aoqKFLy4yPTEgNCBM26Wg0biEdTW5oYE/xys5m/w=
=hEo1
-----END PGP SIGNATURE-----

On 9.9.2011 10:15, Ralph Engels wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Beta Msys2 environment uploaded.
> Source also awailiable there.
> Consult the readme in the beta if something is unclear.
>
> https://sourceforge.net/projects/cbadvanced/files/Sources/?
>
> Sleepy head uploaded both the beta and the source to sources :X
>
> Ill do patches a bit later only got 2 hours sleep this night.

I really do not have time to test it until later today but the current 
MSYS mounting system has to be implemented to get rid of the cygdrive.

I'll try to recompile GCC for MSYS (and release the patch) although 
MSYSTEM=MSYS should be fixed before that.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 09-09-2011 10:02, Teemu Nätkinniemi skrev:
> On 9.9.2011 10:15, Ralph Engels wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Beta Msys2 environment uploaded. Source also awailiable there. 
>> Consult the readme in the beta if something is unclear.
>> 
>> https://sourceforge.net/projects/cbadvanced/files/Sources/?
>> 
>> Sleepy head uploaded both the beta and the source to sources :X
>> 
>> Ill do patches a bit later only got 2 hours sleep this night.
> 
> I really do not have time to test it until later today but the
> current MSYS mounting system has to be implemented to get rid of
> the cygdrive.
> 
> I'll try to recompile GCC for MSYS (and release the patch) although
>  MSYSTEM=MSYS should be fixed before that.
> 
> ------------------------------------------------------------------------------
>
> 
Why Cloud-Based Security and Archiving Make Sense
> Osterman Research conducted this study that outlines how and why
> cloud computing security and archiving is rapidly being adopted
> across the IT space for its ease of implementation, lower cost, and
> increased reliability. Learn more.
> http://www.accelacomm.com/jaw/sfnl/114/51425301/ 
> _______________________________________________ Mingw-msys mailing
> list Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Np it all went a bit quick :)

MSYSTEM works only uname reports wrong.
MINGW instead of MSYS but it uses MSYS path so that part is working
but strange non the less since i changed the code for the environment
to report MSYS.

Did a gcc 4.3.4 + binutils 2.22 cvs yesterday i can upload it to my
site as well.

Tested the mount system today and agree we need the MSYS one. I can
mount mingw with it but bootstrapping a gcc build with this
combination is not quite working.

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOamg+AAoJEIjGvG7Y4HU8zQIH/3YAI5PeFArXJQJKHbROqMuH
Fc76AMJMRSkztR+sA5SyGL0+dQx8Fr3e+JDaA8JZbuDboTCScj0w+qpz2QJ8nZ2L
/JUrVbbXDXX0QmvddgvpQGo9+St1ZMg2jH5oxQnnskTK7vryxpF39CREfrJEQPLn
wDcglCLbzQL0E/RkhpOXEvMcNlgO5MoX6J4RDOycBFHsERjrNnQlz7+SDjOV2GPM
c2fS9qT9GVRleWH5GisC7JsP2D8SsLlg+c5GUl4GSbjhhoqNrGtmqX2TLoEuWLOn
UFuVEcIh87WHDUlkYc8Dn8xuiEbUZreRkP/BZgVNHSXbsXmdqIIMwcVPhag6xZY=
=hNEm
-----END PGP SIGNATURE-----

On 9.9.2011 22:25, Ralph Engels wrote:

> Did a gcc 4.3.4 + binutils 2.22 cvs yesterday i can upload it to my
> site as well.

Please do.

> Tested the mount system today and agree we need the MSYS one. I can
> mount mingw with it but bootstrapping a gcc build with this
> combination is not quite working.

I think cross-compiler using Linux (as Charles suggested) might be the 
best option?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok i will upload it allthough it was built for (and with) the new msys
so im not sure it will work for the old.
If it does not ill rebuild it for the old msys.

I made some small changes to the mount table to make it closer to msys
way but without changing to much yet. Let me hear your view on the below.


inline void
mount_info::create_root_entry (const PWCHAR root)
{
    /* Create a default root dir derived from the location of the Msys
DLL.
       The entry is immutable, unless the "override" option is given
in /etc/fstab. */
	/* this part seems to be needed for msys */
    char native_root[PATH_MAX];
    sys_wcstombs (native_root, PATH_MAX, root);
    assert (*native_root != '\0');
    if (add_item (native_root, "/", MOUNT_SYSTEM | MOUNT_BINARY |
MOUNT_IMMUTABLE | MOUNT_AUTOMATIC) < 0)
	{
        api_fatal ("add_item (\"%W\", \"/\", ...) failed, errno %d",
native_root, errno);
	}
    /* Create a default cygdrive entry.  Note that this is a user entry.
       This allows to override it with mount, unless the sysadmin created
       a cygdrive entry in /etc/fstab. */
	/* remove for msys ? only seems to apply to the cygdrive itself */
    cygdrive_flags = MOUNT_BINARY | MOUNT_NOPOSIX | MOUNT_CYGDRIVE;
    strcpy (cygdrive, CYGWIN_INFO_CYGDRIVE_DEFAULT_PREFIX "/");
    cygdrive_len = strlen (cygdrive);
}

/* init: Initialize the mount table.  */

void
mount_info::init ()
{
    PWCHAR pathend;
    WCHAR path[PATH_MAX];

    pathend = wcpcpy (path, installation_root);
    create_root_entry (path);
    pathend = wcpcpy (pathend, L"\\etc\\fstab");

    from_fstab (false, path, pathend);
    from_fstab (true, path, pathend);

	/* changed root to /usr as default for msys so the entire root is
visible to /usr, old one had static mounts for only bin and lib while
root was "/" */
    if (!root_mnt)
    {
        char native[PATH_MAX];
        if (root_idx < 0)
		{
            api_fatal ("root_idx %d, user_shared magic %p, nmounts
%d", root_idx, user_shared->version, nmounts);
		}
        char *p = stpcpy (native, mount[root_idx].native_path);
        if (!root_mnt)
        {
            stpcpy (p, "\\");
            add_item (native, "/usr", MOUNT_SYSTEM | MOUNT_BINARY |
MOUNT_AUTOMATIC);
        }
    }
}




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOao2cAAoJEIjGvG7Y4HU87dwH/iXvG6BcWt/Cha420qsQmYdx
2UMc1iUs/G3++C83dyagOzXacyQi+ndj1PU3xaqkOy5e8kny4/xjGAtfWp5ShnGc
O3Apm+SncQHRZhal+oOXuvM6HaNeWavL1XzqR6W1srl1c0+CCrgeg+okex0wpVG+
8XWTXrDTE3n5FyOIZmQW9q0REiIcP4K2OOBVkA2XLgmbpczg5D+ml/JCVMYQIjKm
83y588tIBVA/Sj/KSl0frtQ0iPw7ldm9gG+UyJW6vjb/3lctTZbhMujkhGZEfdlc
sJbHY2qzAXuiARHuXiw14rh/Q/J/2mOyDIo3n9H6dqVkLHtjXWQk90BWLqksL+Q=
=U+ZW
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 09-09-2011 23:25, Teemu Nätkinniemi skrev:
> On 9.9.2011 22:25, Ralph Engels wrote:
> 
>> Did a gcc 4.3.4 + binutils 2.22 cvs yesterday i can upload it to
>> my site as well.
> 
> Please do.
> 
>> Tested the mount system today and agree we need the MSYS one. I
>> can mount mingw with it but bootstrapping a gcc build with this 
>> combination is not quite working.
> 
> I think cross-compiler using Linux (as Charles suggested) might be
> the best option?
> 
> ------------------------------------------------------------------------------
>
> 
Why Cloud-Based Security and Archiving Make Sense
> Osterman Research conducted this study that outlines how and why
> cloud computing security and archiving is rapidly being adopted
> across the IT space for its ease of implementation, lower cost, and
> increased reliability. Learn more.
> http://www.accelacomm.com/jaw/sfnl/114/51425301/ 
> _______________________________________________ Mingw-msys mailing
> list Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Fixed the mount table problem to map directly to drive skipping
cygdrive. Now works exactly like msys :) going to test if mingw works
correctly with the new way now. If it does yahoo!.
Still a little work left since the cygwin runtime uses cygcheck for a
lot of the path related stuff and i cannot built it before i reworked
the makefile to accept the external mingw compiler instead of the one
that comes with normal cygwin which i removed.

If you are good with makefiles ill hand that part over to you. I can
mostly get around smaller problems but im by no means an autotools guru :/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOaptbAAoJEIjGvG7Y4HU887QIAIXcFzobOJ7nS3fxW5Pyk0JP
TvsmHqlz+O95w8m4arBIfIdBLoX/wUK+Vvwshcshkj9JLYpcEbqNrf47wFALlwYK
LDf/pcWJ/NZu5vnqWhbh74G0hvdC3g1aaTsxyW8Y0SjFhoD+rZkoJxXaqzO5xm6b
di1PI94E7VeBaLC/arpjwzh5O89x125DjU4WmyWxNUwnBPi+39WOUbHJBk4CxLaV
JjkswkzHjFwZ3n8Hw1N/InWuE6UUmN49zbPJ0guwK4SSoMINROvNW/bIJy/SgXGZ
f1V08w9RoscezYdgucj3BB2m+f1KXMCs91JOp038mj37JLVgJcMjWZ0pH6AQW4U=
=ekgR
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok now im running into trouble :X after changing the /cygdrive code
msys fails to recognize its own directories guess i should have waited
on that part untill i could get msys to recompile its kernel itself
(back to square one). going to keep the broken source for reference
and start over with the one that still had /cygdrive and work from there.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOawhfAAoJEIjGvG7Y4HU8TXsH/3XQ9bwCoovI/sq3EKwlJza3
FjFpNxgHnNuVIDDYEv1aA1xU/p/eK3l8AmPCZZg05x2liDELvvRYYBieo7HvyvcE
1si5SkQ9Ty3CGmNb1lkcnuXXn1RCU70Qa+Db4XiqsOT5ol5tcRJep9Jz0cb0jNJn
+SHbajYWQDCq+pbXYk/i/Vko6L1Ctw5hSL1b82l0wjD5pPLescL+K03JK6n2Hash
GfgWHPeZthdU4X9Mx7dQQl3A5hBjSbsY7lhqK2RWu+jjMH8VJj2d6h/bUF4c0OZE
4Bre1A2tzojTChof5GzYes96yk8VvCFpSi2+uYiFDjnixOQuNUwK8Yh64OdmRWE=
=jELg
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Still hacking about on it, and ran into some slight problems. For some
reason uname insisted that MSYSTEM was MINGW32_NT even if i was in the
msysdvlpr mode. Turned out to be a missing = at the end of the env var
MSYSTEM. the table now uses a different layout so it doesnt apply to
the old diff anymore. Also having some difficulty removing /cygdrive
(the code changed considerable). Atleast i got the new Msys to boot
the dll build but it gasps rather loudly on cygserver + cyglsa.
Unfortunatly it seems the dll depends on libcygserver.a + some source
files from it, so removing it would be rather difficult i guess.
Else it seems to be close to working but i wonder if i should upload
the diffs just yet considering its state ?.

One question i hope someone can help me with. Since i removed cygwins
internal mingw some tools cannot be built since they rely on the mingw
compiler + libraries/includes. Is there any way to tell it that i want
to use the external mingw without making a wholy mess in the makefiles ?.

Best regards Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOa3plAAoJEIjGvG7Y4HU8sowIAIzwbs3N8z0xz7bUrCOEspdz
WOrgju/alFxarAQh2Mmmurke/Cgivwitqzlax/mFuhvx17onnvu2nQJvN2UPKkt5
n6sqDI5xwaynWHqje0pSFutxWFXPAJ/uduzoVFLFIC9SI4JfAkpTfRzsgt2+hD5F
lPgpLjHaZkdU6dUaRFoRedVDEcTKvpdjku6tW/VlCqFAR6FolkcbF60k9ASjvi8q
xuCWJemmnQgV+qk11IGf/9GIcufLLGxgSrAJx50ZFyk/2x5aifRHsRCj5h+CuqJH
bm6xKILta8hPxc9ef5qf/FXoXsMfgK1axnjCC1FFPfi2JJ/0rMPXMoOpbeM+INc=
=5enH
-----END PGP SIGNATURE-----

--- On Sat, 10/9/11, Ralph Engels <ralphengels@...> wrote:

> One question i hope someone can help me with. Since i
> removed cygwins
> internal mingw some tools cannot be built since they rely
> on the mingw
> compiler + libraries/includes. Is there any way to tell it
> that i want
> to use the external mingw without making a wholy mess in
> the makefiles ?.

Rename gcc to mingw32-gcc in makefile.

On 9/10/2011 10:55 AM, Ralph Engels wrote:
>  Also having some difficulty removing /cygdrive
> (the code changed considerable). 

Cygwin now allows /etc/fstab to change the "default" value of the
cygdrive prefix from "/cygdrive" to whatever the user wants. Many choose
to set it to "/" -- which is what we want here, although we want to do
it in code, rather than in the /etc/fstab file.

It should simply be a matter of us changing the default value of
cygdrive_prefix, wherever it is defined, from "/cygdrive" to "/"

> Unfortunatly it seems the dll depends on libcygserver.a + some source
> files from it

modern cygwin cooperates with the cygserver daemon -- *if present and
running* -- in order to support certain IPC facilities.  So, the daemon
has an API, and cygwin dll uses it.  Now, you don't HAVE to have the
daemon running, and cygwin will just return ENOSYS when the user tries
to use the facilities that need cygserver for proper operation.  So, you
don't need to port cygserver *itself* -- just enough of the "interface
code" -- that is, libcygserver.a -- so that it can always return "sorry,
cygserver not running; please fail whatever operation the user was
trying to do".

> One question i hope someone can help me with. Since i removed cygwins
> internal mingw some tools cannot be built since they rely on the mingw
> compiler + libraries/includes. Is there any way to tell it that i want
> to use the external mingw without making a wholy mess in the makefiles ?.

Not sure.  I'm not clear what they've changed in the cygwin build
system, now that the "cygwin" compiler no longer support -mno-cygwin and
they have to rely on either (cygwin-gcc with -no-stdlib -no-stdinc
-I/mingw/include/path etc etc) OR (where-is-mingw-cross-compiler...).

If they are doing the former, then you ought to be able to do that too,
with msys-gcc -no-stdlib -no-stdinc -I/usr/include/mingw
-I/usr/include/w32api -L/usr/lib/mignw -L/usr/lib/w32api etc etc.

Hmm...well, we have the .../w32api stuff, since we provide an
msys-w32api package.  But we don't currently provide an msys-mingwrt
package, so /usr/include/mingw and /usr/lib/mingw don't exist. Maybe we
should?

--
Chuck

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 10-09-2011 19:29, Charles Wilson skrev:
> On 9/10/2011 10:55 AM, Ralph Engels wrote:
>> Also having some difficulty removing /cygdrive (the code changed
>> considerable).
> 
> Cygwin now allows /etc/fstab to change the "default" value of the 
> cygdrive prefix from "/cygdrive" to whatever the user wants. Many
> choose to set it to "/" -- which is what we want here, although we
> want to do it in code, rather than in the /etc/fstab file.
> 
> It should simply be a matter of us changing the default value of 
> cygdrive_prefix, wherever it is defined, from "/cygdrive" to "/"
> 
>> Unfortunatly it seems the dll depends on libcygserver.a + some
>> source files from it
> 
> modern cygwin cooperates with the cygserver daemon -- *if present
> and running* -- in order to support certain IPC facilities.  So,
> the daemon has an API, and cygwin dll uses it.  Now, you don't HAVE
> to have the daemon running, and cygwin will just return ENOSYS when
> the user tries to use the facilities that need cygserver for proper
> operation.  So, you don't need to port cygserver *itself* -- just
> enough of the "interface code" -- that is, libcygserver.a -- so
> that it can always return "sorry, cygserver not running; please
> fail whatever operation the user was trying to do".
> 
>> One question i hope someone can help me with. Since i removed
>> cygwins internal mingw some tools cannot be built since they rely
>> on the mingw compiler + libraries/includes. Is there any way to
>> tell it that i want to use the external mingw without making a
>> wholy mess in the makefiles ?.
> 
> Not sure.  I'm not clear what they've changed in the cygwin build 
> system, now that the "cygwin" compiler no longer support
> -mno-cygwin and they have to rely on either (cygwin-gcc with
> -no-stdlib -no-stdinc -I/mingw/include/path etc etc) OR
> (where-is-mingw-cross-compiler...).
> 
> If they are doing the former, then you ought to be able to do that
> too, with msys-gcc -no-stdlib -no-stdinc -I/usr/include/mingw 
> -I/usr/include/w32api -L/usr/lib/mignw -L/usr/lib/w32api etc etc.
> 
> Hmm...well, we have the .../w32api stuff, since we provide an 
> msys-w32api package.  But we don't currently provide an
> msys-mingwrt package, so /usr/include/mingw and /usr/lib/mingw
> don't exist. Maybe we should?
> 
> -- Chuck
> 
> ------------------------------------------------------------------------------
>
> 
Malware Security Report: Protecting Your Business, Customers, and the
> Bottom Line. Protect your business and customers by understanding
> the threat from malware and how it can impact your online business.
>  http://www.accelacomm.com/jaw/sfnl/114/51427462/ 
> _______________________________________________ Mingw-msys mailing
> list Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Tried setting the default cygdrive prefix to / but that crashes the
dll. I managed to do it some other (complicated) way which seems to
work except for having trouble bootstrapping a gcc build with mingw.
It might have been related to a previous problem i had where uname
refused to accept the values from the MSYSTEM var even though i added
the code specifically. I found out that the cygwin team had changed
the way it looked for forced env variables but it was a pain in the
proverbial behind to figure out which boolean in the table turned the
correct variable on (no documentation besides that it was changed).
Besides the fixes i managed to get it building itself besides 2 of the
tools (cygserver.exe & cygcheck.exe) the rest builds now. cygcheck
depended on the mingw that normally came with the source so adjusting
the makefile to use the external mingw should fix that. cygserver
fails with unknown reference to vtable hmm ? i tried adding libstdc++
as that is normally the cause for those errors but that didnt quite
cut it. Ideas are welcome.

Updated gcc to 4.4.6 for the build environment as the old 3.3.4 cannot
cope with it. (cannot be used with the old msys unfortunatly) :/

ill keep the diff of a little longer untill it can build itself fully.

In regards to including the mingw runtime like cygwin does. I wouldnt
mind and it will be a whole lot easier to get things going. I was just
afraid it might interfere with seperate mingw mingw mounts, but if
that aint the case then i see no reason not to. Will also help
immensly in porting tools.

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOa6oaAAoJEIjGvG7Y4HU8A58H/3447xmnk/3qr5NsBVu1t8im
S4xbz5hYY9LJwKVilWppTWfxWynXeP46w79qq6dxEl3lEnJ6vD5Su2/xMo7JcQVU
LGS0QQCv82CYTg3ojYoR/8gmV/bYVyDrPrY6ubE1jNrDGbo2scO48GuEnRJPWYdR
7pMb917KqKVgD2N7g+/XcumckUw5YaQujOUIbB/Bq327Zueu8ulSuW9EMF2SsvAO
R7hK6E+Gqqrx7Z+KvoGYmINBvUxHe+IdmqY8YzlGG9A70zmDd3J8O6u1AeddHvrI
u1sbsi5TIx1OQzQhkvYy0PSZx8w13Ht/HMZPAejXbJ8RZfDt9RNs5/Lvc477hfY=
=lB/l
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Last bugger before it can build itself natively.

/cygdrive/d/projects/builddir/msyscoreport/source/winsup/cygserver/client.cc:38:
undefined reference to `vtable for client_request_get_version'
/cygdrive/d/projects/builddir/msyscoreport/source/winsup/cygserver/client.cc:38:
undefined reference to `vtable for client_request_get_version'
client.o:/cygdrive/d/projects/builddir/msyscoreport/source/winsup/cygserver/client.cc:281:
undefined reference to
`client_request_shutdown::client_request_shutdown()'
client.o:client.cc:(.rdata$_ZTV25client_request_attach_tty[vtable for
client_request_attach_tty]+0x14): undefined reference to
`client_request_attach_tty::serve(transport_layer_base*, process_cache*)'
/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/winsup/cygwin/libmsys-1.0.dll.a(libcmain.o):
In function `main':
/cygdrive/d/projects/builddir/msyscoreport/source/winsup/cygwin/lib/libcmain.c:39:
undefined reference to `_WinMain@...'
collect2: ld returned 1 exit status

I cant for my life figure out why this fails ? it uses g++ as it
should hmm ?. All other tools now build.

heres the commandline it uses to build.

g++-4
- -L/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/winsup
-
-L/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/winsup/cygwin
-
-L/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/winsup/w32api/lib
- -isystem
/cygdrive/d/projects/builddir/msyscoreport/source/winsup/include
- -isystem
/cygdrive/d/projects/builddir/msyscoreport/source/winsup/cygwin/include
-isystem
/cygdrive/d/projects/builddir/msyscoreport/source/winsup/w32api/include
-B/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/newlib/
- -isystem
/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/newlib/targ-include
- -isystem
/cygdrive/d/projects/builddir/msyscoreport/source/newlib/libc/include
   -o cygserver.exe client.o process.o msg.o sem.o shm.o
threaded_queue.o transport.o transport_pipes.o bsd_helper.o bsd_log.o
bsd_mutex.o sysv_msg.o sysv_sem.o sysv_shm.o setpwd.o
/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/winsup/cygwin/version.o
/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/winsup/cygwin/libmsys-1.0.dll.a
- -static -static-libgcc
-
-L/cygdrive/d/projects/builddir/msyscoreport/build/i686-pc-msys/winsup/cygwin
- -lntdll

allthough i dont see any reference to libstdc++ i tried adding it
manually to see if that helped but nope.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJObHrWAAoJEIjGvG7Y4HU81AcH/2g0B+ELpzvv9dcQDNQCbH3d
e5WWzLUJZN8irCEZiODIErDm9e2kWs6gCohn944TJcLA7FwnP00sDW3wEop4rc5y
KRzeFhHuaWFFLNUskAOYOGBH4IuicpPaoBIc1Sr9x5Jjp0hRaBWs1Aj4Bmxx+CUU
FfqGzfWejX4AhFa835lRlgXjWiv0cM8w3XE457U+gq8oJo4mGI7P/xATeWdafSSe
V4CEGiQuYpy6smflolvM7AkBKG7NTGRokgM8dA98JX+jr1d9WjKcACiIhzKkTkwq
DcSjqP2eKa2QWUCfT3rJmfrTzbtex1nfi4u9aUiu0gxfEZFTy0Sz3qcNBcuAB2E=
=d5xs
-----END PGP SIGNATURE-----

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

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.

-----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 Mingw-msys@... 
> 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-----

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?

-----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 Mingw-msys@... 
> 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-----

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?

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

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

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

-----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 Mingw-msys@... 
> 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-----

-----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 Mingw-msys@... 
> 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-----

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.

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

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.

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

On 9/12/2011 12:06 PM, Vincent Torri wrote:
> 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.

There are two ways to go:

1) more stripped down, less posix support: faster, but current apps
(like, say, coreutils: even coreutils-5.97) will break as it depends on
the current posix feature set of msys-1.  And forget about updating to
newer platform apps like coreutils-8.10.

2) more posix support: allows to update core platform apps to newer
versions -- since cygwin capabilities drive upstream feature
exploitation, and msys is a "walled garden", newer upstream projects
continually add new requirements on new cygwin features.  This makes
porting to msys1 harder and harder every year. I currently have to add a
lot of (old) workarounds to msys-ssh -- workarounds that USED to be in
the upstream code under #ifdef __CYGWIN__, but have now been removed as
unnecessary on cygwin.  This is true for many upstream projects.

Thus, I don't see #1 as feasible longterm. We really have to go with #2,
or we'll be stuck with older and older (relatively speaking) versions of
the application suites (such as coreutils, ssh, etc).

The price of progress.

--
Chuck

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey again.
Sorry fell asleep so didnt catch up.

For me the goal is mostly access to newer tools i cannot build with
msys1 (that and better posix support). I kinda expected build times to
go up with unicode support so in that regard im not surprised. The
goal for me with Msys2 is the same it was with Msys1 to have a posix
environment for things with autotools dependancy to build on windows,
not so much to try and make a mini cygwin :) (allthough my current
version looks awfully like that). I hope to make it closer to how Msys1
works over time.

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJObtb3AAoJEIjGvG7Y4HU8pxcH/jaaJdNn0K57Rtz7ynKRyF6/
W7QLHIC1emtOZvx0238ushwnKIV1W9If4+IopFJ5xIpGcwiGjHoMK/4iCw36xR5m
XvzXboB5S2CJjOuGTZPUU5PCzN+/CcsHXb8TiMl+G4kPhoMkKeA1RwxtowhAsgHJ
3Hl3MaLYLAyVpbvlEXiIO15opnvGD2Td94ZQESDXbZzmCEZXbwXX+qyBfH4poCak
zliW4zQTj+JtSuu3bxvC5jmtIIMHxOC5fOX/+fKr9BQhIcIJRf+7nJN919XjZBUS
BhBR60qoCohDcZdonp6BEwCIHmAkAXEwqsRYqmnyUM/i7bUb+dl9dio4vMPdaD0=
=d2Dx
-----END PGP SIGNATURE-----

On 13.9.2011 7:07, Ralph Engels wrote:

> For me the goal is mostly access to newer tools i cannot build with
> msys1 (that and better posix support). I kinda expected build times to
> go up with unicode support so in that regard im not surprised. The
> goal for me with Msys2 is the same it was with Msys1 to have a posix
> environment for things with autotools dependancy to build on windows,
> not so much to try and make a mini cygwin :) (allthough my current
> version looks awfully like that). I hope to make it closer to how Msys1
> works over time.

There are patches for Cygwin that enable profiling the Cygwin dll 
itself. Might be useful as soon as MSYS2 becomes stable.

I forgot the link about profiling:

http://www.mail-archive.com/cygwin-patches@...>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 13-09-2011 07:25, Teemu Nätkinniemi skrev:
> I forgot the link about profiling:
> 
> http://www.mail-archive.com/cygwin-patches@...>
>
>  
> ------------------------------------------------------------------------------
>
> 
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the 
> BlackBerry® mobile platform with sessions, labs & more. See new
> tools and technologies. Register for BlackBerry® DevCon today! 
> http://p.sf.net/sfu/rim-devcon-copy1 
> _______________________________________________ Mingw-msys mailing
> list Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Links to new gcc and source for it.

http://sourceforge.net/projects/cbadvanced/files/Tools/gcc-4.3.4-src-msys2.7z/download

http://sourceforge.net/projects/cbadvanced/files/Tools/gcc-4.3.4-msys2.7z/download
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJObu5CAAoJEIjGvG7Y4HU8QGoH/1U4xEcRpUcEyvH+QN/qAd+e
7pbQKcF5fRHeMfCIOkM3iQoeNJEtGxAiGkHKI4hE6IeIik0MFfrbCA3zQ0VFJizc
oCQ1yAUUQWm17WVSxWb/saOesCh58BpAoog9YDvx8b0pM+xSoZ/PrVTmIji8EGiG
SwD/h6ATxNzdG4qVfV+M540NFytkd/+eCP5mddZHCc4SUDfDJOwfarv2GTKoKho8
12IRKcOaskdVfHotUy2HF49LP/CKHR0KLsArqgaJk7FVoqJcWFGmKnIr8EajjA4o
fzGhWhwS5VGvZd4G+VU4FlztV8BHnq+KnFwQBo9p9Rqz5xeLHUa6nXzuBjrfNxU=
=yDcQ
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 13-09-2011 07:25, Teemu Nätkinniemi skrev:
> I forgot the link about profiling:
> 
> http://www.mail-archive.com/cygwin-patches@...>
>
>  
> ------------------------------------------------------------------------------
>
> 
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the 
> BlackBerry® mobile platform with sessions, labs & more. See new
> tools and technologies. Register for BlackBerry® DevCon today! 
> http://p.sf.net/sfu/rim-devcon-copy1 
> _______________________________________________ Mingw-msys mailing
> list Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Thanks teemu. Ill look into it.

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJObvPpAAoJEIjGvG7Y4HU8Vq8H/Rl5jo/6E4cCu2GKA3A5GCIC
VLQo83Cqe5n1FvZpfkkeRz0RrnZPR6zCBKq+FpdJ2KqM1CowCTm3EXCDbg8DwhEG
GodUhFLJhgWLosRoWgb40YGaW7T9ljAxUQQEFPT7jQNJyCVVsaZgDPZWF+G/RXaU
Rw4GrWA1yRkafVOO48QEOgQYDtKmURDYXie1chcR0u4w5BS1yMRzKzn2ITgFXcdQ
lOHrsTwQaTJL6mX4S849mSa2nrvqJJWvqECeFjo4d441agw6V0oRKJrhd/jmffTn
TvnkYRVA7A9k4bsYtAo/UQExdp8/KfpjhUJfV/7jYypsyvxJ1BcdTlT9z1fswI0=
=PEj7
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 12-09-2011 21:40, Charles Wilson skrev:
> On 9/12/2011 12:06 PM, Vincent Torri wrote:
>> 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.
> 
> There are two ways to go:
> 
> 1) more stripped down, less posix support: faster, but current
> apps (like, say, coreutils: even coreutils-5.97) will break as it
> depends on the current posix feature set of msys-1.  And forget
> about updating to newer platform apps like coreutils-8.10.
> 
> 2) more posix support: allows to update core platform apps to
> newer versions -- since cygwin capabilities drive upstream feature 
> exploitation, and msys is a "walled garden", newer upstream
> projects continually add new requirements on new cygwin features.
> This makes porting to msys1 harder and harder every year. I
> currently have to add a lot of (old) workarounds to msys-ssh --
> workarounds that USED to be in the upstream code under #ifdef
> __CYGWIN__, but have now been removed as unnecessary on cygwin.
> This is true for many upstream projects.
> 
> Thus, I don't see #1 as feasible longterm. We really have to go
> with #2, or we'll be stuck with older and older (relatively
> speaking) versions of the application suites (such as coreutils,
> ssh, etc).
> 
> The price of progress.
> 
> -- Chuck
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
I think i agree with wilson on that one.
The ammounts of hacking i had to do lately to get things like
coreutils-8.10 semi working on msys1 was pretty staggering :/ and it
still cannot parse permissions correctly so i turned of all security
on it so it would atleast work for building other apps on msys1, but
tbh that is not the way to go.

Can probably optimize the runtime to some degree i reckon, its all a
question of time and work :).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJObvZeAAoJEIjGvG7Y4HU8zxkH/jrUXe8LeX2VqPVqHIN8oB7T
MTPWyZg0hwTfw875ugRpTzftBxhOjUUk8J22f3rXCyS9rNdNSoTMPkHbDYuSL0d4
0yKkua8GyB6Nili0ZExJBZp+yNKXPys6cFTQJ1sAuq/FCsIkC+uh8pVyvqxr/I9P
vDWJhv41C0A0fXNhL87narJriMAyhwMpxpjkkZE2cRAzc7NdqgnliLQ3uzupGyR7
iuNFl4e1KHi4g8B0JzYbjrIA2Nv5+VATom8yKNwujZBEATffFZ33FjJ3lSNg3+XP
0vb93q7kSdvdilWVBGy6P9ebEo1u1J1f8KfGhnah4LZPOlu0FYonl+7g1NadNNM=
=4uq+
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Allmost forgot.

Fstab mounts follow cygwin syntax so if you get an error its most
likely because you have something like c:/somedir. /somedir in fstab.
Asmwarrior PM'ed me with exactly that and i gave him an example on how
to do it.

# mount things outside the msys directory here.
c:\msys2\mingw32 /mingw32 cygexec binary 0 0
c:\msys2\mingw64 /mingw64 cygexec binary 0 0

Mounts these two as a part of msys2.
Theres a few quirks with mounting MinGW like this unfortunatly.
For one a gcc bootstrap fails because libgcc cannot find the libraries
(/cygdrive problem it seems) maybe because my MinGW gcc was built
without hmm ?.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJObwiMAAoJEIjGvG7Y4HU822EIALHa352SVFXj/ldmPv6EXIFX
7g28A4vps2RqInvv0Wc7Q7cE4ZzI3bEe/45rruTJ5FJ/anOTlUJCOE2xX+4KQqNa
2MsNRPHngfitMwxG61e2620dIg4w3JDn9/DniIBeJd+Zpusy/85cbEcJEABwcRoi
TJTBm6rTd+1pE2p5T+jXKoJQ3zb08LRWhkSXgTEIwqtz/9GKYmsYITm5aTpIw83m
7WdBeT8jQX9ICqSMtEyfBcl96HM3VTGmHqxH8ddkxnEgT+HFMe5XOzeF7nKLPsgs
LMRImTHJaCAOj6z+7Vy/iR2JZD6k8qygRST5ce+RiIQKFUBZOUmdn1LddLx8zIc=
=y5Xb
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 13-09-2011 07:25, Teemu Nätkinniemi skrev:
> I forgot the link about profiling:
> 
> http://www.mail-archive.com/cygwin-patches@...>
>
>  
> ------------------------------------------------------------------------------
>
> 
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the 
> BlackBerry® mobile platform with sessions, labs & more. See new
> tools and technologies. Register for BlackBerry® DevCon today! 
> http://p.sf.net/sfu/rim-devcon-copy1 
> _______________________________________________ Mingw-msys mailing
> list Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
I recompiled the old gcc-3.4.4 and libiconv-1.13 for the new runtime
as it turned out some exports from iconv where missing in the old one
causing incorrect runtime compilation if it picked up iconv. Gcc-3.4.4
i done to see if did any difference so far nothing weird but it works
fine.

i made  folder for Msys2 stuff on my server. You can find new builds
etc there.

https://sourceforge.net/projects/cbadvanced/files/Msys2/

Best Wishes Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOb0rhAAoJEIjGvG7Y4HU8EjAH/1SI1Eft/Lm4Pm2n1/7AHi1p
U3+Hp0YSyZN32JshkkAEULvcwXI8bnD+9LFnE0Sn40nRqg2nTK+iOR2esXN3xwkg
EUkEUN2T9cnNcBsIl4qloh84H+coYtFXHQGkGQ+VYB3mLlDWlWmnE4j5Gi6ajUs4
vEm72jRZn8AzgSoEnakAA46Kv3L/QTzdJnr2Js8tz3Nspfqz7Iw2hZhpiXik+RiZ
N1Kgd6uz65NNmFukDeMfO2vy286oParrpo2Gc41P47DTtJxOcZq2MyD3YBDuEHy1
vYxzhBBsQixKmhVJaKbSPOB2seV1ztbla5HkyfRXDvss0jWxMMZbShWmRp2TvH8=
=qJ9l
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok seems i got closer to a user buildable port, there are a few
caveats though. First it needs a pretty complete Tex package for the
documentation (i could supply my own environment but its HUGE 10gig+)
or someone could help me deactivate the documentation build (more
likely i think). Also it needs atleast the new Build package im going
to upload (Msys1 cannot do the job unfortunatly).
It still uses a close to Cygwin mount system so if the developers wish
to change that i think it would be appreciated. I been very carefull
not to change to much only modifying the source to accept the Msys
structure instead of looking for the compiler in a subdir eg.
/usr/i686-pc-msys. I better let the real Msys developers hammer on the
mount system. The msys-1.0.dll exports the same things the old
msys-1.0.dll does besides the AbsDllPath etc stuff, so old msys
packages work with the new runtime. This means you wont have to
recompile everything from ground up atleast not immediatly. A few
newer things are needed though
so as gcc-4 libiconv mpfr gmp ppl and cloog (supplied on my
sourceforge server).

I will upload the source + patches shortly.

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOb4RfAAoJEIjGvG7Y4HU8gCAH/jJ5472AzkMXdY01U/Z/8xVx
+IyPYxcpPKKvPKhl3EtAXxJY84PeiyN9f6mVAIhrX6wuLGPbkFHeM7/IRt8+VNmy
oO2xDhd1S213onQ6Gn5qYE7qS2jjMT9QQLBYCjAgEwR2+E/DL8nTrKyBWY1iCz7o
BnFn/nxw+9aMMH+cFZjOz5hpVwF5zoFwx25OS/CoilnwiCc//8W5vY5R3m/9ituD
cUXvU120lsFyZexVWeoq5LJ0yDvyKXe0pbE8DZGkFfKWbPnQjnBw9zE1MUJPXdMw
RQDz3YQcuzwv7uZm40ddIof27zi++cTd3ePiCxNByofn0UsxiwZbuH6EGe4YWj4=
=id47
-----END PGP SIGNATURE-----

On 12.9.2011 22:40, Charles Wilson wrote:

> Thus, I don't see #1 as feasible longterm. We really have to go with #2,
> or we'll be stuck with older and older (relatively speaking) versions of
> the application suites (such as coreutils, ssh, etc).

With the following patch the latter option seems more feasible as it 
speeds up Cygwin quite a bit. First I did some timing with configuring 
Cygwin and here are the results (repeated three times but the results 
were basically the same on all the runs):

Normal Cygwin 1.7.9
real    1m6.456s
user    0m6.118s
sys     0m14.377s

With jojelino's patch
real    0m22.126s
user    0m5.899s
sys     0m14.316s

After this I decided to build the whole dll (using make -j3), first with 
jojelino's patch applied:

real    10m23.910s
user    5m50.155s
sys     7m35.555s

And decided not to run the test with the regular dll as it takes around 
20 minutes on this machine.

Here's the patch:
http://www.mail-archive.com/cygwin-patches@...>

On 13.9.2011 19:27, Ralph Engels wrote:

> Ok seems i got closer to a user buildable port, there are a few
> caveats though. First it needs a pretty complete Tex package for the
> documentation (i could supply my own environment but its HUGE 10gig+)
> or someone could help me deactivate the documentation build (more
> likely i think). Also it needs atleast the new Build package im going

Building the Cygwin dll ignores errors regarding building documentation, 
like this:

make[3]: xmlto: Command not found
make[3]: [faq/faq-nochunks.html] Error 127 (ignored)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 13-09-2011 19:07, Teemu Nätkinniemi skrev:
> On 13.9.2011 19:27, Ralph Engels wrote:
> 
>> Ok seems i got closer to a user buildable port, there are a few 
>> caveats though. First it needs a pretty complete Tex package for
>> the documentation (i could supply my own environment but its HUGE
>> 10gig+) or someone could help me deactivate the documentation
>> build (more likely i think). Also it needs atleast the new Build
>> package im going
> 
> Building the Cygwin dll ignores errors regarding building
> documentation, like this:
> 
> make[3]: xmlto: Command not found make[3]: [faq/faq-nochunks.html]
> Error 127 (ignored)
> 
> ------------------------------------------------------------------------------
>
> 
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the 
> BlackBerry® mobile platform with sessions, labs & more. See new
> tools and technologies. Register for BlackBerry® DevCon today! 
> http://p.sf.net/sfu/rim-devcon-copy1 
> _______________________________________________ Mingw-msys mailing
> list Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
Aye its just the install part that fails the build succeds.
I made the full package now and its compilable with itself.
Uploading the full pack to my server now. Dumper.exe relies on
msys-z.dll and some of the others need the gcc-4 stdc++ dll but thats
it. To build the src you need a mingw subdirectory under /usr.

Have fun testing :)

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOb51DAAoJEIjGvG7Y4HU8kSwH/2OXpw3qYFO+sLLuAUWhu3Wz
Ck2Jr3syFxi7vHZOB/c7SJPIuxQdJAmMENDLmsk/FlhT54F2yWFDllQer+9hYGM0
eWRPxHsUDWdIYG2fA+hMe0fllFWLtNEgU4eOokI+lXZh/DA8rZSEBORmMm/FqoNh
+HXtDNQl+OL6qdw7tV//dcrmYVWgRyHSTjgi6GKw03m7J7yfdrEcjsmLv68kOfb6
ecAm061IB+myNHMbiSGjBi6dWcF98mze4EuII2EKYJLX4oJiFkq3tdTTVqyWMEf8
LxCjV10iSUFcT972we1JhbYGt21x1j/WzSp9Kjz8C12liBmppy1zmxE1dMcwvv0=
=NO0a
-----END PGP SIGNATURE-----

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

On 15.9.2011 14:31, Ralph Engels wrote:

> 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 :/.
>

I am extremely busy until Monday so I really cannot do anything about it 
before that.

Use procmon and strace to see where Mingw's programs are trying to 
access the files and that might give you more insight on the problem.

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

The people who know MSYS the best are Earnie, Charles and Cesar.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Den 15-09-2011 21:17, Teemu Nätkinniemi skrev:
> On 15.9.2011 14:31, Ralph Engels wrote:
> 
>> 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 :/.
>> 
> 
> I am extremely busy until Monday so I really cannot do anything
> about it before that.
> 
> Use procmon and strace to see where Mingw's programs are trying to
>  access the files and that might give you more insight on the
> problem.
> 
>> 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.
> 
> The people who know MSYS the best are Earnie, Charles and Cesar.
> 
> ------------------------------------------------------------------------------
>
> 
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 Mingw-msys@... 
> https://lists.sourceforge.net/lists/listinfo/mingw-msys
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOcmITAAoJEIjGvG7Y4HU8Zd0H/0bVr1k0EJQTUQNLUNuzHESO
KGdBx+PfSOs7u8wcqR3P6IfpGUPgBCHU4LD42P1QE/53nvOLoIPKGzpvs2eGDaLm
uUuoMpHGuTq87kAG6m7kdCm1A6qjOmIn4lpF84wcmJqCjsMtwVNUZx6KG/vGdQ/w
709IamVsPut1ZvUmAxEgGGUIuaAgcB2Q13EtdkFRZ8ZzsOXfdQ8HiqIorZ2p6TbC
eTBdkxJWL7vGyDdDpK4gtT1hKXtKMat/aguvWdRjyTQKjeEexHHO0UIyrQUwGH83
rBN4PX7ieUgjGQArW0qbxOoCyXeil/neXSZzHOScglBGdIglp6TAdfvGeR16xGQ=
=pH0M
-----END PGP SIGNATURE-----

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

-----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 Mingw-msys@... 
> 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-----

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOfujXAAoJEIopQjIpgMdESJQH/iBXLaw5/XQaYGbq2bf7i0Su
4pd/L5ywJNIa4a34CNWNG1ozlMkWJulZDyAoErXewz8iVIeuiWQv+eC20z3cz8Qz
5uFxE2jUN741f5Pe4zL3ujPh9ktWwGySgZ/2HcGoThzmVUABJiY2nywNqQfsPkJo
s+iY+pWeAAoa+WR/WDnBpF1TX1vjTfxcCApB6Cc57NaBjvNXTTOA+wx33/4BHkVq
P43SEzxt4weLTd+jLwNrsTQ4Nt/A6mMSF99jRoLXUZxm/zvsGwfLV+PmV0aUTITP
W4J0NgIUBbiLZqv+hwvjG2kN7CB6fVvqnV7t8bCGEIlf2JoTafRSUV0PseI3MCg=
=8FcQ
-----END PGP SIGNATURE-----

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

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

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

? 2011/9/27 3:23, Ralph Engels ??:
> 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
Eagerly for your back :)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOgSUZAAoJEIopQjIpgMdEV4EIAJeCub0cQlP85h9QJrRRWSnf
jrlgV3+GWVZXZOvBr9QbB+KUj4aNq4Ad0KHWv5k4dvkf10gxkQijfqGi8oFpsVpp
oKygSIIXIq/nBd2DBR0a9uYs8nDV3bK8s4sLJg7Ub21VUqgwIWKlQ/fi+Fw+Akja
nXc/HULEMLWUnq2QInGaCsTinvjdLM2G2OpEdN1E4EjjieNVD3GSa2iftJv96Xsb
PCPKBF8oWmfAVFrj6RwCdItgFU4721aMsYEBcY2jP7TuWUFVB2f3lFxkpe1otGnR
wMqgDFYOIy3iWAyIArqAUezVl+NWLGCVNV2gazNWX7xsaKuMkB9nZBAPzom2znM=
=QyRw
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks :)

I havent dropped the project but im still a bit short of c++ knowladge
i started a long time ago with pure C and in a totally different
direction (game development) i did pick up some substantial knowladge
about gcc autotools and gnu compilers over the years though (im no
richard stallman though) ;).

The work on my port so far was making a native msys environment to
avoid the need for cross compiling and for that it works quite fine.
What remains are things such as support for the win32 version of mingw
instead of cygwins mingw.

- From what i gathered speaking to Earnie and others the vital part of
that seems to be the msys_p2w function but i ran into a few roadblocks
implementing it since the functions where it was used have changed
considerably.
Also cygwin seems to have a new funtion which does atleast part of
what the msys_p2w function did in the cygwin_conv_path function but
missing the support for the mingw compiler. My thoughts on this is it
might be possible to modify the existing function to implement the
missing functionality from msys_p2w, but i might be wrong so ideas are
welcome.

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 :).

Ralph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOgWySAAoJEIjGvG7Y4HU8OWcH/A+2EUq2fHGfQ6uAwxgk0Kjx
lgFFBjnfNe89SYiue88Bq6eltbkiQBo3Rt/fM53XycH4K23S0itQ2I6stz+MD8JN
sE590LjPFzHUrgYxOmk9wr0GFZuVM//LVnMcvVKXev6VmdRmy97SqDxE8k++mWsB
ZD20bDQi2uqzjP9x668SvACIN3SLmE0O6KVeanKB19hMdSrhp0X/nJujxJLS7QCj
oaNDOwlIfMim+aiRSfrFsnR2/cnSSB/LKHty3rR08HXZGyzTUnybDSv9aXWe7gfI
kqiuMpDjVQ7kSCcOavMrwuGgXcRuOIGAI5MrnmIQWRkcl6Q+u/aNeEHUNaueJ28=
=SOB3
-----END PGP SIGNATURE-----

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aye im aware of the shortcommings allthough i havent used xp in quite
a while, and newer with a fat table. Im not sure how cygwin normally
handles situations where its installed on a system with a fat table
but i suspected that it had some failsafes such as turning symlinks of
in case the OS didnt support them ?. The Msys way is ok with me if its
easier to maintain but symlinks have kinda grown on me since i use
sysroots quite often and it saves me having headers and libraries in
weird places :).
The ultimate descision is ofcourse up to the msys developers who might
want to use my preliminary port as a base for a new msys core.

Ralph


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOgY8VAAoJEIjGvG7Y4HU802EH/A2LuvX3lW9To61e+1/et6tV
JCU0qdYxvy15E96+ylFAKdrJKUZdI+KGJlUYRqjHs+8fFrHs0rR/ht1/kLj27RP0
EoDOe51m9ARDUdhF3HZypQcVkXtzjoJuHiE7Tep+eSJwbWVBNN/MUH2AXfkdqPPa
e5kOBAYVSow6iPYpNbRu7aWyrEMBSJNEf9R3ecDfYXgR6yrB2aKkl7+/mkU+zZEJ
jbaQgIEK3y68NGtBMwg7kAYt1OWTVzUTNEX0GYTessYZMthqKj4qSVvlAnF8rFmU
F+gdp5dgc09rUOk3l3kSuXCLTXmURHbb4o7rPuYbd7t8PEX2jNuVVrnjNKYbtZM=
=9isv
-----END PGP SIGNATURE-----

On 9/27/2011 4:53 AM, Ralph Engels wrote:
> Aye im aware of the shortcommings allthough i havent used xp in
> quite a while, and newer with a fat table. Im not sure how cygwin
> normally handles situations where its installed on a system with a
> fat table but i suspected that it had some failsafes such as
> turning symlinks of in case the OS didnt support them ?.

No, these problems with native symlinks is why cygwin symlinks are
implemented differently.  (Cygwin can understand native symlinks and
junction points but it never creates them).

Moreover, it is precisely because cygwin symlinks are a cygwin-only
mechanism (and thus, not understood by "native" programs) that MSYS-1
completely disabled symlinks support: what good is it for msys to
create symlinks that the native programs it supports -- like MinGW gcc
-- can't understand them.

-- 
Chuck

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

On 27/09/11 08:20, Charles Wilson wrote:
> 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,

Surely the real issue is that native symlinks aren't supported by any
MSW version prior to Vista, irrespective of file system.  Prior to
Vista, we had reparse points on NTFS, (which might emulate symlinks to
some extent), but they certainly aren't semantically equivalent to POSIX
symlinks.

Now, Vista and Win7 symlinks are allegedly semantically equivalent to
POSIX symlinks, but I'm not entirely convinced of this, since...

> and (3) IIRC you have to have Administrator privilege to create
> native symlinks.

...you have to hold a symlink creation privilege which, by default, is
granted to administrators only.  I guess an administrator can grant it
to other users, but since I'm not an administrator for our corporate
systems, (my only exposure to Vista or later), and the administrator has
declined to grant me this privilege, native symlinks just don't work at
all, /for me/.

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

I agree.

-- 
Regards,
Keith.

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