-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to ram001 on 2/3/2007 5:17 PM:
> Hi
>
> I am new to cygwin. When i am trying to execute my cshell. It is throwing
> error as bash:csh:command not found .how to move to bash shell. I am trying
> to move to ksh sell when i am typing ksh on the
Hi
I am new to cygwin. When i am trying to execute my cshell. It is throwing
error as bash:csh:command not found .how to move to bash shell. I am trying
to move to ksh sell when i am typing ksh on the command promt then it
showing the same error as command promt .I Installed Cygwin thrice . i stu
On Sat, Feb 03, 2007 at 01:54:50PM -0700, Morgan Gangwere wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>jgbk9 wrote:
>> Despite warnings, I replaced the cygwin profile and bashrc files, and I cant
>> seem to remember how to recover from this. Reinstalling cygwin doesnt do any
>> good at
I have a gmail web account, but don't think I can send plain text
through it, but I'll have a look.
Found plain text option and added myself.
Thanks again Eric!
Lots of gold stars for Eric!
--
Ken Shaffer
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
>> I'm having problems with "here docs" after an upgrade. Simply going
>> back to bash 3.1-6 fixed the problem, but I'd thought I'd post
cygchecks
>> and straces.
>The bash release recently changed to honor the setting of TMPDIR
That was it! My script used TMPDIR; changed to use MYTMPDIR instea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Morgan Gangwere on 2/3/2007 1:54 PM:
> jgbk9 wrote:
>> Despite warnings, I replaced the cygwin profile and bashrc files, and I cant
>> seem to remember how to recover from this. Reinstalling cygwin doesnt do any
>> good at all. Any help?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Shaffer, Kenneth on 2/3/2007 12:15 PM:
> I'm having problems with "here docs" after an upgrade. Simply going
> back to bash 3.1-6 fixed the problem, but I'd thought I'd post cygchecks
> and straces.
The bash release recently changed to h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jgbk9 wrote:
> Despite warnings, I replaced the cygwin profile and bashrc files, and I cant
> seem to remember how to recover from this. Reinstalling cygwin doesnt do any
> good at all. Any help?
you can recover... but its difficult.
a: open the reg
On Sat, Feb 03, 2007 at 02:15:16PM -0500, Shaffer, Kenneth wrote:
>I'm having problems with "here docs" after an upgrade. Simply going
>back to bash 3.1-6 fixed the problem, but I'd thought I'd post
>cygchecks and straces. I'm trying to narrow down, but these scripts
>are huge and the here doc po
Despite warnings, I replaced the cygwin profile and bashrc files, and I cant
seem to remember how to recover from this. Reinstalling cygwin doesnt do any
good at all. Any help?
--
View this message in context:
http://www.nabble.com/dumb-mistake-tf3166879.html#a8785032
Sent from the Cygwin Users
On Sat, Feb 03, 2007 at 11:33:00PM +1300, Danny Smith wrote:
>That is, to do the right thing, we would need to:
>
>extern __declspec(dllimport) void foo (void) __asm__("__imp__bar");
>void call_bar(void)
>{ foo(); }
>
>to get
>_call_bar:
> pushl %ebp
> movl__imp__bar, %ecx
>
Dear Mr/ Mrs ,
I Would like to invite you to join the course will be held at the end of March,
2007.
1. Title : Modern Administration & Filing System
Instructor : Drs. Elyus Lanin, Msi
Date/ Venue : March 5 - 6, 2007/ Holiday Inn Hotel, Bandung
2.
Hello,
I would appreciate help with
While working on some dllimport problems with aliased symbols, I ran
across this inconsistency with gcc (all versions)
The use of a literal asmspec to rename a static lib symbol
(say "bar"),
extern void foo (void) __asm__("_bar");
void call_bar(void)
{ fo
13 matches
Mail list logo
