-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 18:51, Alexpux wrote:
среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал:
On Jun 12 15:50, Alexpux wrote:
среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
On Jun 11 21:10, Алексей Павлов wrote:
4. Replaced Cygwin
On Jun 19 12:08, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 18:51, Alexpux wrote:
среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал:
On Jun 12 15:50, Alexpux wrote:
среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
On Jun 11 21:10, Алексей
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 12:57, Corinna Vinschen wrote:
On Jun 19 12:08, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 18:51, Alexpux wrote:
среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал:
On Jun 12 15:50, Alexpux wrote:
On Jun 19 13:32, LRN wrote:
On 19.06.2013 12:57, Corinna Vinschen wrote:
On Jun 19 12:08, LRN wrote:
To be fair here, i've tried the MSYS=winsymlinks:nativestrict, and first
thing i hit was AC_PROG_LN_S. That macro explicitly refuses to use `ln
- -s' provided by MSYS or Cygwin, asking for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 13:55, Corinna Vinschen wrote:
On Jun 19 13:32, LRN wrote:
On 19.06.2013 12:57, Corinna Vinschen wrote:
On Jun 19 12:08, LRN wrote:
To be fair here, i've tried the MSYS=winsymlinks:nativestrict, and first
thing i hit was
On Jun 19 14:28, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 13:55, Corinna Vinschen wrote:
On Jun 19 13:32, LRN wrote:
On 19.06.2013 12:57, Corinna Vinschen wrote:
On Jun 19 12:08, LRN wrote:
To be fair here, i've tried the MSYS=winsymlinks:nativestrict,
On Jun 19 12:34, Corinna Vinschen wrote:
On Jun 19 14:28, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 13:55, Corinna Vinschen wrote:
On Jun 19 13:32, LRN wrote:
On 19.06.2013 12:57, Corinna Vinschen wrote:
On Jun 19 12:08, LRN wrote:
To be fair
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19 12:34, Corinna Vinschen wrote:
On Jun 19 14:28, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 13:55, Corinna Vinschen wrote:
On Jun 19 13:32, LRN wrote:
On 19.06.2013 12:57, Corinna Vinschen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 15:54, Ruben Van Boxem wrote:
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19 12:34, Corinna Vinschen wrote:
On Jun 19 14:28, LRN wrote:
[...]
and that you're using winsymlinks:nativestrict?
No. I'm using any one of
2013/6/19 LRN lrn1...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 15:54, Ruben Van Boxem wrote:
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19 12:34, Corinna Vinschen wrote:
On Jun 19 14:28, LRN wrote:
[...]
and that you're using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 16:11, Ruben Van Boxem wrote:
2013/6/19 LRN lrn1...@gmail.com
On 19.06.2013 15:54, Ruben Van Boxem wrote:
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19 12:34, Corinna Vinschen wrote:
On Jun 19 14:28, LRN wrote:
[...]
On Jun 19 16:01, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 15:54, Ruben Van Boxem wrote:
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19 12:34, Corinna Vinschen wrote:
On Jun 19 14:28, LRN wrote:
[...]
and that you're using
On 6/19/2013 20:11, Ruben Van Boxem wrote:
Call me naive, but why not create the link to non-existent ... thing (which
should possible, just choose file or directory; it doesn't matter because
its not there)... then when the actual thing is created, change the link to
conform to the new
On Jun 19 14:11, Ruben Van Boxem wrote:
2013/6/19 LRN lrn1...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 15:54, Ruben Van Boxem wrote:
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19 12:34, Corinna Vinschen wrote:
On Jun 19 14:28, LRN
On Jun 19 14:36, Corinna Vinschen wrote:
On Jun 19 16:01, LRN wrote:
Cygwin emulates untyped linking (ln -s) by checking the type of the
target and creating the link of the right type. If the target doesn't
exist, you're screwed.
Not really screwed. But if the target doesn't exist, you
Usually it's because Cygwin is usually a lot slower than native for IO
heavy operations. Projects (such as the Android NDK) that supply
Cygwin-based compilers usually try to migrate to native ASAP, viewing the
Cygwin-based tools as a stop-gap measure.
On Wed, Jun 19, 2013 at 2:05 PM, Corinna
On Jun 19 14:14, Ray Donnelly wrote:
On Wed, Jun 19, 2013 at 2:05 PM, Corinna Vinschen wrote:
Btw., this is one reason why I don't understand the desire to use native
tools. If you can get a working POSIXy build environment for free, why
do you want to use native tools which only generate
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19 14:11, Ruben Van Boxem wrote:
2013/6/19 LRN lrn1...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.06.2013 15:54, Ruben Van Boxem wrote:
2013/6/19 Corinna Vinschen vinsc...@redhat.com
On Jun 19
On Jun 19 15:27, Ruben Van Boxem wrote:
2013/6/19 Corinna Vinschen
And there's another problem with this approach. Unfortunately you can't
overwrite symlinks atomically. You have to remove the old symlink and
create a new one. In the time between removing and recreation, another
On Jun 19 15:24, Corinna Vinschen wrote:
On Jun 19 14:14, Ray Donnelly wrote:
On Wed, Jun 19, 2013 at 2:05 PM, Corinna Vinschen wrote:
Btw., this is one reason why I don't understand the desire to use native
tools. If you can get a working POSIXy build environment for free, why
do you
Hi Алексей,
On Jun 11 21:10, Алексей Павлов wrote:
Cygwin and MSYS have significantly different goals (even if MSYS is
entirely based on Cygwin).
My understanding is that MSYS is the minimal shell required to run
autotools and get sources from internet from different repositories.
I'm
On Jun 12 12:47, Corinna Vinschen wrote:
6. Perhaps remove /cygdrive prefix to simply typing paths. Mostly this is
to retain compatibility with MSYS-enabled software that makes assumptions
about /c/ being equivalent to C:/
It's not necessary at all to change the Cygwin/MSYS2 DLL to make
--
Alexpux
Отправлено с помощью Sparrow (http://www.sparrowmailapp.com/?sig)
среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
Hi Алексей,
On Jun 11 21:10, Алексей Павлов wrote:
Cygwin and MSYS have significantly different goals (even if MSYS is
entirely based on Cygwin).
--
Alexpux
Отправлено с помощью Sparrow (http://www.sparrowmailapp.com/?sig)
среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
Hi Алексей,
On Jun 11 21:10, Алексей Павлов wrote:
Cygwin and MSYS have significantly different goals (even if MSYS is
entirely based on Cygwin).
2013/6/12 LRN lrn1...@gmail.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 14:47, Corinna Vinschen wrote:
Hi Алексей,
On Jun 11 21:10, Алексей Павлов wrote:
MSYS includes the following changes to Cygwin to support using native Win32
programs:
1. Automatic path mangling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 15:57, Ray Donnelly wrote:
I wonder if it would be possible to have a plugin system to allow for
the behaviour changes we need to cygwin.dll, so msys.dll exists and
only handles those parts and cygwin.dll loads that as a plugin, if
On Jun 12 16:00, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 14:47, Corinna Vinschen wrote:
Hi Алексей,
On Jun 11 21:10, Алексей Павлов wrote:
MSYS includes the following changes to Cygwin to support using native Win32
programs:
1. Automatic path
On Jun 12 15:50, Alexpux wrote:
среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
On Jun 11 21:10, Алексей Павлов wrote:
MSYS includes the following changes to Cygwin to support using native
Win32
programs:
1. Automatic path mangling of command line arguments and
Ok, We're back to asking for a plugin with a clearly defined interface for
env. var and path translation; despite LRNs reasonable objections I think
it might be the only acceptable solution?
.. that way we can continue to speculate (as MSYS always has) about what's
a path and what isn't and also
On Jun 12 15:11, Ray Donnelly wrote:
Ok, We're back to asking for a plugin with a clearly defined interface for
env. var and path translation; despite LRNs reasonable objections I think
it might be the only acceptable solution?
.. that way we can continue to speculate (as MSYS always has)
--
Alexpux
Отправлено с помощью Sparrow (http://www.sparrowmailapp.com/?sig)
среда, 12 июня 2013 г. в 18:33, Corinna Vinschen написал:
On Jun 12 15:11, Ray Donnelly wrote:
Ok, We're back to asking for a plugin with a clearly defined interface for
env. var and path translation; despite
--
Alexpux
Отправлено с помощью Sparrow (http://www.sparrowmailapp.com/?sig)
среда, 12 июня 2013 г. в 18:00, Corinna Vinschen написал:
On Jun 12 15:50, Alexpux wrote:
среда, 12 июня 2013 г. в 14:47, Corinna Vinschen написал:
On Jun 11 21:10, Алексей Павлов wrote:
MSYS includes the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 17:50, Corinna Vinschen wrote:
On Jun 12 16:00, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.06.2013 14:47, Corinna Vinschen wrote:
Hi Алексей,
On Jun 11 21:10, Алексей Павлов wrote:
MSYS includes the following
Am 12.06.2013 17:33, schrieb LRN:
On 12.06.2013 17:50, Corinna Vinschen wrote:
On Jun 12 16:00, LRN wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 12.06.2013 14:47, Corinna Vinschen wrote:
Hi Алексей,
On Jun 11 21:10, Алексей Павлов wrote:
MSYS includes the following changes to
On Jun 12, 2013 11:53 AM, Rainer Emrich sf.rai...@emrich-ebersheim.de
wrote:
Am 12.06.2013 17:33, schrieb LRN:
On 12.06.2013 17:50, Corinna Vinschen wrote:
On Jun 12 16:00, LRN wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 12.06.2013 14:47, Corinna Vinschen wrote:
Hi
On Jun 10 13:19, Алексей Павлов wrote:
Corinna,
I upload 3rdparty sources that I use in MSYS2 to
https://sourceforge.net/projects/msys2/files/Sources/
Thank you.
Corinna
--
This SF.net email is sponsored by Windows:
Hi Алексей,
On Jun 10 10:19, Corinna Vinschen wrote:
On Jun 8 12:49, Алексей Павлов wrote:
I recreate git repository on msys2.sf.net.
Now master branch point to MSYS2 source and when you go to code page on
sf.net you get page with MSYS2 source.
Thank you, that's much better. This
2013/6/11 Corinna Vinschen vinsc...@redhat.com
Hi Алексей,
On Jun 10 10:19, Corinna Vinschen wrote:
On Jun 8 12:49, Алексей Павлов wrote:
I recreate git repository on msys2.sf.net.
Now master branch point to MSYS2 source and when you go to code page on
sf.net you get page with
Hi Алексей,
On Jun 8 01:56, Алексей Павлов wrote:
2013/6/7 Corinna Vinschen wrote:
A final note: I'm not opposing the fork. Under the GPL it's your
perfect right to do so, as long as you adhere to the license
requirements. But that doesn't mean I have to understand it. If the
DLL
On Jun 11 13:26, Corinna Vinschen wrote:
Other than that I'm rather puzzled as to what MSYS2 is about, other than
to duplicate developer efforts and to split communities. Apart from
your perfect right to fork, you might nevertheless understand that I'm a
bit annoyed. Especially given the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 15:26, Corinna Vinschen wrote:
Hi Алексей,
On Jun 8 01:56, Алексей Павлов wrote:
2013/6/7 Corinna Vinschen wrote:
A final note: I'm not opposing the fork. Under the GPL it's your
perfect right to do so, as long as you adhere to
I for one am hugely appreciative of all the hard work that Corinna, Kai,
redhat, the mingw-w64 team and also Alexey has put into both Cygwin and
MSYS2.
Cygwin and MSYS2 exist for different, mutually exclusive goals. Anything we
can reasonably do on MSYS2 (credits, thanks printed at each login,
On Jun 11 15:43, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 15:26, Corinna Vinschen wrote:
Hi Алексей,
On Jun 8 01:56, Алексей Павлов wrote:
2013/6/7 Corinna Vinschen wrote:
A final note: I'm not opposing the fork. Under the GPL it's your
perfect
On Jun 11 12:58, Ray Donnelly wrote:
I for one am hugely appreciative of all the hard work that Corinna, Kai,
redhat, the mingw-w64 team and also Alexey has put into both Cygwin and
MSYS2.
Cygwin and MSYS2 exist for different, mutually exclusive goals. Anything we
I fail to see that. MSYS2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 15:58, Ray Donnelly wrote:
MSYS itself was badly fragmented by the msysgit
project which uses an even earlier version of MSYS than the latest one
which is also missing important tools such as install.exe and something
has to be done
On Tue, Jun 11, 2013 at 1:25 PM, LRN lrn1...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 15:58, Ray Donnelly wrote:
MSYS itself was badly fragmented by the msysgit
project which uses an even earlier version of MSYS than the latest one
which is also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 16:04, Corinna Vinschen wrote:
On Jun 11 15:43, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 15:26, Corinna Vinschen wrote:
Hi Алексей,
On Jun 8 01:56, Алексей Павлов wrote:
2013/6/7 Corinna Vinschen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 16:14, Corinna Vinschen wrote:
On Jun 11 12:58, Ray Donnelly wrote:
I for one am hugely appreciative of all the hard work that Corinna, Kai,
redhat, the mingw-w64 team and also Alexey has put into both Cygwin and
MSYS2.
Cygwin and
On Jun 11 12:58, Ray Donnelly wrote:
I for one am hugely appreciative of all the hard work that Corinna, Kai,
redhat, the mingw-w64 team and also Alexey has put into both Cygwin and
MSYS2.
Cygwin and MSYS2 exist for different, mutually exclusive goals. Anything
we
I fail to see that.
On Jun 11 16:59, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 16:14, Corinna Vinschen wrote:
On Jun 11 12:58, Ray Donnelly wrote:
I for one am hugely appreciative of all the hard work that Corinna, Kai,
redhat, the mingw-w64 team and also Alexey has put into
On Jun 11 16:42, m...@morous.org wrote:
On Jun 11 12:58, Ray Donnelly wrote:
I for one am hugely appreciative of all the hard work that Corinna, Kai,
redhat, the mingw-w64 team and also Alexey has put into both Cygwin and
MSYS2.
Cygwin and MSYS2 exist for different, mutually exclusive
2013/6/11 Corinna Vinschen vinsc...@redhat.com:
On Jun 11 16:59, LRN wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11.06.2013 16:14, Corinna Vinschen wrote:
On Jun 11 12:58, Ray Donnelly wrote:
I for one am hugely appreciative of all the hard work that Corinna, Kai,
redhat,
On Jun 11 16:52, LRN wrote:
And why exactly is that a problem? The cross compiler is creating
the exact same code as a native-like compile with the same version.
Cross-compiling is somewhat more tricky. Also do remember that MSYS1 is
rather old, cross-compiling was even trickier back then.
Corrina,
My user-based perspectives embedded below for your consideration...
On Jun 8 01:56, Алексей Павлов wrote:
2013/6/7 Corinna Vinschen wrote:
A final note: I'm not opposing the fork. Under the GPL it's your
perfect right to do so, as long as you adhere to the license
Cygwin and MSYS have significantly different goals (even if MSYS is
entirely based on Cygwin).
My understanding is that MSYS is the minimal shell required to run
autotools and get sources from internet from different repositories.
MSYS is about porting Unix programs to Windows without having a
Hi Алексей,
On Jun 8 12:49, Алексей Павлов wrote:
I recreate git repository on msys2.sf.net.
Now master branch point to MSYS2 source and when you go to code page on
sf.net you get page with MSYS2 source.
Thank you, that's much better. This allows an unaware user to access
the correct
Corinna,
I upload 3rdparty sources that I use in MSYS2 to
https://sourceforge.net/projects/msys2/files/Sources/
Regards, Alexey.
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate
I recreate git repository on msys2.sf.net.
Now master branch point to MSYS2 source and when you go to code page on
sf.net you get page with MSYS2 source.
--
How ServiceNow helps IT people transform IT departments:
1. A
On Jun 7 00:17, Алексей Павлов wrote:
Hi, everybody!
I have work on creating MSYS2 based on latest Cygwin sources and now create
archives with alpha version.
Links:
32-bit:
Hello,
On 07 Jun, Corinna Vinschen wrote :
I checked the git source repository on sourceware and found that there
is absolutely *no* change compared to the Cygwin source repository, none
git checkout -b msys-2.1 origin/msys2-1.0-dev
There are a lot of changes. 235 to be exact...
Best
On Jun 7 17:34, Jean-Baptiste Kempf wrote:
Hello,
On 07 Jun, Corinna Vinschen wrote :
I checked the git source repository on sourceware and found that there
is absolutely *no* change compared to the Cygwin source repository, none
git checkout -b msys-2.1 origin/msys2-1.0-dev
There
On 07 Jun, Corinna Vinschen wrote :
On Jun 7 17:34, Jean-Baptiste Kempf wrote:
Hello,
On 07 Jun, Corinna Vinschen wrote :
I checked the git source repository on sourceware and found that there
is absolutely *no* change compared to the Cygwin source repository, none
git checkout
On Jun 7 17:57, Jean-Baptiste Kempf wrote:
On 07 Jun, Corinna Vinschen wrote :
On Jun 7 17:34, Jean-Baptiste Kempf wrote:
Hello,
On 07 Jun, Corinna Vinschen wrote :
I checked the git source repository on sourceware and found that there
is absolutely *no* change compared to
63 matches
Mail list logo