delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/08/24/05:53:15

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <718D38CAB6E0D011B2C90060970C28A57E17E4@exchangeserver.pixelpower.com>
From: David Korn <dkorn AT pixelpower DOT com>
To: "'mohammad Saleem'" <mosa AT enea DOT se>, cygwin AT cygwin DOT com,
crossgcc AT sourceware DOT cygnus DOT com
Subject: RE: How to re-configure
Date: Fri, 24 Aug 2001 10:53:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)

>Hi all,
>
> By misstake I configured binutils at wrong place and now I want to run
>configure script again from another directory.
> When I do that I get the following message:
>
>
> *********************************************
> Configuring for a i686-pc-cygwin32 host.
> *** Cannot configure here in "/build/binutils" when
>"/source/binutils-2.10" is currently configured.
>bash-2.02$
>***************************************
>
>How can I solve this problem?


    Hi Mohammad,

 I haven't seen that error message myself, but I think what it's trying to
tell you is that you ran the configure command in the source directory, and
it's created some auto-generated files in the source tree; if you were to
try and configure in a separate build directory now, it would autogenerate
the needed files in that directory, but then the ones in the main source
tree would override them, so it wouldn't work.  In other words, doing a 
configure command in the source directory has modified the source directory
so that when you build it you'll get the configuration you first chose, no
matter what.

  To get it back the way it was before, you could either search the source
tree for any files with a timestamp matching the time when you configured,
and delete them, but probably the quickest simplest and most reliable 
solutions would just be to delete the source tree and unpack the binutils
tar.gz again.  I hope you kept it around after you unpacked it the first
time!  If you didn't, then have a go by deleting the recent files that were
created when you ran configure, or download it again if you have a fast
enough net connection for that to be easy.


       DaveK
-- 
" So far, science's crowning achievement, the Atomic Bomb, has not even
been able to alleviate the misery and torture of endless centuries of
world poverty." - George Hammond, self-proclaimed discoverer of the 
scientific proof of god.


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019