On Thu, Feb 24, 2022, at 4:32 PM, Adam Dinwoodie wrote:
> I'll see what I can do to get it working again for you!
Adam, that is so nice of you, thank you!
On Thu, Feb 24, 2022, at 6:54 PM, Allen Hewes wrote:
> Am I missing something?
yup, "git grep" not "grep"
On Thu, Feb 24, 2022, at 7:27 PM
Hi,
I appreciate this is just a birthday wish-list item, but...
% git grep -P hopeful...
fatal: cannot use Perl-compatible regexes when not compiled with USE_LIBPCRE
It would be lovely (well, at least for me) if this could work.
--
Problem reports: https://cygwin.com/problems.html
FAQ:
On Sat, Jan 23, 2021, at 7:08 PM, Achim Gratz wrote:
> Anthony Heading writes:
> […]
> > What approach do you want? (Choose 'local::lib', 'sudo' or 'manual')
> > [local::lib]
>
> Well, just say "manual" at this promp
On Fri, Jan 22, 2021, at 7:35 PM, Achim Gratz wrote:
>
> For good measure I repeated this with /usr/local not existing at all and
> the result stays the same.
Achim, that was a helpful test, thankyou. Digging further, the triggering
perl code in /usr/share/perl5/5.30/CPAN/FirstTime.pm, so to
On Fri, Jan 22, 2021, at 4:36 PM, Marco Atzeri via Cygwin wrote:
>
> not on usr/local
>
> perl-Stow: Perl library for stow
>
> 2020-02-04 19:14 0 usr/share/perl5/
> 2020-02-04 19:14 0 usr/share/perl5/site_perl/
> 2020-02-04 19:14 0 usr/share/perl5/sit
Hi Brian!
On Fri, Jan 22, 2021, at 7:33 AM, Brian Inglis wrote:
> either something has not completed correctly, or something is missing in
> recent
> installations.
I think that's right. Those the directories which are referenced in the
binary, I know the generic upstream perl source process
Hi,
Whenever I have a new cygwin setup, I get an error/warning when trying to
install perl modules:
% cpan install Win32::Symlink
Loading internal logger. Log::Log4perl recommended for better logging
[...]
Use of uninitialized value $what in concatenation (.) or string at
/usr/share/perl5/5.30
On Tue, Oct 27, 2015, at 01:29 AM, Mark Geisert wrote:
> I really appreciate the leads and code you've provided. Could we
> please discuss only on the Cygwin mailing list? That's the convention
> we have, barring extraordinary circumstances :) . It allows for
> public review.
I believe I did send
On Mon, Oct 26, 2015, at 03:54 PM, Mark Geisert wrote:
> There are configure errors from this process, at least on my
> machine. I'll take on maintenance of this package. Give me a short
> while to get my sea legs. Thanks Ken for the pointers and Corinna
> for the nudge.
Thanks Mark. I would t
On Sun, Oct 25, 2015, at 11:57 PM, Mark Geisert wrote:
> ...if tmp_str is not modified after the above line, ...
Indeed. Unfortunately it is modified.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com
reproduce how
the binary package was built, or any other way to verify that the source
and binaries do match?
Thanks
Anthony
On Sat, Oct 17, 2015, at 10:30 PM, Anthony Heading wrote:
> Seems free() is being called on an adjusted pointer, causing general
> misbehaviour. A minimal patch
Seems free() is being called on an adjusted pointer, causing general
misbehaviour. A minimal patch below.
Anthony
--- src/mkshortcut/mkshortcut.c.Orig2015-10-17 21:57:08.0
-0400
+++ src/mkshortcut/mkshortcut.c 2015-10-17 22:16:41.269357400 -0400
@@ -412,7 +412,7 @@
char* exe_nam
I guess this patch is right.
Rgds
A
--- sys/file.h.Orig 2014-08-05 23:46:27.199694300 -0400
+++ sys/file.h 2014-08-05 23:46:55.919734500 -0400
@@ -39,7 +39,14 @@
#define LOCK_NB0x04/* don't block when
locking */
#define LOCK_UN0x08/
Brian Dessent wrote:
> All of the actual processing of all window events happens through
> messages passed to WndProc, but WndProc is never directly called
> by user code. So if you want to communicate information between the
> window procedure and the main function (such as: bad error happened,
>
Brian Dessent wrote:
> I think you're confusing the two separate issues, or maybe I didn't
> transition from one to the other very clearly.
>
> The reason we ship with SJLJ is because the Dwarf unwinder (prior to gcc
> 4.3) can't deal with foreign frames. You can run into this simply by
> writing
Brian Dessent wrote:
The choice to ship gcc configured for SJLJ is because it is the only way
to guarantee correct behavior in all cases. [... elided... ] EH across
shared libraries will always be broken in the case of static libgcc et
al. (The same is true on other platforms like Linux, so it'
On Fri, Jan 14, 2005 at 02:35:28PM -0500, Christopher Faylor wrote:
> On Fri, Jan 14, 2005 at 10:39:23AM -0800, Earl Chew wrote:
> >I think the name of the current executable is stored in myself->progname
> >within cygwin1.dll.
> >
> >The more easily accessible __progname returns the basename of th
On Thu, Nov 21, 2002 at 11:47:22PM -0500, Christopher Faylor wrote:
> I'm regenerating a snapshot right now which may become 1.3.16.
> Please try it.
Might I ask whether there are any fixes or remaining known problems
with signals being lost on multi-processor machines?
The much reported 'rsync
On Mon, Sep 23, 2002 at 01:06:22PM -0700, Sudheer Tumuluru wrote:
>
> I am having the same problem with rsync 2.5.5-1. I am
> trying to rsync a couple of short text files between a linux server and
> Win2k Professional boxes with cygwin. About 20% of the time, rsync freezes
> at the end of th
19 matches
Mail list logo
