On Thu, Mar 19, 2020 at 3:51 PM David Karr via Cygwin
wrote:
> On Wed, Mar 18, 2020 at 2:17 PM David Karr <> wrote:
>
> > On Wed, Mar 18, 2020 at 9:38 AM Ken Brown via Cygwin <> wrote:
> >
> >> On 3/18/2020 11:22 AM, Andrey Repin wrote:
> >> > Greetings, David Karr!
> >> >
> >> >> Thanks, that wo
On Wed, Mar 18, 2020 at 2:17 PM David Karr <> wrote:
> On Wed, Mar 18, 2020 at 9:38 AM Ken Brown via Cygwin <> wrote:
>
>> On 3/18/2020 11:22 AM, Andrey Repin wrote:
>> > Greetings, David Karr!
>> >
>> >> Thanks, that worked. For now, I guess I have to figure out how to set
>> that
>> >> property
On Wed, Mar 18, 2020 at 9:38 AM Ken Brown via Cygwin <> wrote:
> On 3/18/2020 11:22 AM, Andrey Repin wrote:
> > Greetings, David Karr!
> >
> >> Thanks, that worked. For now, I guess I have to figure out how to set
> that
> >> property permanently, or until this pty bug is fixed.. I start Emacs
>
On 3/18/2020 11:22 AM, Andrey Repin wrote:
Greetings, David Karr!
Thanks, that worked. For now, I guess I have to figure out how to set that
property permanently, or until this pty bug is fixed.. I start Emacs from a
shortcut, executing "emacs.xml". I see the file appears to have some
syntax
Greetings, David Karr!
> Thanks, that worked. For now, I guess I have to figure out how to set that
> property permanently, or until this pty bug is fixed.. I start Emacs from a
> shortcut, executing "emacs.xml". I see the file appears to have some
> syntax for setting the environment, but I've
emoved
> > in
> > 8.0
> > [INFO] Scanning for projects...[
> > [WARNING] l
> >
> >
> >
> >
> >
> >
> > ---
> >
> > The first thing I see is that it prints the shell prompt twice AFTER
> &g
g I see is that it prints the shell prompt twice AFTER
pressing enter on the command line to run. That might possibly be an issue
with my Bash dot files, but this didn't happen before the Cygwin upgrade,
and it doesn't happen in the mintty window.
After that, it gets even worse. The
pressing enter on the command line to run. That might possibly be an issue
with my Bash dot files, but this didn't happen before the Cygwin upgrade,
and it doesn't happen in the mintty window.
After that, it gets even worse. The "Java HotSpot ..." line prints in
three lines, in
On Sat, 4 Jan 2020 10:51:42 +0900
Takashi Yano wrote:
> On Thu, 2 Jan 2020 22:16:02 +
> Ken Brown wrote:
> > I think this narrows it down to one of the following commits:
>
> I looked into this probelm and found the issue occurs after
> the following commit.
>
> > commit 915fcd0ae8d83546ce135
On Thu, 2 Jan 2020 22:16:02 +
Ken Brown wrote:
> I think this narrows it down to one of the following commits:
I looked into this probelm and found the issue occurs after
the following commit.
> commit 915fcd0ae8d83546ce135131cd25bf6795d97966
> Author: Takashi Yano
> Date: Thu Sep 5 13:22:
[Please don't top-post on this list.]
On 1/2/2020 4:25 PM, ianpu...@gmail.com wrote:
> Now narrowed down to cygwin1.dll version 3.1.0-0.4 as the release which
> introduced this issue.
>
> I found the intervening versions between 3.0.7-1 and 3.1.0-1 as test
> releases in earlier release archives a
h that I took then?
> >
> > Ian
> >
> > > -Original Message-
> > > From: cygwin-ow...@cygwin.com On
> > Behalf Of
> > > Ian Puleston
> > > Sent: Friday, December 27, 2019 4:39 PM
> > >
> > > Hi,
> > >
On 1/2/2020 2:16 PM, ianpu...@gmail.com wrote:
> Hi.
>
> I don't know if this will help at all since there is a big time gap and it
> looks like a lot of changes between these, but I tried the cygwin1 dlls from
> the snapshots at https://www.cygwin.com/snapshots and found that the
> 2019-08-19 sna
gt; >
> > I have a Cygwin installation on a Windows 10 PC, on which I use
> > X-Windows to access a Linux development/build server. All has been
> > working great for a long time, until I rand a Cygwin upgrade on
> > December 23rd, and after that
> > X11
then?
Ian
> -Original Message-
> From: cygwin-ow...@cygwin.com On Behalf
> Of Ian Puleston
> Sent: Friday, December 27, 2019 4:39 PM
> To: cygwin@cygwin.com
> Subject: X11 forwarding extremely slow (unusable) after Cygwin upgrade on
> Dec 23rd
>
> Hi,
>
Hi,
I have a Cygwin installation on a Windows 10 PC, on which I use X-Windows to
access a Linux development/build server. All has been working great for a
long time, until I rand a Cygwin upgrade on December 23rd, and after that
X11 has become pretty much unusable. I normally launch the
Hi,
I have a Cygwin installation on a Windows 10 PC, on which I use X-Windows to
access a Linux development/build server. All has been working great for a long
time, until I rand a Cygwin upgrade on December 23rd, and after that X11 has
become pretty much unusable. I normally launch the
> Try mounting the SAMBA server directory and using the 'noacl' option
> for that mount point.
I thought I had tried a noacl mount of the share on /usr/home and
it had no effect on the problem. But given your suggestion I tried
again and low and behold... It worked.
noacl is the key..
> Se
On 9/12/2011 3:08 PM, Eric S. Johnson wrote:
Ive looked around the archives and the FAQ's. I can't seem to
figure this out. I must be missing some simple clue here.
I have some windows XP clients of a samba server. I recently
upgraded one from cygwin 1.5(ish?) to cygwin 1.7 latests.
On the upgr
I don't think cygcheck can resolve a symlink.
(I'm not near a Windows machine to test right now)
For the archives, yes, it can.
I don't have emacs on my machine (vi is the one true editor) but the
only difference between the two invocation methods is that if you pass a
symlink, cygcheck emit
On 4/19/2011 6:57 AM, Ken Brown said this:
> On 4/18/2011 5:44 PM, Tim Daneliuk wrote:
>> On 4/18/2011 3:27 PM, Ken Brown wrote:
>>> On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
> This has happened the last few times I did an upgrade with
On 4/18/2011 5:44 PM, Tim Daneliuk wrote:
On 4/18/2011 3:27 PM, Ken Brown wrote:
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start
On 4/18/2011 3:27 PM, Ken Brown wrote:
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
fine.
Previously, I w
On Mon, Apr 18, 2011 at 04:36:09PM -0400, Ken Brown wrote:
>On 4/18/2011 4:30 PM, Christopher Faylor wrote:
>> On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
>>> On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
> This has happened
On 4/18/2011 4:30 PM, Christopher Faylor wrote:
On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, an
On Mon, Apr 18, 2011 at 04:27:18PM -0400, Ken Brown wrote:
>On 4/18/2011 4:02 PM, marco atzeri wrote:
>> On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
>>> This has happened the last few times I did an upgrade with setup.exe.
>>> emacs, emacs-nox, and emacs -nw will not start at all. Xemac
On 4/18/2011 4:02 PM, marco atzeri wrote:
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
fine.
Previously, I was able to work around this by falling
On Mon, Apr 18, 2011 at 10:01 PM, Tim Daneliuk wrote:
> This has happened the last few times I did an upgrade with setup.exe.
> emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
> fine.
>
> Previously, I was able to work around this by falling back to a
> previous version of ema
This has happened the last few times I did an upgrade with setup.exe.
emacs, emacs-nox, and emacs -nw will not start at all. Xemacs works
fine.
Previously, I was able to work around this by falling back to a
previous version of emacs, but this too seems broken now.
Ideas?
--
--
On 01/12/2010 07:16 AM, Tod wrote:
On 1/11/2010 3:58 PM, Larry Hall (Cygwin) wrote:
On 01/11/2010 03:46 PM, Tod wrote:
I'm upgrading to 1.7.1 from the previous version which I was pretty good
at keeping up to date.
I ran into a problem installing openssh which locked the install forcing
me to
On 1/11/2010 3:58 PM, Larry Hall (Cygwin) wrote:
On 01/11/2010 03:46 PM, Tod wrote:
I'm upgrading to 1.7.1 from the previous version which I was pretty good
at keeping up to date.
I ran into a problem installing openssh which locked the install forcing
me to cancel. I stopped the openssh servic
On 01/11/2010 03:46 PM, Tod wrote:
I'm upgrading to 1.7.1 from the previous version which I was pretty good
at keeping up to date.
I ran into a problem installing openssh which locked the install forcing
me to cancel. I stopped the openssh service and cygwin service and tried
again. It completed
I'm upgrading to 1.7.1 from the previous version which I was pretty good
at keeping up to date.
I ran into a problem installing openssh which locked the install forcing
me to cancel. I stopped the openssh service and cygwin service and
tried again. It completed with me ok'ing past pointer er
On Wed, Dec 16, 2009 at 07:07:44AM -0600, David Nelson wrote:
>There is no question; only a report.
>
>I re-installed a new version of Cygwin (into f:\cygwin) after a recent
>but long overdue
>upgrade of the "base" caused 'makes' on my C project to begin failing
>in strange ways.
>The details of th
David Nelson wrote:
> There is no question; only a report.
It's well-known that you can't have multiple versions of the cygwin DLL
hanging around at the same time or you may get problems. You seem to have had
both /bin dirs in your PATH at the same time; that's asking for trouble.
> Searching
There is no question; only a report.
I re-installed a new version of Cygwin (into f:\cygwin) after a recent
but long overdue
upgrade of the "base" caused 'makes' on my C project to begin failing
in strange ways.
The details of the failures are lost to my memory since I began
hunting around on this
On Feb 19 09:13, David le Comte wrote:
> My USB serial port card can support 9216000 bps, and all power of 2
> sub-multiples
> to 115200, then the "usual suspects" below that. Is this list a subset
> of your new list of
> supported baudrates?
It's the list of baudrates supported by Linux up to
Thank you for your response Corinna.
When I did my upgrade to include cron, I just upgraded the "admin"
section. I came in
to work on the weekend, and did a full upgrade and everything is back to
normal.
I must have got something out of whack with something else by only doing a
partial upgrad
On Feb 16 10:27, David le Comte wrote:
> Two days ago, I upgraded my Cygwin to extend my "admin" components so that
> I could use cron. When I did this I found that a program I had previously
> written to set a baudrate on a serial port to 230400bps is now failing,
> whereas
> before it was OK.
David le Comte wrote:
Brian Ford wrote:
On Fri, 16 Feb 2007, David le Comte wrote:
Note that using stty -F /dev/comX where X is the "Comm port number"
still works, ie it can still set the baud rate to 230400 (or even
25).
Sorry, but note also that if you are going to use Posix sty
Brian Ford wrote:
On Fri, 16 Feb 2007, David le Comte wrote:
Note that using stty -F /dev/comX where X is the "Comm port number"
still works, ie it can still set the baud rate to 230400 (or even
25).
Sorry, but note also that if you are going to use Posix style termio
calls, you n
On Fri, 16 Feb 2007, David le Comte wrote:
> Note that using stty -F /dev/comX where X is the "Comm port number"
> still works, ie it can still set the baud rate to 230400 (or even
> 25).
Sorry, but note also that if you are going to use Posix style termio
calls, you need to use the Posix dev
I'm not sure what broke, but you might consider trying a snapshot:
http://cygwin.com/ml/cygwin-cvs/2007-q1/msg00066.html
--
Brian Ford
Lead Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained crew...
--
Brett adelphia.net> writes:
I see that my problem was unrelated to the original I replied to this morning.
I am still hopig someone has an idea for me to try. Here are my symptoms again.
I am running a Win 2000 Professional box with Norton Antivirus 2003
professional. I am behind a LynkSys WR
> >Larry, I suspect "ls -l" showed files with permissions
> --+, which
> >Ron interpreted as 000 without noticing the ACL flag.
>
> Yes, I suspect this as well.
Suspection was correct. I did pay no attention to the "+", but I read
the info node and saw the hint to "alternate access metho
At 04:27 PM 7/12/2005, you wrote:
>On Tue, 12 Jul 2005, Larry Hall wrote:
>
>> At 10:20 AM 7/12/2005, you wrote:
>> >On Tue, 12 Jul 2005, FischRon.external wrote:
>> >
>> >> > So, except for the pdksh postinstall (which is a genuine bug),
>> >> > everything else seems to be related to the weird per
On Tue, 12 Jul 2005, Larry Hall wrote:
> At 10:20 AM 7/12/2005, you wrote:
> >On Tue, 12 Jul 2005, FischRon.external wrote:
> >
> >> > So, except for the pdksh postinstall (which is a genuine bug),
> >> > everything else seems to be related to the weird permissions on your
> >> > machine.
> >>
> >
At 10:20 AM 7/12/2005, you wrote:
>On Tue, 12 Jul 2005, FischRon.external wrote:
>
>> > So, except for the pdksh postinstall (which is a genuine bug),
>> > everything else seems to be related to the weird permissions on your
>> > machine.
>>
>> Could it be related to the strange fact that my numeri
On Tue, 12 Jul 2005, FischRon.external wrote:
> > So, except for the pdksh postinstall (which is a genuine bug),
> > everything else seems to be related to the weird permissions on your
> > machine.
>
> Could it be related to the strange fact that my numeric user id
> suddenly has changed from 400
> So, except for the pdksh postinstall (which is a genuine
> bug), everything
> else seems to be related to the weird permissions on your machine.
Could it be related to the strange fact that my numeric user id
suddenly has changed from 400 to 121833?
One more note regarding the recreation of /e
On Tue, 12 Jul 2005, FischRon.external wrote:
> > I think your main problem wasn't with permissions, but with
> > postinstall scripts not running properly. See if running them fixes
> > the problem.
>
> I re-ran them. Incidentally, all those sh files had permission 000;
> interestingly, I was sti
> I think your main problem wasn't with permissions, but with
> postinstall
> scripts not running properly. See if running them fixes the problem.
I re-ran them. Incidentally, all those sh files had permission 000;
interestingly, I was still able to execute them. I had expected to
get error mess
> Well, you *do* need an entry for your domain user. That's
> accomplished
> with "mkpasswd -d -u YOURUSERNAME" (which will only query the PDC for
> YOURUSERNAME, not list all users). I'm no security expert,
> but I think
> there's enough local information that "mkpasswd -l -c" ("-c"
> stands
On Mon, 11 Jul 2005, FischRon.external wrote:
> > > I did the variation with "-l -c" to recreate /etc/passwd, because
> > > "-d" would hang the shell.
> >
> > It doesn't hang, just takes very very long in large domains. What you
> > want is "mkpasswd -d -u YOURUSERNAME >> /etc/passwd". Though I
> > I did the variation with "-l -c" to recreate /etc/passwd,
> because "-d"
> > would hang the shell.
>
> It doesn't hang, just takes very very long in large domains. What you
> want is "mkpasswd -d -u YOURUSERNAME >> /etc/passwd". Though
> I believe
> "mkpasswd -c" already does that without
On Mon, 11 Jul 2005, FischRon.external wrote:
> > The -u flag to mkpasswd (and -g flag to mkgroup) are your
> > friends. See
> > the User's Guide.
> >
> > The thing is that if you're the only user in your domain using the
> > machine, you can simply run "mkpasswd -l -c > /etc/passwd"
> > (or "mkp
> The -u flag to mkpasswd (and -g flag to mkgroup) are your
> friends. See
> the User's Guide.
>
> The thing is that if you're the only user in your domain using the
> machine, you can simply run "mkpasswd -l -c > /etc/passwd"
> (or "mkpasswd
> -l -d -u YOURUSERNAME > /etc/passwd").
I did the
On Sun, 10 Jul 2005, Joshua Daniel Franklin wrote:
> On 7/7/05, Igor Pechtchanski wrote:
> > > > If you still haven't run setup since that fateful man installation
> > >
> > > no, I didn't
> >
> > Good. The file was actually very helpful. Perhaps we could offer general
> > advice in the User's G
On 7/7/05, Igor Pechtchanski wrote:
> > > If you still haven't run setup since that fateful man installation
> >
> > no, I didn't
>
> Good. The file was actually very helpful. Perhaps we could offer general
> advice in the User's Guide section on setup to back up that file in case
> of any insta
On Thu, 7 Jul 2005, FischRon.external wrote:
> > > ~ $ getfacl /usr /usr/share /usr/share/misc
> > > # file: /usr
> > > # owner: Administrators
> > > # group: mkpasswd
> > ^^^
> > > user::rwx
> > > group::---
> > ^^
> > > group:SYSTEM:rwx
> > > mask:rwx
> > > other:---
>
> > ~ $ getfacl /usr /usr/share /usr/share/misc
> > # file: /usr
> > # owner: Administrators
> > # group: mkpasswd
> ^^^
> > user::rwx
> > group::---
> ^^
> > group:SYSTEM:rwx
> > mask:rwx
> > other:---
> > default:user:Administrators:rwx
> > default:group:SYSTEM:rwx
> > d
On Thu, 7 Jul 2005, FischRon.external wrote:
> > Please make sure your mailer respects the Reply-To: header -- I set it
> > for a reason. There's no need to Cc: me on the messages, as I read
> > the list.
>
> Thank you for pointing this out! It's done correct now.
Yes it is. Thank you for notic
On Wed, Jul 06, 2005 at 11:32:08PM +0200, Gerrit P. Haase wrote:
>Christopher Faylor wrote:
>>Last night's snapshot should fix this problem.
>>
>>http://cygwin.com/snapshots/
>
>I think with the 20050705 snapshot bash / rxvt is much much faster
>faster compared with 1.5.17 which I used before;)
Hm
Christopher Faylor wrote:
Last night's snapshot should fix this problem.
http://cygwin.com/snapshots/
I think with the 20050705 snapshot bash / rxvt is much much
faster faster compared with 1.5.17 which I used before;)
Gerrit
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simp
Jacek Piskozub wrote:
Dave,
Can't locate mozLock.pm in @INC (@INC contains: /usr/lib/perl5/5.8/cygwin
Find it attached.
Chris will probably kill me when he wakes up :-(
Lol.
Gerrit
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.
On Tue, Jul 05, 2005 at 12:52:49PM -0400, Christopher Faylor wrote:
>On Tue, Jul 05, 2005 at 07:59:32AM -0700, Yitzchak Scott-Thoennes wrote:
>>On Tue, Jul 05, 2005 at 10:17:28AM -0400, Christopher Faylor wrote:
>>>The malloc implementation in perl was updated to the latest version of
>>>Doug Lea's
On Tue, Jul 05, 2005 at 07:59:32AM -0700, Yitzchak Scott-Thoennes wrote:
>On Tue, Jul 05, 2005 at 10:17:28AM -0400, Christopher Faylor wrote:
>>The malloc implementation in perl was updated to the latest version of
>>Doug Lea's malloc so there is a possibility that this is a malloc bug.
>>However,
On Tue, 5 Jul 2005, Jacek Piskozub wrote:
> Yitzchak Scott-Thoennes wrote:
>
> > What perl version (on linux)? Do you have a test case?
>
> No, it works fine on Linux. Same script, same Mozilla build, same Perl
> version (5.8.6).
>
> I would bet my money that the fault is on cygwin side, especia
Yitzchak Scott-Thoennes wrote:
> What perl version (on linux)? Do you have a test case?
No, it works fine on Linux. Same script, same Mozilla build, same Perl
version (5.8.6).
I would bet my money that the fault is on cygwin side, especially as
with cygwin 1.5.17, mozilla builds work fine.
Fu
On Tue, Jul 05, 2005 at 10:17:28AM -0400, Christopher Faylor wrote:
> The malloc implementation in perl was updated to the latest version of
> Doug Lea's malloc so there is a possibility that this is a malloc bug.
> However, given that the perl on my linux system routinely trips a
> "double free" e
I've downloaded this and it does just sit there but I don't know how long
I'm
supposed to wait. Is it supposed to print a lot of stuff right away?
Yes, it's supposed to produce a cab file while reporting what it is doing.
I realized that if you press CTRL-c it really starts to build the cab fi
Ron,
Please make sure your mailer respects the Reply-To: header -- I set it for
a reason. There's no need to Cc: me on the messages, as I read the list.
On Tue, 5 Jul 2005, FischRon.external wrote:
> > On Mon, 4 Jul 2005, FischRon.external wrote:
> >
> > > Now I checked /usr/share/misc and foun
On Tue, Jul 05, 2005 at 08:52:25AM +0200, Jacek Piskozub wrote:
>I'll risk wasting some more precious time (ypurs or mine) adding a Perl
>stackdump I found in the Mozilla directory where the build failed:
>
>===begin stackdump
>Exception: STATUS_ACCESS_VIOLATION at eip=610AA95A
>eax=2F632F65 eb
On Mon, Jul 04, 2005 at 07:39:39PM -0400, Volker Quetschke wrote:
>>>It is a standalone testcase, unfortunately it depends on the absolute path
>>>it resides in. To reproduce unpack perlfreeze.zip to d: and then
>>>do:
>>>$ cd /cygdrive/d/perlfreeze
>>>$ ./perltest.pl
>>>
>>>and see it hang. (In rx
Dave,
Can't locate mozLock.pm in @INC (@INC contains: /usr/lib/perl5/5.8/cygwin
Find it attached.
Chris will probably kill me when he wakes up :-(
J.
#
# * BEGIN LICENSE BLOCK *
# Version: MPL 1.1/GPL 2.0/LGPL 2.1
#
# The contents of this file are subject to the Mozilla Public Li
Original Message
>From: Jacek Piskozub
>Sent: 05 July 2005 12:09
> Ignore my previous post. I attached the HTMLized version downloaded as a
> test of wget :-(
>
> This is the real script.
>
> J.
[EMAIL PROTECTED] /test/perl> ./make-jars.pl
: bad interpreter: No such file or directory
[E
Ignore my previous post. I attached the HTMLized version downloaded as a
test of wget :-(
This is the real script.
J.
#!/perl
# make-jars [-f] [-v] [-l] [-x] [-a] [-e] [-d ] [-s ] [-t
] [-c ] [-z zipprog] [-o operating-system] <
my $cygwin_mountprefix = "";
if ($^O eq "cygwin") {
$cygwi
Hi,
More random ramblings:
I tried to debug the script using the ancient "print" inserting
technique. The result was interesting. I can stop the crash from
happening by adding a lot of print commands. Does it show it is a timing
(race) problem?
To make it even more interesting, by adding ju
Original Message
>From: Jacek Piskozub
>Sent: 05 July 2005 10:19
> Hi,
>
> More test results:
>
> I added "-d" to the Mozilla rule file that runs make-jars.pl (yes, it is
> definitely this script, see
> http://lxr.mozilla.org/seamonkey/source/config/make-jars.pl for a copy).
[EMAIL PRO
Hi,
More test results:
I added "-d" to the Mozilla rule file that runs make-jars.pl (yes, it is
definitely this script, see
http://lxr.mozilla.org/seamonkey/source/config/make-jars.pl for a copy).
This is the output I got
main::(/cygdrive/d/mozilla_source/mozilla/config/make-jars.pl:5):
5
Chris,
It is really strange.
It should start immediately when running the script and the whole
process lasts about 5 seconds.
Using
system $systemcall;
instead of
open (DDF, "$systemcall") ...
works fine.
This also works:
$systemcall='\\/c/WINDOWS/system32/makecab.exe /V3 /F ...
And this too:
Hi,
Using even more of your precious time I re-run the Mozilla suite
compilation. This is the final part of the output:
make[4]: Entering directory
`/cygdrive/d/mozilla_source/mozilla/netwerk/resources'
+++ making chrome
/cygdrive/d/mozilla_source/mozilla/netwerk/resources =>
../../dist/bi
> On Mon, 4 Jul 2005, FischRon.external wrote:
>
> > After upgrading cygwin to the most recent version, I found that man
> > pages aren't displayed anymore; for example
> >
> > $ man man
> > Warning: cannot open configuration file /usr/share/misc/man.conf
>
> That's not good...
[snip]
> > Now
I'll risk wasting some more precious time (ypurs or mine) adding a Perl
stackdump I found in the Mozilla directory where the build failed:
===begin stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=610AA95A
eax=2F632F65 ebx=0800 ecx=871C9010 edx=871C9000 esi=2F632F65
edi=871C26C8
ebp=007
On Mon, Jul 04, 2005 at 05:57:48PM -0400, Volker Quetschke wrote:
> Stop wasting your precious time complaining about my useless strace.
Well, since you already said you would try to reduce it to a standalone
testcase, I think you can deduce that CGF's comments weren't directed
primarily (or neces
It is a standalone testcase, unfortunately it depends on the absolute path
it resides in. To reproduce unpack perlfreeze.zip to d: and then
do:
$ cd /cygdrive/d/perlfreeze
$ ./perltest.pl
and see it hang. (In rxvt/bash)
I've downloaded this and it does just sit there but I don't know how long I
On Mon, Jul 04, 2005 at 07:12:33PM -0400, Volker Quetschke wrote:
>Volker Quetschke wrote:
>>This is the perl script that works with the 1.5.17 cygwin dll and
>>hangs with 1.5.18:
>>
>>-- snip perltest.pl --
>>#!/bin/perl
>>
>>$extracmd='';
>>#$extracmd='sleep 1 && ';
>>$systemcall=$extracmd.'make
Volker Quetschke wrote:
This is the perl script that works with the 1.5.17 cygwin dll and
hangs with 1.5.18:
-- snip perltest.pl --
#!/bin/perl
$extracmd='';
#$extracmd='sleep 1 && ';
$systemcall=$extracmd.'makecab.exe /V3 /F
d:/w1/SRC680_m113/instsetoo_native/wntmsci10.pro/OpenOffice/ddf/en-
On Mon, Jul 04, 2005 at 05:57:48PM -0400, Volker Quetschke wrote:
>Stop wasting your precious time complaining about my useless strace.
You know, oddly enough, the only mention of "time" in my previous
message was to suggest a more economical use of a bug reporter's time --
assuming that the bug r
After upgrading cygwin yesterday I get the following reproducible hang
in a perl script starting an external program.
This is the perl script that works with the 1.5.17 cygwin dll and hangs
with 1.5.18:
Did you also see this with snapshots?
I didn't try. I will first try to condense the proble
Christopher Faylor
[...]
>
>We normally do trust that people who report problems are actually having
>problems and having multiple people report that they have the same
>problem with no additional debugging details beyond "it dies for me when
>I run this other big application" is not generally go
Christopher Faylor wrote
>"the same problem"? "A hang" is != "a crash".
>
Well, a perl script not finishing the way it was meant to finish caused
by upgrade to cygwin 1.5.18..
Call it a related problem, if you wish.
J.
--
If Linux is good enough for BlueGene, it's good for me.
--
Unsubsc
On Mon, Jul 04, 2005 at 01:44:24PM -0400, Christopher Faylor wrote:
>On Mon, Jul 04, 2005 at 12:42:49PM -0400, Volker Quetschke wrote:
>>After upgrading cygwin yesterday I get the following reproducible hang
>>in a perl script starting an external program.
>>
>>This is the perl script that works wi
On Mon, Jul 04, 2005 at 07:41:05PM +0200, Jacek Piskozub wrote:
>Volker Quetschke wrote:
>>After upgrading cygwin yesterday I get the following reproducible hang
>>in a perl script starting an external program.
>
>I believe I've seen the same problem. Mozilla suite cannot be build
>anymore after
On Mon, Jul 04, 2005 at 12:42:49PM -0400, Volker Quetschke wrote:
>After upgrading cygwin yesterday I get the following reproducible
>hang in a perl script starting an external program.
>
>This is the perl script that works with the 1.5.17 cygwin dll and
>hangs with 1.5.18:
Did you also see this
Volker Quetschke wrote:
After upgrading cygwin yesterday I get the following reproducible
hang in a perl script starting an external program.
I believe I've seen the same problem. Mozilla suite cannot be build
anymore after upgrading to cygwin 1.5.18 (two different Windows hosts).
Downgra
After upgrading cygwin yesterday I get the following reproducible
hang in a perl script starting an external program.
This is the perl script that works with the 1.5.17 cygwin dll and
hangs with 1.5.18:
-- snip perltest.pl --
#!/bin/perl
$extracmd='';
#$extracmd='sleep 1 && ';
$systemcall=$ext
On Mon, 4 Jul 2005, FischRon.external wrote:
> After upgrading cygwin to the most recent version, I found that man
> pages aren't displayed anymore; for example
>
> $ man man
> Warning: cannot open configuration file /usr/share/misc/man.conf
That's not good...
> Then I saw that my MANPATH lo
After upgrading cygwin to the most recent version, I found that man
pages
aren't displayed anymore; for example
$ man man
Warning: cannot open configuration file /usr/share/misc/man.conf
Then I saw that my MANPATH looks strange:
$ echo MANPATH
:/usr/ssl/man
Note the leading column, whic
Hi,
I just upgraded to cygwin 1.5.11, great that there is a new release. But, I
use wincvs to get my cvs code, after the upgrade that doesn't work anymore,
cvs just hangs. Doing just "cvs -z9 update" hangs forever, after downgrading
to 1.5.10, it works again, anyone having an idea?
Johnny
--
Un
1 - 100 of 106 matches
Mail list logo
