Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 10:55:40AM -0700, Jerry DeLisle wrote:
Christopher Faylor wrote:
--- snip ---
I will try the manual process you suggested after I figure out how to get the
snapshot and when it is available.
Bare in mind that I am using the broken environment t
On Mon, Jul 06, 2009 at 10:55:40AM -0700, Jerry DeLisle wrote:
>Christopher Faylor wrote:
>--- snip ---
>>> I will try the manual process you suggested after I figure out how to get
>>> the
>>> snapshot and when it is available.
>>
>
>Bare in mind that I am using the broken environment to do thi
Christopher Faylor wrote:
--- snip ---
I will try the manual process you suggested after I figure out how to get the
snapshot and when it is available.
Bare in mind that I am using the broken environment to do this. I managed to
extract the snapshot and replace the cygwin1.dll while not run
On Mon, Jul 06, 2009 at 10:00:22AM -0700, Jerry DeLisle wrote:
>Maybe this warrants a cygwin1.dll release.
It would be premature to make a release without verifying that it fixes the
problem.
>I will try the manual process you suggested after I figure out how to get the
>snapshot and when it is
Jerry DeLisle wrote:
> I will try the manual process you suggested after I figure out how to
> get the snapshot and when it is available.
Look here: http://cygwin.com/snapshots/
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cy
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 12:32:16AM -0400, Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
Jerry DeLisle wrote:
I am making the switch to 1.7. I started with a clean windows (nt4)
environment and went through the usual run of setup
On Mon, Jul 06, 2009 at 12:32:16AM -0400, Christopher Faylor wrote:
>On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
>>Jerry DeLisle wrote:
>>> I am making the switch to 1.7. I started with a clean windows (nt4)
>>> environment and went through the usual run of setup-1.7 downloaded toda
Christopher Faylor wrote:
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
Jerry DeLisle wrote:
I am making the switch to 1.7. I started with a clean windows (nt4)
environment and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get initi
On Mon, Jul 06, 2009 at 05:20:41AM +0100, Dave Korn wrote:
>Jerry DeLisle wrote:
>> I am making the switch to 1.7. I started with a clean windows (nt4)
>> environment and went through the usual run of setup-1.7 downloaded today.
>>
>> All appears fine, but bash does not get initialized.
>>
>> pw
Jerry DeLisle wrote:
> I am making the switch to 1.7. I started with a clean windows (nt4)
> environment and went through the usual run of setup-1.7 downloaded today.
>
> All appears fine, but bash does not get initialized.
>
> pwd is /usr/bin
>
> path is not set
>
> home directory is not crea
Jerry DeLisle wrote:
Dave Korn wrote:
Jerry DeLisle wrote:
Well, I am moving to this thread now.
Jerry, can I show you something you must not have realised about how
email
threading works?
Thank you for pointing this out. I usually don't use the thread view in
my mail client. I wi
I am making the switch to 1.7. I started with a clean windows (nt4) environment
and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get initialized.
pwd is /usr/bin
path is not set
home directory is not created
These are all taken care of nicely
Dave Korn wrote:
Jerry DeLisle wrote:
Well, I am moving to this thread now.
Jerry, can I show you something you must not have realised about how email
threading works?
Thank you for pointing this out. I usually don't use the thread view in my mail
client. I will avoid this breakage i
Jerry DeLisle wrote:
> Well, I am moving to this thread now.
Jerry, can I show you something you must not have realised about how email
threading works?
When you hit "Reply" to an existing post, your mailer adds "In-Reply-To:"
and/or "References:" headers to your reply, so that other maile
are having? Apparently it doesn't.
It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION which
is known to occur on Windows 7 with your not-so-serious "Bash
initialization w/cygwin-1.7".
My release of binutils means that Eric can respin bash. It doesn't mean
that, if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jerry DeLisle on 7/4/2009 7:10 PM:
> All appears fine, but bash does not get initialized.
And this has already been brought up. I'm hoping that today's binutils
release solves things, although I won't have a chance to release an
updated
I am making the switch to 1.7. I started with a clean windows (nt4) environment
and went through the usual run of setup-1.7 downloaded today.
All appears fine, but bash does not get initialized.
pwd is /usr/bin
path is not set
home directory is not created
These are all taken care of nicely
17 matches
Mail list logo
