Hi Dave,
Dave Korn wrote 16 April 2007 14:28:-
>
> On 16 April 2007 13:14, Adye, TJ (Tim) wrote:
>
> > I'm a bit surprised this isn't flagged by the compiler (it
> > warns you about lots of other non-standard usages), though I guess
it
> > would be a bit
> > So, the case here ("_name" as an argument name) should be fine.
>
> Except that that was just an example, and in fact a
> misleading one, because what Chelton's code was /actually/
> using was "_N"... hence the problem.
Ah yes, I didn't see that (I thought his second case was the example
Hi,
Dave Korn wrote on 16 April 2007 12:29:
>
> Thanks for the correction. I'm referring to the C
> standard; I think C++ follows basically the same rules but
> don't have a spec handy to refer to.
The C++ standard is a little different, but the result in this case is
the same:-
"17.4.3.1.2/
Buff Miner wrote on 11 April 2007 17:14:
>
> More precisely:
> Start up bash by doing Start -> Programs -> Cygwin -> Cygwin
> Bash\ Shell.
> Right click on the icon in the upper left of the title bar
> and select properties Under Options, select 'QuickEdit Mode',
> hit ok Select 'Modify shortc
Brian Dessent wrote on 09 April 2007 22:05:
>
> If you really want a compromise solution, you could modify
> run to not depend on cygwin1.dll at link-time but instead
> LoadLibrary() it at runtime, and if that fails fall back to
> whatever the native version would have done. Thus you get a
> s
Hi Dave,
Dave Korn wrote on 09 April 2007 17:16:
>
> > You might have a better idea for where the non-Cygwin version
> > should go - I just put it in /usr/bin/run-native.exe.
>
> Or just "alias run-native='cmd /c start '".
If that did what we wanted, then we wouldn't need the run package in
Hi Christopher,
Christopher Faylor wrote:
>
> I don't see any reason to include a non-cygwin version of a
> program in the *cygwin* distribution. If you don't have
> cygwin1.dll in the path, then you aren't running in a cygwin
> environment.
>
> This is not to say that I don't understand perf
Hi Alexander,
For many years I've continued to use Chuck Wilson's old run-1.1.4
because it included a version that was linked without Cygwin
(run-native.exe, built with VC). Although it doesn't have all the
features of the Cygwin version (eg. it can't translate Cygwin mount
points), it does allow
Hi Corinna,
Thanks for the inetutils update. The inetd -D option is particularly
welcome (so thanks also to Bryan Thrall).
Unfortunately the new version's ftp, rcp, and rlogin commands give an
annoying new warning when connecting, eg.
ftp: setsockopt TOS (ignored): Protocol not available
Actu
Hi Gerrit,
> -Original Message-
> From: Gerrit P. Haase <[EMAIL PROTECTED]>
> Sent: 12 July 2005 13:03
> To: Adye, TJ (Tim)
> Cc: The Cygwin Mailing List
> Subject: Re: Updated: perl-5.8.7-2
>
> Adye, TJ (Tim) wrote:
> >>Have you recompiled Win32::
Gerrit P. Haase wrote:
> > Hi Tim,
> >
> > Adye, TJ (Tim) wrote:
> >
> >> Hi Gerrit,
> >>
> >> Thanks for the Perl update.
> >>
> >> Unfortunately this doesn't seem to fix the problem I reported
earlier
> >&
Hi Gerrit,
Thanks for the Perl update.
Unfortunately this doesn't seem to fix the problem I reported earlier
("Perl Win32::Shortcut screws up fork"). My test script worked fine
after "rebaseall", but when I reinstalled Cygwin from scratch (including
Perl 5.8.7-2) it dies with
C:\cygwin\bin\perl
)
>
> On Thu, Jul 07, 2005 at 05:29:25PM +0100, Adye, TJ (Tim) wrote:
> >Hi,
> >
> >With cygwin-1.5.18-1, the |readshortcut| command crashes on exit if I
> >specify a Cygwin-style path name. The crash goes away if I
> downgrade to
> >cygwin 1.5.17-1.
>
x27;s Win32::Shortcut and fork work together!
Thanks for the hint.
Nevertheless, there does seem to be a problem with the rebaseall.
Tim.
> -Original Message-
> From: Adye, TJ (Tim)
> Sent: 07 July 2005 19:55
> To: 'Cygwin List'
> Subject: RE: Perl Win32::Shortcut scre
(/usr/bin/cygiconv-2.dll) failed with last error = 6
cygiconv-2.dll is used by bash, but rebaseall is a bash script. What can
I do?
Thanks,
Tim.
> -Original Message-
> From: Larry Hall
> Sent: 07 July 2005 19:09
> To: Adye, TJ (Tim); cygwin@cygwin.com
> Subject: Re: Perl Win32
Christopher Faylor wrote:
> Btw, in case anyone is interested, I tracked this down by putting a
> breakpoint on free, and printing the address being freed. Then I
> cut/pasted that output to a file and sorted the file based on the
> address. This unearthed a few potential candidates for this pro
Hi,
In an attempt to work round the problem with readshortcut I reported
earlier, I thought I'd use a Perl script. Unfortunately the
Win32::Shortcut package seems to cause problems with process forking
(unlike the readshortcut error, this one isn't specific to the latest
cygwin DLL). I get an erro
Hi,
With cygwin-1.5.18-1, the |readshortcut| command crashes on exit if I
specify a Cygwin-style path name. The crash goes away if I downgrade to
cygwin 1.5.17-1.
% readshortcut "C:/Documents and Settings/All Users/Start
Menu/Programs/Accessories/Calculator"
/cygdrive/c/WINDOWS/system32/calc.exe
005 at 12:33:55AM +0100, Adye, TJ (Tim) wrote:
> >Hi,
> >
> >On 26 May 2005, Christopher Faylor wrote:
> >
> >> I've made a new version of the Cygwin DLL and associated utilities
> >> available for download. As usual, a list of what has changed
&g
opened afsauthent.dll
Tim.
> -Original Message-
> From: Larry Hall
> Sent: 03 June 2005 01:05
> To: Adye, TJ (Tim); The Cygwin Mailing List
> Subject: RE: Updated: cygwin-1.5.17-1
>
> At 07:33 PM 6/2/2005, you wrote:
> >Hi,
> >
> >On 26 May 20
Hi,
On 26 May 2005, Christopher Faylor wrote:
> I've made a new version of the Cygwin DLL and associated utilities
> available for download. As usual, a list of what has changed
> is below.
> [...]
> cgf: Make dlopen search /usr/bin (for Windows compatibility)
> and /usr/lib (for UNIX compati
21 matches
Mail list logo
