On 30 March 2007 10:20, Corinna Vinschen wrote:
> On Mar 30 09:33, Dave Korn wrote:
>> On 30 March 2007 08:58, Corinna Vinschen wrote:
>>> Btw., do they provide the source codes for the Cygwin DLL and their
>>> tools?
>>
>>
>> ... because rebuilding their tools from source into your standard
On Mar 30 09:33, Dave Korn wrote:
> On 30 March 2007 08:58, Corinna Vinschen wrote:
>
> > On Mar 30 00:59, Steve M. Robbins wrote:
> >> Dear Phil Betts et al,
> >>
> >> Thank you for the humourous "soapbox" lecture. I do recognize the
> >> sentiment and I'm all for improving the world as much as
On 30 March 2007 08:58, Corinna Vinschen wrote:
> On Mar 30 00:59, Steve M. Robbins wrote:
>> Dear Phil Betts et al,
>>
>> Thank you for the humourous "soapbox" lecture. I do recognize the
>> sentiment and I'm all for improving the world as much as the next
>> guy. I do my bit volunteering for
On Mar 30 00:59, Steve M. Robbins wrote:
> Dear Phil Betts et al,
>
> Thank you for the humourous "soapbox" lecture. I do recognize the
> sentiment and I'm all for improving the world as much as the next
> guy. I do my bit volunteering for Debian. When it comes to windows,
> however, I just wan
Dear Phil Betts et al,
Thank you for the humourous "soapbox" lecture. I do recognize the
sentiment and I'm all for improving the world as much as the next
guy. I do my bit volunteering for Debian. When it comes to windows,
however, I just want to get my work done.
To answer your question, "can
Igor Peshansky wrote on Thursday, March 29, 2007 2:27 PM::
> On Thu, 29 Mar 2007, Christopher Faylor wrote:
>
>> On Thu, Mar 29, 2007 at 12:34:07PM +0100, Phil Betts wrote:
>>>
>>> Any 3PP that forces one to use their (inevitably out of date)
>>> version of cygwin (and thereby killing the offici
On Thu, 29 Mar 2007, Christopher Faylor wrote:
> On Thu, Mar 29, 2007 at 12:34:07PM +0100, Phil Betts wrote:
> >
> >Any 3PP that forces one to use their (inevitably out of date) version
> >of cygwin (and thereby killing the official installation) is IMO broken
> >and the issue should be taken up w
On Thu, Mar 29, 2007 at 02:11:40PM +0200, J?rg Schaible wrote:
>Phil Betts wrote on Thursday, March 29, 2007 1:34 PM:
>>
>>Any 3PP that forces one to use their (inevitably out of date) version
>>of cygwin (and thereby killing the official installation) is IMO broken
>>and the issue should be taken
Phil Betts wrote on Thursday, March 29, 2007 1:34 PM:
[snip]
>
> Any 3PP that forces one to use their (inevitably out of date) version
> of cygwin (and thereby killing the official installation) is
> IMO broken
> and the issue should be taken up with them. At the very least, it
> shows they ha
On Thu, Mar 29, 2007 at 12:34:07PM +0100, Phil Betts wrote:
>
>Any 3PP that forces one to use their (inevitably out of date) version
>of cygwin (and thereby killing the official installation) is IMO broken
>and the issue should be taken up with them. At the very least, it
>shows they have such li
Steve M. Robbins wrote on Thursday, March 29, 2007 6:05 AM::
> Howdy,
>
> I had installed cygwin and used it for some months. Then I had to
> install another tool (crestron SIMPL+ compiler) and discovered that
> cygwin no longer worked. It turns out that the SIMPL+ compiler is
> based around a
Howdy,
I had installed cygwin and used it for some months. Then I had to
install another tool (crestron SIMPL+ compiler) and discovered that
cygwin no longer worked. It turns out that the SIMPL+ compiler is
based around a cygwin gcc cross compiler. So I need to have two
simultaneous cygwin envi
On 27 March 2006 16:44, Brian Hawkins wrote:
> OK please clarify how I commandeered a thread? I addressed my email to
> the cygwin list and set my own subject. I was not replying to any other
> thread.
If you weren't replying to any other thread, why did you send the following
headers with yo
Alexander Herrmann wrote:
> On 3/27/06, Igor Peshansky <[EMAIL PROTECTED]> wrote:
>> On Sun, 26 Mar 2006, Larry Hall (Cygwin) wrote:
>>> Brian Hawkins wrote:
[snip]
>>> FWIW, if you want something similar to symbolic links for
>>> directories and you're running W2K or above with NTFS, you can use
>
switching development environments.
I posted my comments because there may be someone out there who will say
"Hey that will work for me too."
Brian
Larry Hall (Cygwin) wrote:
Brian Hawkins wrote:
Just FYI. I found a pretty good way to manage multiple cygwin installs.
I use the win
Dankeschoen
On 3/27/06, Markus Schönhaber <[EMAIL PROTECTED]> wrote:
> Alexander Herrmann wrote:
> > On 3/27/06, Igor Peshansky <[EMAIL PROTECTED]> wrote:
> > > On Sun, 26 Mar 2006, Larry Hall (Cygwin) wrote:
> > > > Brian Hawkins wrote:
> > > > See the "junction" utility from www.sysinternal.com
Alexander Herrmann wrote:
> On 3/27/06, Igor Peshansky <[EMAIL PROTECTED]> wrote:
> > On Sun, 26 Mar 2006, Larry Hall (Cygwin) wrote:
> > > Brian Hawkins wrote:
> > > See the "junction" utility from www.sysinternal.com if you're
> > > interested in this.
>
> This link is broken(@ least for me) take
On 3/27/06, Igor Peshansky <[EMAIL PROTECTED]> wrote:
> On Sun, 26 Mar 2006, Larry Hall (Cygwin) wrote:
>
> > Brian Hawkins wrote:
> > > Just FYI. I found a pretty good way to manage multiple cygwin installs.
> > >
> > > I use the windows subst comma
On Sun, 26 Mar 2006, Larry Hall (Cygwin) wrote:
> Brian Hawkins wrote:
> > Just FYI. I found a pretty good way to manage multiple cygwin installs.
> >
> > I use the windows subst command.
> >
> > It works like this. Create a directory c:\cyginstalls. Then bene
> From: Larry Hall (Cygwin)
> Sent: Sunday, March 26, 2006 10:42 PM
> To: cygwin@cygwin.com
> Subject: Re: Multiple cygwin installs
>
> Brian Hawkins wrote:
> > Just FYI. I found a pretty good way to manage multiple
> cygwin installs.
> >
> > I use the w
Brian Hawkins wrote:
Just FYI. I found a pretty good way to manage multiple cygwin installs.
I use the windows subst command.
It works like this. Create a directory c:\cyginstalls. Then beneath it
create a directory for each cygwin install you want like cygwin1,
cygwin2 whatever. Then
Just FYI. I found a pretty good way to manage multiple cygwin installs.
I use the windows subst command.
It works like this. Create a directory c:\cyginstalls. Then beneath it
create a directory for each cygwin install you want like cygwin1,
cygwin2 whatever. Then use the subst command
At 07:53 AM 12/3/2001, Brian Genisio wrote:
>Hello all,
>
>Is there any way to maintain multiple cygwin installs? I understand that I can
>simply install cygwin in a separate directory, but there is one problem I run
>into : the registry.
>
>When you install cygwin,
Hello all,
Is there any way to maintain multiple cygwin installs? I understand that I can
simply install cygwin in a separate directory, but there is one problem I run
into : the registry.
When you install cygwin, it creates a "Cygnus Solutions" key tree in HKCU and
HKLM. If you
24 matches
Mail list logo
