RE: Problem with setup (maybe a feature request)
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 should be able to just NEXT through it. The very last page of the setup includes options of creating desktop/quicklaunch shortcuts. Because I run mintty I chose not to have the basic cygwin shell prompt on my desktop. Setup seems unable to remember what my choice was each time I run setup. I think this is undesired behavior. If you are running a desktop icon the setup process shouldn't make a second one. I couldn't find a place where this data might be stored so, my conclusion was either its not stored at all, or I'm just plain wrong. On the chance I'm right: I'd like to see the defaults change to OFF unless its a first install and there is no sub structure (ie no /etc, /var, /bin, .) On the chance I'm wrong and the data in question is stored, can setup respect previous entries? You can run setup wuith the -n option. See http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problem installing setup-1.7
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 components with $NEW_CYGWINROOT on the fly to support that. That would be useful, during the transition. Right. I'll look into it ASAP. /etc/fstab.d/$USER is created and old 1.5 registry user mount points are copied to /etc/fstab.d/$USER on the fly when the user starts the shell the first time. That's done by the new /etc/profile.d/user-fstab.c?sh scripts in base-cygwin. it == 000-cygwin-post-install.sh. I didn't know there were /other/ components of base-cygwin that /would/ handle that part. Isn't it nice to have a surprise every day? :) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Problem installing setup-1.7
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 script which replaces all $OLD_CYGWINROOT path components with $NEW_CYGWINROOT on the fly to support that. That would be useful, during the transition. Right. I'll look into it ASAP. Should be fixed in the just uploaded base-cygwin 0.3-1. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Problem installing setup-1.7
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. Also there is no /etc/fstab file. What went wrong here? There used to be a script, 000-cygwin-post-install.sh, bundled with the cygwin package itself (well, 1.7 versions anyway), that did this. It was recently moved to a package of its own, 'base-cygwin'. However, that package does not seem to have been added to the 'Base' category, or has not been uploaded to the release-2 area (I don't know which). In any case, setup-1.7 didn't download it for me, either. Here's the important part of the /etc/fstab file that it should have created: C:/cygwin-1.7 /some_fs binary 0 0 C:/cygwin-1.7/bin /usr/bin some_fs binary 0 0 C:/cygwin-1.7/lib /usr/lib some_fs binary 0 0 ...modify to suit your needs. -- Chuck
Re: Problem installing setup-1.7
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 for /usr/bin and /usr/lib where missing. Also there is no /etc/fstab file. What went wrong here? There used to be a script, 000-cygwin-post-install.sh, bundled with the cygwin package itself (well, 1.7 versions anyway), that did this. It was recently moved to a package of its own, 'base-cygwin'. However, that package does not seem to have been added to the 'Base' category, or has not been uploaded to the release-2 area (I don't know which). In any case, setup-1.7 didn't download it for me, either. It hasn't been uploaded to the release-2 area yet. I simply forgot to do it yesterday, sorry. I'm going to upload it in a minute. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Problem installing setup-1.7
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 registry. But after running the new setup the mounts for /usr/bin and /usr/lib where missing. Also there is no /etc/fstab file. What went wrong here? There used to be a script, 000-cygwin-post-install.sh, bundled with the cygwin package itself (well, 1.7 versions anyway), that did this. It was recently moved to a package of its own, 'base-cygwin'. However, that package does not seem to have been added to the 'Base' category, or has not been uploaded to the release-2 area (I don't know which). In any case, setup-1.7 didn't download it for me, either. It hasn't been uploaded to the release-2 area yet. I simply forgot to do it yesterday, sorry. I'm going to upload it in a minute. 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... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Problem installing setup-1.7
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: http://cygwin.com/ml/cygwin-apps/2008-04/msg00299.html 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 mount info from the registry before running setup-1.7.exe -- it'll work better on that initial install, but only for system mounts - /etc/fstab. It doesn't attemp to replicate user mounts (for all users? current user? some selected group of 'cygwin' users? Yech!) into /etc/fstab.d/. That's ok, IMO, but when we release 1.7, end-users need to know about that update quirk. -- Chuck [*] 'course, 000-cygwin-post-install.sh does more than just manipulate mounts and /etc/fstab
Re: Problem installing setup-1.7
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 instructions here: http://cygwin.com/ml/cygwin-apps/2008-04/msg00299.html 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 mount info from the registry before running setup-1.7.exe -- it'll work better on that initial install, but only for system mounts - /etc/fstab. It doesn't attemp to replicate user mounts (for all users? current user? some selected group of 'cygwin' users? Yech!) into /etc/fstab.d/. That's ok, IMO, but when we release 1.7, end-users need to know about that update quirk. I'm not quite sure I understand what you mean. The postinstall script is supposed to create the mount points according to the user's 1.5 based system registry mount table. This is for a replacement of a 1.5 with a 1.7 installation, as it's supposed to be at one point. The problem is that this doesn't allow a parallel installation for now, even if setup-1.7 is working as advertised. I should add code to the script which replaces all $OLD_CYGWINROOT path components with $NEW_CYGWINROOT on the fly to support that. /etc/fstab.d/$USER is created and old 1.5 registry user mount points are copied to /etc/fstab.d/$USER on the fly when the user starts the shell the first time. That's done by the new /etc/profile.d/user-fstab.c?sh scripts in base-cygwin. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Problem installing setup-1.7
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 mount info from the registry before running setup-1.7.exe -- it'll work better on that initial install, but only for system mounts - /etc/fstab. I'm not quite sure I understand what you mean. The postinstall script is supposed to create the mount points according to the user's 1.5 based system registry mount table. Right. And once cygwin-1.7 is released, and *regular* users use setup.exe to upgrade an existing installation of cygwin-1.5 to cygwin-1.7, that will work fine. This is for a replacement of a 1.5 with a 1.7 installation, as it's supposed to be at one point. Exactly. 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 components with $NEW_CYGWINROOT on the fly to support that. That would be useful, during the transition. It doesn't attemp to replicate user mounts (for all users? current user? some selected group of 'cygwin' users? Yech!) into /etc/fstab.d/. That's ok, IMO, but when we release 1.7, end-users need to know about that update quirk. /etc/fstab.d/$USER is created and old 1.5 registry user mount points are copied to /etc/fstab.d/$USER on the fly when the user starts the shell the first time. That's done by the new /etc/profile.d/user-fstab.c?sh scripts in base-cygwin. it == 000-cygwin-post-install.sh. I didn't know there were /other/ components of base-cygwin that /would/ handle that part. -- Chuck
RE: problem with setup
Ugh, top-posting... Reformatted. On Wed, 6 Feb 2008, Pedro Macanás wrote: -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Morgan gangwere Enviado el: miércoles, 06 de febrero de 2008 6:08 Para: [EMAIL PROTECTED] http://cygwin.com/acronyms/#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 to reinstall it and all the configuration files and registry modifications). Well, Cygwin setup is an open-source project, and it should be relatively easy to add one more action (uninstall) to it. Would you care to submit a patch? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! That which is hateful to you, do not do to your neighbor. That is the whole Torah; the rest is commentary. Go and study it. -- Rabbi Hillel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with setup
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: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with setup
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 stuck with starting over if you're looking for the easy path. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with setup
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: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with setup
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) '/etc/setup/bash.lst.gz' first. If that doesn't help, you might be stuck with starting over if you're looking for the easy path. That's what I'm trying to do, start over with a new install, but setup crashes when it comes to uninstalling bash. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem with setup
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 move aside) '/etc/setup/bash.lst.gz' first. If that doesn't help, you might be stuck with starting over if you're looking for the easy path. That's what I'm trying to do, start over with a new install, but setup crashes when it comes to uninstalling bash. Which is why I was suggesting removing '/etc/setup/bash.lst.gz'. It sounds like this file may have become corrupt, which can cause 'setup.exe' to crash. If that's it, this should allow 'setup.exe' to run without the need of removing everything and reinstalling. But if it's all the same to you, then you can certainly go ahead and do that. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
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? -- Morgan Gangwere CraiSys if i cant sudo apt-get install life, then why should i need it? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: problem with setup
I think there would be an uninstall icon for Cygwin (i.e. I would like to reinstall it and all the configuration files and registry modifications). Regards. -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Morgan gangwere Enviado el: miércoles, 06 de 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/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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 propagated the original problem from the Win2k machine (that had experienced corruption) to my WinXP (this I believe I propogated) and a Win95 (I didn't copy the tree or anything so not usre how this propogated) or there was something in the succession of updates. At any rate I resolved the Win95 and WinXP through a full removal and reinstall of Cygwin and my build tree - just reinstalling all the packages and deleting/rebuilding my cvs build tree was insufficient. I knew I was home free when I got to the STL error as previously reported by Igor in cygwin-apps: http://cygwin.com/ml/cygwin-apps/2005-06/msg00159.html on either the WinXp and the Win95 machines. So I just thought I would close this out for the archives with a final resolution. Thanks for all the help and assistance bk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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 that is it.
The best thing I can suggest is ask on the autoconf list. Your error
seems like an internal problem with aclocal or autoconf, and they should
be able to help.
I'm no expert on all that auto-* malarkey, but I notice one thing:
$ ./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: $-6')
called
at /usr/bin/autom4te-2.5x line 1008
aclocal: autom4te failed with exit status: 1
aclocal failed
Autotool bootstrapping failed. You will need to investigate and correct
before you can develop on this source tree
I don't even _have_ a /usr/share/autoconf directory on my installation,
and bootstrap.sh WJFFM. Perhaps there is some residual bogosity lurking in
there from old versions?
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?
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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 {devel,stable} notion as well as the
home grown wrapper scripts. The change was announced at
http://cygwin.com/ml/cygwin-apps/2005-05/msg00322.html but I don't
ever remember seeing an actual [ANNOUNCEMENT} message for the new
packages.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
RE: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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' versions of autotools then apparently.
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
The
'new' versions do away with the {devel,stable} notion as well as the
home grown wrapper scripts. The change was announced at
http://cygwin.com/ml/cygwin-apps/2005-05/msg00322.html
Yeh, I do remember seeing that, now you remind me.
but I don't
ever remember seeing an actual [ANNOUNCEMENT} message for the new
packages.
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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 other autotool-related issues. The problem seems to be with something gone awry in the OP's system. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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: $-6')
called
at /usr/bin/autom4te-2.5x line 1008
aclocal: autom4te failed with exit status: 1
aclocal failed
Autotool bootstrapping failed. You will need to investigate and correct
before you can develop on this source tree
I just checked with a fresh CVS checkout of the setup sources and the
bootstrap went fine. I don't really know what that error message means,
so I can't really be of any help there. You should probably ask on the
autoconf list, where they will be able to aid you in debugging it
further. Make sure to give them as many details as possible.
When you have disk corruption any file is potentially a suspect for
being damanged, so it could be a broken configuration file, possibly
something completely unrelated to Cygwin. Normally when you reinstall a
package your local config files are not replaced (particularly if they
have been modified) so you might consider reinstalling. One trick that
you can use to see if it's a Cygwin installation problem is:
1. save your mounts (mount -m mounts.bat)
2. unmount everything (umount -A)
3. rename your cygwin directory to something else
4. reinstall from setup.exe
This will for all intents and purposes shield your previous install, and
simulate a fresh install. If you find the fresh install works, then you
can copy over the parts you want to keep from the old. If it fails in
the same manner you will know that it's not a Cygwin installation
problem and you can revert back to the old install (by doing the steps
in reverse) without losing anything.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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 error I blew away the setup cvs tree and checked it out again. And the compile still failed. Obviously there something wrong with higher on my CVS tree (I guess). 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'll blow away my CVS tree and recheck everything out and see what that does. As I say the rest of my install on the XP machine is all fresh. Thanks bk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake
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 'auto(conf|make)|libtool' autoconf2.59-2 OK autoconf2.1 2.13-1 OK autoconf2.5 2.59-1 OK automake1.7.9-2 OK automake1.4 1.4p6-1 OK automake1.6 1.6.3-1 OK automake1.7 1.7.9-1 OK automake1.8 1.8.5-1 OK automake1.9 1.9.5-1 OK libtool1.5 1.5.18-1 OK The best thing I can suggest is ask on the autoconf list. Your error seems like an internal problem with aclocal or autoconf, and they should be able to help. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ OK. I have a full cywin running now, with Xorg and KDE. So I'm ok. But I had to do it in four stages. KDE is working again under org. Like I said before, it was setup. Bobby
Re: Problem with setup
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 updated by the later installation attempts. Shouldn't setup.log be getting opened in append mode? We examined it at various times during a later installation attempt, and the contents didn't change and the file modification time stayed at 9:38am. At the moment, the log files are written to disc in one bulk write when setup.exe completes. That's probably not a great design feature. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
[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 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. none of the file handles for any of the temp files of the form (where c:\temp is your temporary package directory) c:\temp\http%.\package.tar.bz2 is ever released. The system starts page faulting and the number of handles just grows and grows, and eventually setup dies like this: Microsoft Visual C++ Runtime Error Runtime Error! Program \\samba\install\win32\cygwin\setup.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. That's nasty. I wonder why we haven't seen more reports of this. Is there any reason why your machine should be more susceptible to this? (Low memory, any kind of resource limits?) Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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. Wow! Well, it's not quite as dramatic here, but I can see a good few leaked handles in Process Explorer. I've committed a fix, but unfortunately, when I begun testing to prepare for a release, I ran into all sorts of nasty problems, including being unable to reinstall Cygwin, having uninstalled it to test setup. I'm going to keep working on it though... after I've completely purged Cygwin from my computer, reinstalled, and set up a VM to do tests in without disrupting my primary machine. Might take a while. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ OK. I have a full cywin running now, with Xorg and KDE. So I'm ok. But I had to do it in four stages. KDE is working again under org. Like I said before, it was setup. Bobby -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 cygcheck. 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. none of the file handles for any of the temp files of the form (where c:\temp is your temporary package directory) c:\temp\http%.\package.tar.bz2 is ever released. The system starts page faulting and the number of handles just grows and grows, and eventually setup dies like this: Microsoft Visual C++ Runtime Error Runtime Error! Program \\samba\install\win32\cygwin\setup.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. That's nasty. I wonder why we haven't seen more reports of this. Is there any reason why your machine should be more susceptible to this? (Low memory, any kind of resource limits?) Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ As for for, 256 MB on Celeron II running XP Pro with Service pack 2. Running SP2 since it came out. Problem started November 3rd with a full installation. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 the zip package), that setup.log was not updated by the later installation attempts. Shouldn't setup.log be getting opened in append mode? We examined it at various times during a later installation attempt, and the contents didn't change and the file modification time stayed at 9:38am. At the moment, the log files are written to disc in one bulk write when setup.exe completes. That's probably not a great design feature. Ah. Absolutely. If setup crashes, you have no debug information! I usually fflush after writing an entry to a log file - it's more important to have accurate debug info than to save a few seconds on execution time, I reckon. And in other emails: 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 | head -5 # This file is automatically generated. If you edit it, your # edits will be discarded next time the file is generated. # See http://cygwin.com/setup.html for details. # setup-timestamp: 1098732614 none of the file handles for any of the temp files of the form (where c:\temp is your temporary package directory) c:\temp\http%.\package.tar.bz2 is ever released. The system starts page faulting and the number of handles just grows and grows, and eventually setup dies like this: Microsoft Visual C++ Runtime Error Runtime Error! Program \\samba\install\win32\cygwin\setup.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. That's nasty. I wonder why we haven't seen more reports of this. Is there any reason why your machine should be more susceptible to this? (Low memory, any kind of resource limits?) Not that I'm aware of, no. One machine was dual processor, 1GB of memory. Interestingly, looking at Task Manager during setup.exe's run, even though there seemed to be plenty of physical memory, it changed to display page fault activity rather than RAM usage. Tweaking TM to show page fault activity and handles showed that there was a lot of page faults from setup, and a steadily growing number of handles (the ..tar.bz2 files which were never released). The other PC that showed the problem had 512MB of memory, and no special resource limits. At the crash point, setup.exe has some 600 open handles and 2 Gb of VM. It's accumulated 2.5 million page faults. Wow! Well, it's not quite as dramatic here, but I can see a good few leaked handles in Process Explorer. Yes, we looked in PE too, and it was clear that no .tar.bz2 file handle was released. We were trying a fresh install, and selected All (i.e. every package). I've committed a fix, but unfortunately, when I begun testing to prepare for a release, I ran into all sorts of nasty problems, including being unable to reinstall Cygwin, having uninstalled it to test setup. I'm going to keep working on it though... after I've completely purged Cygwin from my computer, reinstalled, and set up a VM to do tests in without disrupting my primary machine. Might take a while. Sorry to be causing you such hassles. I'm hoping to get a chance to try the latest Cygwin: # This file is automatically generated. If you edit it, your # edits will be discarded next time the file is generated. # See http://cygwin.com/setup.html for details. # setup-timestamp: 1100546431 luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 doesn't seem like a total showstopper to me. Bobby McNulty can probably provide more details. In fact, I think he's already done so. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 | head -5 # This file is automatically generated. If you edit it, your # edits will be discarded next time the file is generated. # See http://cygwin.com/setup.html for details. # setup-timestamp: 1098732614 That's still just telling you the timestamp when setup.ini was created. It has no bearing on the version of setup.exe, which is displayed on the first panel, e.g. Setup.exe version 2.431. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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, of course, but this problem doesn't seem like a total showstopper to me. Bobby McNulty can probably provide more details. In fact, I think he's already done so. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ First install all of the main cygwin without the gnome stuff, then install the x stuff with gnome. Go to Sourceforge and get KDE on Cygwin. rebaseall. startx and you shound have the KDE desktop on X with cygwin. Neat, huh? It works for me. Now, I'm trying to find a good MIDI sequencer that runs under KDE and Cygwin. Rosegarden has too many problems I don't want to deal with. Bobby -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 a snapshot of October 26th (setup-timestamp: 1098732614), and in that version of setup, none of the file handles for any of the temp files of the form (where c:\temp is your temporary package directory) c:\temp\http%.\package.tar.bz2 is ever released. The system starts page faulting and the number of handles just grows and grows, and eventually setup dies like this: Microsoft Visual C++ Runtime Error Runtime Error! Program \\samba\install\win32\cygwin\setup.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 installation attempts. Shouldn't setup.log be getting opened in append mode? We examined it at various times during a later installation attempt, and the contents didn't change and the file modification time stayed at 9:38am. luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ Then I'm not the only one noticing this? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 get a cygcheck. So, does this mean that the changes I made to the xorg distribution worked, then? If so, why are you reporting this here rather than in the cygwin-xfree mailing list where this has been discussed at great length? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ Yes, it worked. Now I'm getting a report that setup is not closing the files. It can't get past the update_info now. Something has happened to setup. Either that, or Cygwin is bigger now than when the current version came out. I lost the URL to the test version of setup. I know they have been working on. I see it in the CVS logs every day.
Re: Problem with setup
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 this mean that the changes I made to the xorg distribution worked, then? If so, why are you reporting this here rather than in the cygwin-xfree mailing list where this has been discussed at great length? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problem with setup
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 get a cygcheck. So, does this mean that the changes I made to the xorg distribution worked, then? If so, why are you reporting this here rather than in the cygwin-xfree mailing list where this has been discussed at great length? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ Yes, it worked. Now I'm getting a report that setup is not closing the files. It can't get past the update_info now. Something has happened to setup. Either that, or Cygwin is bigger now than when the current version came out. I lost the URL to the test version of setup. I know they have been working on. I see it in the CVS logs every day. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
