X-Spam-Check-By: sourceware.org
Date: Sat, 13 Jan 2007 12:54:54 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Thomas Antony <tomasm2005 AT gmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: gcc: installation problem, cannot exec 'cc1'
In-Reply-To: <cf641f1d0701130941k3ae8f26fx214caac574773568@mail.gmail.com>
Message-ID: <Pine.GSO.4.63.0701131251330.17383@access1.cims.nyu.edu>
References: <cf641f1d0701130326i60125618o6be7e047cc87e84f AT mail DOT gmail DOT com>    <000a01c73722$f99c3c10$a501a8c0 AT CAM DOT ARTIMI DOT COM>  <cf641f1d0701130941k3ae8f26fx214caac574773568 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

Ugh, top-posting...  Reformatted.

On Sat, 13 Jan 2007, Thomas Antony wrote:

> On 1/13/07, Dave Korn <dave DOT korn AT XXXXXX DOT XXX> wrote:

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.

> > [snip]
> >   It would be helpful if you could run "cygcheck -c >a.txt" before doing so,
> > "cygcheck -c >b.txt" afterwards, and then show us the output of "grep
> > 'gcc\|mingw\|w32api' a.txt b.txt".  It would be good if we verify whether
> > cygcheck spots these busted links and identifies them as a problem
>
> ...
> Nop.
>
> Tom AT toms-pc ~
> $ grep 'gcc\|mingw\|w32api' a.txt b.txt
> a.txt:gcc                  3.4.4-3            OK
> a.txt:gcc-core             3.4.4-3            OK
> a.txt:gcc-g++              3.4.4-3            OK
> a.txt:gcc-mingw            20040810-1         OK
> a.txt:gcc-mingw-core       20050522-1         OK
> a.txt:gcc-mingw-g++        20050522-1         OK
> a.txt:mingw-runtime        3.11-1             OK
> a.txt:w32api               3.8-1              OK
> b.txt:gcc                  3.4.4-3            OK
> b.txt:gcc-core             3.4.4-3            OK
> b.txt:gcc-g++              3.4.4-3            OK
> b.txt:gcc-mingw            20040810-1         OK
> b.txt:gcc-mingw-core       20050522-1         OK
> b.txt:gcc-mingw-g++        20050522-1         OK
> b.txt:mingw-runtime        3.11-1             OK
> b.txt:w32api               3.8-1              OK
>
> I guess I am gonna have to reinstall the whole thing.

Since cygcheck uses the listings of the installed files from the package
distribution tarball, it's not going to catch missing files/symlinks that
are supposed to be created during the postinstall phase.  In fact, since
gcc-mingw is distributed as a tarball that is extracted in a postinstall
script, it's not possible to check whether it's incomplete using cygcheck.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
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/