On Jun 20 09:07, Earnie Boyd wrote:
> On Wed, Jun 19, 2013 at 4:25 PM, Charles Wilson wrote:
> >
> > I assume that, eventually and as-needed, a *small* number of additional
> > "hooks" could be added to other code paths than exec/spawn/etc -- such as
> > the aforementioned uname(3) thing. (One of t
On Wed, Jun 19, 2013 at 4:25 PM, Charles Wilson wrote:
>
> I assume that, eventually and as-needed, a *small* number of additional
> "hooks" could be added to other code paths than exec/spawn/etc -- such as
> the aforementioned uname(3) thing. (One of the "deltas" between cygwin and
> msys was msys
On 6/19/2013 1:45 PM, Christopher Faylor wrote:
I'm talking about providing hooks so that an add-on MSYS dll could
modify the windows command-line. Then we wouldn't care what MSYS does
with the command-line since it isn't a Cygwin DLL decision. The goal is
to allow a small DLL to hook into Cygw
On Jun 19 11:04, Earnie Boyd wrote:
> On Tue, Jun 18, 2013 at 2:40 PM, Алексей Павлов wrote:
> > I want to add MSYS functionality to Cygwin.
>
> One issue with that would be copyright assignment. Alexey has been in
> the MSYS code so someone who hasn't looked would need to implement
> similar fun
On 2013-06-19 12:57, Warren Young wrote:
Not all packages are cross-compiler-compatible.
Is that another way of saying that not all packages use autotools? :)
autotools can certainly make cross-compiling easier than most other
build systems, but it's not a guarantee either. For instance, an
On 6/19/2013 07:31, Charles Wilson wrote:
http://www.mingw.org/wiki/Posix_path_conversion
That's good info.
I'm glad to see that relative paths are never molested. I tried for a
while to confuse Cygwin and native Windows programs using relative
paths, and failed to find a case where the pa
On Wed, Jun 19, 2013 at 11:30:11AM -0600, Warren Young wrote:
>On 6/18/2013 20:02, Christopher Faylor wrote:
>> On Tue, Jun 18, 2013 at 04:04:06PM -0600, Warren Young wrote:
>>> It would be possible, though somewhat evil, for Cygwin's exec()
>>> implementation to peek at the DLL dependency list of
On Jun 19 10:53, Warren Young wrote:
> On 6/19/2013 03:05, Corinna Vinschen wrote:
> >
> >Done. Please have a look:
> >http://cygwin.com/faq.html#faq.using.multiple-copies
> >http://cygwin.com/faq.html#faq.using.third-party.multiple-copies
>
> Thanks!
>
> It looks like 4.22 is still out of date,
On 6/18/2013 20:02, Christopher Faylor wrote:
On Tue, Jun 18, 2013 at 04:04:06PM -0600, Warren Young wrote:
It would be possible, though somewhat evil, for Cygwin's exec()
implementation to peek at the DLL dependency list of a program before
starting it, and from that infer whether it should aut
On 6/19/2013 03:05, Corinna Vinschen wrote:
Done. Please have a look:
http://cygwin.com/faq.html#faq.using.multiple-copies
http://cygwin.com/faq.html#faq.using.third-party.multiple-copies
Thanks!
It looks like 4.22 is still out of date, though. The "must be run
serially" bit, at least, con
On Tue, Jun 18, 2013 at 2:40 PM, Алексей Павлов wrote:
> I want to add MSYS functionality to Cygwin.
One issue with that would be copyright assignment. Alexey has been in
the MSYS code so someone who hasn't looked would need to implement
similar functionality.
--
Earnie
-- https://sites.google.
On 6/18/2013 10:05 PM, Christopher Faylor wrote:
Let me state it again: Corinna and I have been having private discussion
about this and are open to talking about the possibility of adding
MSYS capability to Cygwin. I'm advocating adding hooks to the DLL
which would accomplish that.
Wow, that'
On 6/18/2013 6:04 PM, Warren Young wrote:
It would be possible, though somewhat evil, for Cygwin's exec()
implementation to peek at the DLL dependency list of a program before
starting it, and from that infer whether it should automatically
translate paths.
The I/O hit this would cause would be
2013/6/19 Corinna Vinschen :
> On Jun 19 10:53, Алексей Павлов wrote:
>> Today I investigate in this direction and find that logic works well
>> except one line in spawn.cc that I think can be fixed without break
>> anything.
>>
>> Index: cygwin/spawn.cc
>> =
On Jun 19 10:53, Алексей Павлов wrote:
> Today I investigate in this direction and find that logic works well
> except one line in spawn.cc that I think can be fixed without break
> anything.
>
> Index: cygwin/spawn.cc
> ===
> RCS fil
On Jun 19 10:15, Corinna Vinschen wrote:
> On Jun 18 22:03, Christopher Faylor wrote:
> > On Tue, Jun 18, 2013 at 03:24:52PM -0600, Warren Young wrote:
> > >On 6/18/2013 13:31, Christopher Faylor wrote:
> > >> On Tue, Jun 18, 2013 at 01:10:06PM -0600, Warren Young wrote:
> > 3. In MSYS mode Cy
On Jun 18 22:03, Christopher Faylor wrote:
> On Tue, Jun 18, 2013 at 03:24:52PM -0600, Warren Young wrote:
> >On 6/18/2013 13:31, Christopher Faylor wrote:
> >> On Tue, Jun 18, 2013 at 01:10:06PM -0600, Warren Young wrote:
> 3. In MSYS mode Cygwin need to be very portable
> >>>
> >>> It would
I want point all who read this ML to mingw-w64 ML discussion about MSYS:
http://sourceforge.net/mailarchive/message.php?msg_id=31008339
Also I want to say that all changes that I do in Cygwin DLL (except
symlink-copy) do not break any Cygwin stuff and only applied to
non-cygwin applications. For C
2013/6/19 Christopher Faylor wrote:
> On Tue, Jun 18, 2013 at 04:04:06PM -0600, Warren Young wrote:
>>On 6/18/2013 13:30, ??? ?? wrote:
>>> 2013/6/18 Warren Young :
On 6/18/2013 12:40, ??? ?? wrote:
>
> 1. The correct definition of executables belonging to Cygwin DLL.
>
On Tue, Jun 18, 2013 at 05:29:04PM -0400, Charles Wilson wrote:
>However, discussing "not-cygwin" on the cygwin list(s) is A Bad Idea, so
>you should go "over there" and talk it out with those guys.
Let me state it again: Corinna and I have been having private discussion
about this and are open t
On Tue, Jun 18, 2013 at 03:24:52PM -0600, Warren Young wrote:
>On 6/18/2013 13:31, Christopher Faylor wrote:
>> On Tue, Jun 18, 2013 at 01:10:06PM -0600, Warren Young wrote:
3. In MSYS mode Cygwin need to be very portable
>>>
>>> It would indeed be nice to have a portable Cygwin. That is, one
On Tue, Jun 18, 2013 at 04:04:06PM -0600, Warren Young wrote:
>On 6/18/2013 13:30, ??? ?? wrote:
>> 2013/6/18 Warren Young :
>>> On 6/18/2013 12:40, ??? ?? wrote:
1. The correct definition of executables belonging to Cygwin DLL.
>>>
>>> Can you give an example of what you
On 6/18/2013 16:04, Warren Young wrote:
You're proposing some kind of global search-and-replace
operation, which will inevitably turn into a Whac-a-Mole game.
I just thought of an example. How many POSIX paths are in this
perfectly legal command, which invokes a native Windows executable?
On 6/18/2013 16:04, Warren Young wrote:
$ cd /bin
$ mv ln.exe sane-ln.exe
$ ln -s cp.exe ln.exe
Of course, that final step should be
$ cp cp.exe ln.exe
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 6/18/2013 13:30, Алексей Павлов wrote:
2013/6/18 Warren Young :
On 6/18/2013 12:40, Алексей Павлов wrote:
1. The correct definition of executables belonging to Cygwin DLL.
Can you give an example of what you mean here?
All cygwin applications depends on cygwin1.dll. We need to translate
On 6/18/2013 2:40 PM, Алексей Павлов wrote:
I want to add MSYS functionality to Cygwin.
More than 10 years ago Cygwin 1.3 had forked to MSYS. But now this
MSYS is very old and don't has any support for it.
...
I want to hear your opinions about how it can be implemented in Cygwin codebase.
G
On 6/18/2013 13:31, Christopher Faylor wrote:
On Tue, Jun 18, 2013 at 01:10:06PM -0600, Warren Young wrote:
3. In MSYS mode Cygwin need to be very portable
It would indeed be nice to have a portable Cygwin. That is, one that
could be run from a copied directory or USB key, without being forma
[I'm being a reluctant explicator here]
On Tue, Jun 18, 2013 at 01:10:06PM -0600, Warren Young wrote:
>On 6/18/2013 12:40, ?? wrote:
>>
>> 1. The correct definition of executables belonging to Cygwin DLL.
>
>Can you give an example of what you mean here?
>
>This must be so
2013/6/18 Warren Young :
> On 6/18/2013 12:40, Алексей Павлов wrote:
>>
>>
>> 1. The correct definition of executables belonging to Cygwin DLL.
>
>
> Can you give an example of what you mean here?
>
All cygwin applications depends on cygwin1.dll. We need to translate
arguments only for non-cygwin a
On 6/18/2013 12:40, Алексей Павлов wrote:
1. The correct definition of executables belonging to Cygwin DLL.
Can you give an example of what you mean here?
This must be some kind of translation error, since executables never
belong to DLLs. The reverse is sometimes true, but mostly not.
2
On Tue, Jun 18, 2013 at 10:40:36PM +0400, ??? ?? wrote:
>Hi everybody!
>
>I want to add MSYS functionality to Cygwin.
>More than 10 years ago Cygwin 1.3 had forked to MSYS. But now this
>MSYS is very old and don't has any support for it.
>Primary goal of MSYS is to provide environment with
31 matches
Mail list logo
