Rance Hall sent the following at Tuesday, January 05, 2010 10:13 AM
I'm running cygwin 1.7.x and I've been pretty faithful with running
setup again when updates are announced.
I've noticed that setup remembers almost all the answers from the
previous run, so if you are just doing an update you
On Apr 27 18:36, Charles Wilson wrote:
Corinna Vinschen wrote:
The problem is that this doesn't allow a parallel installation for
now, even if setup-1.7 is working as advertised.
That's what I was trying to say.
I should add code
to the script which replaces all $OLD_CYGWINROOT path
On Apr 28 10:51, Corinna Vinschen wrote:
On Apr 27 18:36, Charles Wilson wrote:
Corinna Vinschen wrote:
The problem is that this doesn't allow a parallel installation for
now, even if setup-1.7 is working as advertised.
That's what I was trying to say.
I should add code
to the
Steffen Sledz wrote:
I tried to install setup-1.7 on a system running a normal release
before. I've deleted the whole C:\cygwin dir from the disk and removed
all cygwin/cygnus related items from the registry.
But after running the new setup the mounts for /usr/bin and /usr/lib
where missing.
On Apr 27 10:41, Charles Wilson wrote:
Steffen Sledz wrote:
I tried to install setup-1.7 on a system running a normal release
before. I've deleted the whole C:\cygwin dir from the disk and removed all
cygwin/cygnus related items from the registry.
But after running the new setup the mounts
On Apr 27 17:56, Corinna Vinschen wrote:
On Apr 27 10:41, Charles Wilson wrote:
Steffen Sledz wrote:
I tried to install setup-1.7 on a system running a normal release
before. I've deleted the whole C:\cygwin dir from the disk and removed all
cygwin/cygnus related items from the
Corinna Vinschen wrote:
Nevertheless, take the scripts carefully for now. I have a nagging
feeling that my approach to fetch the old mount points from the registry
is not exactly foolproof. Something about the rootdir...
Well, if you follow Brian instructions here:
On Apr 27 15:09, Charles Wilson wrote:
Corinna Vinschen wrote:
Nevertheless, take the scripts carefully for now. I have a nagging
feeling that my approach to fetch the old mount points from the registry
is not exactly foolproof. Something about the rootdir...
Well, if you follow Brian
Corinna Vinschen wrote:
On Apr 27 15:09, Charles Wilson wrote:
Then when you run setup-1.7.exe you don't /have/ any mounts in the registry
-- so all you'll get in /etc/fstab are the basic default mounts. [*] Later,
when setup-1.7.exe is updated -- so that we don't have to remove all the
1.5
/#PCYMTNQREAIYR. Thanks.
Asunto: Re: problem with setup
*cough*
just a thought... but cant you simply as administrator or some other
form of admin simply kill your cygwin isntall directory and remove the
Cygwin registry keys?
I think there would be an uninstall icon for Cygwin (i.e. I would like
Amadeus W.M. wrote:
Is there a way to completely remove cygwin as if it was never there?
http://cygwin.com/faq/faq.setup.html#faq.setup.uninstall-all
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
Warren Young wrote:
Amadeus W.M. wrote:
Is there a way to completely remove cygwin as if it was never there?
http://cygwin.com/faq/faq.setup.html#faq.setup.uninstall-all
Might be worth trying to delete (or move aside) '/etc/setup/bash.lst.gz'
first. If that doesn't help, you might be
On Tue, 05 Feb 2008 18:06:52 -0700, Warren Young wrote:
Amadeus W.M. wrote:
Is there a way to completely remove cygwin as if it was never there?
http://cygwin.com/faq/faq.setup.html#faq.setup.uninstall-all
Thanks! That should do.
--
Unsubscribe info:
On Tue, 05 Feb 2008 20:59:11 -0500, Larry Hall (Cygwin) wrote:
Warren Young wrote:
Amadeus W.M. wrote:
Is there a way to completely remove cygwin as if it was never there?
http://cygwin.com/faq/faq.setup.html#faq.setup.uninstall-all
Might be worth trying to delete (or move aside)
Amadeus W.M. wrote:
On Tue, 05 Feb 2008 20:59:11 -0500, Larry Hall (Cygwin) wrote:
Warren Young wrote:
Amadeus W.M. wrote:
Is there a way to completely remove cygwin as if it was never there?
http://cygwin.com/faq/faq.setup.html#faq.setup.uninstall-all
Might be worth trying to delete (or
*cough*
just a thought... but cant you simply as administrator or some other
form of admin simply kill your cygwin isntall directory and remove the
Cygwin registry keys?
--
Morgan Gangwere
CraiSys if i cant sudo apt-get install life, then why should i need it?
--
Unsubscribe info:
febrero de 2008 6:08
Para: cygwin@cygwin.com
Asunto: Re: problem with setup
*cough*
just a thought... but cant you simply as administrator or some other
form of admin simply kill your cygwin isntall directory and remove the
Cygwin registry keys?
--
Unsubscribe info: http://cygwin.com/ml
Just a follow up on this:
I finally resolved this and as everyone knew/suspected it was not an
autoconf/automake issue or at least I don't think it was unless there was
something missed in update to update to update. I actually had the same
autom4te error on 3 machines of which I either
Original Message
From: Brian Dessent
Sent: 17 June 2005 06:42
Brian Keener wrote:
The only other thing I can think of is what version of autoconf and
automake and libtool are you using. Mine are the versions that were
released when stable and devel became obsolete. But not sure
Dave Korn wrote:
I don't have any /usr/bin/autom4te-2.5x either. My Channels.pm lives
under /usr/autotool/{devel,stable}/share/Autom4te.
Sounds like you have some stray stuff going on?
You're still on the 'old' versions of autotools then apparently. The
'new' versions do away with the
Original Message
From: Brian Dessent
Sent: 17 June 2005 11:12
Dave Korn wrote:
I don't have any /usr/bin/autom4te-2.5x either. My Channels.pm lives
under /usr/autotool/{devel,stable}/share/Autom4te.
Sounds like you have some stray stuff going on?
You're still on the 'old'
Dave Korn wrote:
Guess I am, at that. And from the looks of things, I'm staying that way
for at least a little while longer. I need to be able to build setup! g
(From the 'knew you were joking, but:' department...)
I am using the new packages and had no problem running bootstrap.sh or
any
Brian Keener wrote:
$ cd /usr/develop/src/cygwin-apps/setup
/usr/develop/src/cygwin-apps/setup
$ ./bootstrap.sh
Running bootstrap.sh in libgetopt++
unknown channel $-5 at /usr/share/autoconf/Autom4te/Channels.pm line 538
Autom4te::Channels::msg('$-5', 'configure.in:14', 'warning:
Thanks Brian for the follow up and the suggestion. As I mentioned I did just
do a clean install of cygwin and all apps to a Windows XP laptop but like a
dummy and lazy person I copied my cvs tree from the Win2k laptop. Then when I
tried to compile on the WinXP machine and I still got the
Brian Keener wrote:
The only other thing I can think of is what version of autoconf and automake
and libtool are you using. Mine are the versions that were released when
stable and devel became obsolete. But not sure that is it.
I too use the 'new' autotools:
$ cygcheck -c|grep -P
Luke Kendall wrote:
On 16 Nov, Bobby McNulty wrote:
Then I'm not the only one noticing this?
No, myself and one other person here have begun noticing it.
luke
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Luke Kendall wrote:
I should also add that after a setup.exe crash at 9:38am after being
left running overnight, later attempts to install that day (with the VM
size steadily increasing, and setup.exe appearing to stick at the
stage where it is installing the zip package), that setup.log was not
[EMAIL PROTECTED] wrote:
On 11 Nov, Bobby McNulty wrote:
Guys, theres a major problem with setup.
According to the error I just got, setup is not
closing any of its files after writing them.
I finally got past xorg, and got up to update_info.
I'll rerun setup to get a cygcheck.
I can confirm
Luke Kendall wrote:
On 17 Nov, To: [EMAIL PROTECTED] wrote:
The system starts page faulting and the number of
handles just grows and grows, and eventually setup dies
I can add this:
At the crash point, setup.exe has some 600 open handles and 2 Gb of VM.
It's
accumulated 2.5 million page faults.
Luke Kendall wrote:
On 16 Nov, Bobby McNulty wrote:
Then I'm not the only one noticing this?
No, myself and one other person here have begun noticing it.
luke
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Max Bowsher wrote:
[EMAIL PROTECTED] wrote:
On 11 Nov, Bobby McNulty wrote:
Guys, theres a major problem with setup.
According to the error I just got, setup is not
closing any of its files after writing them.
I finally got past xorg, and got up to update_info.
I'll rerun setup to get a
On 17 Nov, Max Bowsher wrote:
Luke Kendall wrote:
I should also add that after a setup.exe crash at 9:38am after being
left running overnight, later attempts to install that day (with the VM
size steadily increasing, and setup.exe appearing to stick at the
stage where it is installing
On Thu, Nov 18, 2004 at 11:09:26AM +1100, Luke Kendall wrote:
Sorry to be causing you such hassles. I'm hoping to get a chance to
try the latest Cygwin:
You can try the latest cygwin. Just install everything in two or
three steps.
This is not the final solution, of course, but this problem
Luke Kendall wrote:
I can confirm this. We took a snapshot of October 26th
(setup-timestamp: 1098732614), and in that version of setup,
That number you quoted identifies the version of the setup.ini datafile, not
the setup.exe program.
Sorry, how's this?
$ bunzip2 -c setup.bz2 |
Christopher Faylor wrote:
On Thu, Nov 18, 2004 at 11:09:26AM +1100, Luke Kendall wrote:
Sorry to be causing you such hassles. I'm hoping to get a chance to
try the latest Cygwin:
You can try the latest cygwin. Just install everything in two or
three steps.
This is not the final solution,
On 11 Nov, Bobby McNulty wrote:
Guys, theres a major problem with setup.
According to the error I just got, setup is not
closing any of its files after writing them.
I finally got past xorg, and got up to update_info.
I'll rerun setup to get a cygcheck.
I can confirm this. We took
On 17 Nov, To: [EMAIL PROTECTED] wrote:
The system starts page faulting and the number of
handles just grows and grows, and eventually setup dies
I can add this:
At the crash point, setup.exe has some 600 open handles and 2 Gb of VM. It's
accumulated 2.5 million page faults.
luke
--
I should also add that after a setup.exe crash at 9:38am after being
left running overnight, later attempts to install that day (with the VM
size steadily increasing, and setup.exe appearing to stick at the
stage where it is installing the zip package), that setup.log was not
updated by the later
Luke Kendall wrote:
On 17 Nov, To: [EMAIL PROTECTED] wrote:
The system starts page faulting and the number of
handles just grows and grows, and eventually setup dies
I can add this:
At the crash point, setup.exe has some 600 open handles and 2 Gb of VM. It's
accumulated 2.5 million
On 16 Nov, Bobby McNulty wrote:
Then I'm not the only one noticing this?
No, myself and one other person here have begun noticing it.
luke
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
Christopher Faylor wrote:
On Thu, Nov 11, 2004 at 05:26:34PM -0600, Bobby McNulty wrote:
Guys, theres a major problem with setup.
According to the error I just got, setup is not
closing any of its files after writing them.
I finally got past xorg, and got up to update_info.
I'll rerun setup to
On Thu, Nov 11, 2004 at 05:26:34PM -0600, Bobby McNulty wrote:
Guys, theres a major problem with setup.
According to the error I just got, setup is not
closing any of its files after writing them.
I finally got past xorg, and got up to update_info.
I'll rerun setup to get a cygcheck.
So, does
Christopher Faylor wrote:
On Thu, Nov 11, 2004 at 05:26:34PM -0600, Bobby McNulty wrote:
Guys, theres a major problem with setup.
According to the error I just got, setup is not
closing any of its files after writing them.
I finally got past xorg, and got up to update_info.
I'll rerun setup to
43 matches
Mail list logo
