New James Bond movie: You Only Reboot Twice.
-Sean P Murphy
On Wed, Jan 2, 2013 at 1:29 PM, Ryan Johnson
wrote:
> On 02/01/2013 11:24 AM, Aaron Schneider wrote:
>>
>> On 02/01/2013 19:21, Christopher Faylor wrote:
>>>
>>> But most likely you need to run rebaseall.
>>
>>
>> It was solved with ju
On 02/01/2013 11:24 AM, Aaron Schneider wrote:
On 02/01/2013 19:21, Christopher Faylor wrote:
But most likely you need to run rebaseall.
It was solved with just restarting the computer.
The Windows motto: "when in doubt, reboot"
FYI, it may be that you just hit a mintty session that had a
p
On Wed, Jan 02, 2013 at 07:24:09PM +0100, Aaron Schneider wrote:
>On 02/01/2013 19:21, Christopher Faylor wrote:
>> But most likely you need to run rebaseall.
>
>It was solved with just restarting the computer.
So, the lesson learned is that you always have to restart your computer
twice.
--
Prob
On 02/01/2013 19:21, Christopher Faylor wrote:
But most likely you need to run rebaseall.
It was solved with just restarting the computer.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
On Wed, Jan 02, 2013 at 07:17:32PM +0100, Aaron Schneider wrote:
>-bash: fork: retry: Resource temporarily unavailable
> 0 [main] bash 8080 child_info_fork::abort:
>C:\cygwin\bin\cyggcc_s-1.dll: Loaded to different address:
>parent(0x3D) != child(0x3E)
>-bash: fork: retry: Resource
On Thu, Apr 30, 2009 at 7:27 AM, Ken Brown
> A build script I was running failed because it had a command of > the form
> 'eval foo=bar time '.
That won't work because time is a special shell keyword, and as such
only recognized when it's the first word on the command line. The same
is true of al
On 4/30/2009 7:56 AM, Eric Blake wrote:
time is a special case. It is BOTH a bash reserved word and an external
command (assuming you've installed the external package). The difference
is what syntax you use.
Thanks for the explanation. My problem, obviously, is that I hadn't
installed the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ken Brown on 4/30/2009 5:27 AM:
> A build script I was running failed because it had a command of the form
> 'eval foo=bar time '. Here's a simple test case:
This is not cygwin specific.
>
> $ eval foo=bar time true
> -bash: time: comm
2009/4/30 Ken Brown :
> A build script I was running failed because it had a command of the form
> 'eval foo=bar time '. Here's a simple test case:
>
> $ eval foo=bar time true
> -bash: time: command not found
>
> It works fine without foo=bar:
>
> $ eval time true
>
> real 0m0.060s
> user 0
Arun Biyani wrote:
I just upgraded to the current bash. Now I am getting an error. I
reinstalled, rebooted
the machine. Still get the same error. The variable $HOME is set correctly.
> bash: /c/home/abiyani/.bash_login: line 7: syntax error: unexpected
end of file
>
> [EMAIL PROTECTED] ~
Igor Peshansky wrote:
Is there any particular reason you post the output of od on .bashrc when
the error was reported in .bash_login?
BTW, for the future, you might want to run "od -c" instead -- its output
is a bit more readable.
Igor
Igor & Dave,
Thx. It is a CR/LF problem. I had
On Tue, 26 Sep 2006, Arun Biyani wrote:
> Original Message
> Subject: Re: Bash problem - v3.1.17(8) - syntax error
> Date: Tue, 26 Sep 2006 12:17:34 -0700
> From: Arun Biyani <[EMAIL PROTECTED]>
> To: Dave Korn <[EMAIL PROTECTED]&
Original Message
Subject:Re: Bash problem - v3.1.17(8) - syntax error
Date: Tue, 26 Sep 2006 12:17:34 -0700
From: Arun Biyani <[EMAIL PROTECTED]>
To: Dave Korn <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Dave Korn wrote:
On 26
On 26 September 2006 20:11, Arun Biyani wrote:
> I just upgraded to the current bash. Now I am getting an error. I
> reinstalled, rebooted
> the machine. Still get the same error. The variable $HOME is set correctly.
Wrong line-ends most likely. Run d2u on it.
cheers,
DaveK
--
Can'
thank you all. There was an incredible reason for the problem: ActiveTcl
manipulated the TEXPATH variable and .exe was not reckognized eny more. Even
when I reinstalled Tcl, their uninstaller did not restore this variable.
After I restored the variable, everything worked again.
So this was not a
As requested at http://cygwin.com/bugs.html:
o Please describe how to reproduce the problem,
including a test case, if possible.
o Please include at least the version number of the
Cygwin release you are using along with the
operating system name and its version number,
for example, "cy
Janos,
A hint about how to diagnose this problem is to open a CMD.exe window an
enter the command to launch BASH there so you can see the diagnostics
(instead of having them displayed in a window that vanishes immediately).
If you have not modified the shortcut that Cygwin Setup adds to the
Pr
Janos,
A very general hint is that installing one or both of those other
applications changed your system's PATH environment variable in a way
that's causing some of BASH's start-up processing to fail. Possibly the
BASH startup processing is invoking a program or script whose name is that
of a
18 matches
Mail list logo
