X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Fri, 9 Apr 2010 12:54:10 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: "GCC is not found" and "compiler cannot create executables" errors
Message-ID:	<20100409105410.GE28908@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<k2i7758a5c31004080511r876491dfy6326bb0712dca648 AT mail DOT gmail DOT com> <4BBDE46D DOT 5070406 AT etr-usa DOT com> <v2w7758a5c31004080736ja46e3d08q602c97313e945408 AT mail DOT gmail DOT com> <m2o1ef5a52f1004080818v2cb7ef14ke2b22a5f450b7bfb AT mail DOT gmail DOT com> <h2w7758a5c31004080825m884404f6jbf0108177af1229b AT mail DOT gmail DOT com> <v2r1ef5a52f1004080849z1693fc01v3b2d924f2c04b91 AT mail DOT gmail DOT com> <20100408170304 DOT GA4912 AT ghost DOT local DOT lan> <p2j7758a5c31004090226u2f58a2a5ia6259a78cec8faf5 AT mail DOT gmail DOT com> <20100409095634 DOT GB1960 AT calimero DOT vinschen DOT de> <w2y7758a5c31004090338leb58fbw47e45ee470c1e3a5 AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<w2y7758a5c31004090338leb58fbw47e45ee470c1e3a5@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

On Apr  9 12:38, david sastre wrote:
> Hello,
> 
> Thanks for the explanation.
> This also solves another recent mystery (for me):
> why I have unable to properly use another locally built program:
> 
> $ cygcheck /usr/local/sbin/lighttpd
>  -> C:\cygwin\usr\local\sbin\..\stow\lighttpd-1.4.26\sbin\lighttpd.exe
> C:\cygwin\usr\local\sbin\..\stow\lighttpd-1.4.26\sbin\lighttpd.exe
>   C:\cygwin\usr\local\bin\cyglightcomp.dll  C:\cygwin\bin\cyggcc_s-1.dll
>     C:\cygwin\bin\cygwin1.dll
>       C:\WINDOWS\system32\ADVAPI32.DLL
>         C:\WINDOWS\system32\KERNEL32.dll
>           C:\WINDOWS\system32\ntdll.dll
>         C:\WINDOWS\system32\RPCRT4.dll
>           C:\WINDOWS\system32\Secur32.dll
>   C:\cygwin\bin\cygcrypto-0.9.8.dll
>   C:\cygwin\bin\cygfam-0.dll
>   C:\cygwin\bin\cygpcre-0.dll
>   C:\cygwin\bin\cygssl-0.9.8.dll
> cygcheck: C:\cygwin\usr\local\bin\cyglightcomp.dll is a symlink instead of a DLL
> 
> Not to mention the whole list of modules, also built as DLLs...
> 
> And -this is going to re-scope the subject- is there a way to
> circumvent this limitation?
> Other than pointing --prefix to /usr/local/ rather than
> /usr/local/stow/package, not to lose
> stow's little advantage to manage software as (pseudo)packages.
> I mean, if I want to use this version (1.4.26) of lighttpd (BTW,
> enhanced with IPV6, SSL and some other stuff -yet to test, though), am
> I suppossed to build a standard cygwin package for this
> to work?

Not necessarily.  Just add the path to your DLLs to $PATH.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

- Raw text -