delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Message-ID: | <42B24541.C9E4B714@dessent.net> |
Date: | Thu, 16 Jun 2005 20:36:33 -0700 |
From: | Brian Dessent <brian AT dessent DOT net> |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: Problem compiling Setup but unsure if my install is hosed or is it the source or autoconf/automake |
References: | <VA DOT 000011ba DOT 01eda85e AT thesoftwaresource DOT com> |
X-Spam-Report: | -5.8/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.1 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results |
X-IsSubscribed: | yes |
Reply-To: | cygwin AT cygwin DOT com |
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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |