X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com connect(): No such file or directory From: Paul Bibbings Subject: Re: gcc: building gcc-4.5.0 for Cygwin Date: Thu, 15 Apr 2010 22:49:19 +0100 Lines: 21 Message-ID: <87pr202xpc.fsf@gmail.com> References: <87y6go3743.fsf@gmail.com> <4BC7617A.4020306@cygwin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (windows-nt) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com "Larry Hall (Cygwin)" writes: > On 4/15/2010 2:26 PM, Paul Bibbings wrote: >> Can I, then, do the same with the .dlls in question? Is it possible, >> for instance, for .dlls to be loadable via symlinks under Cygwin? > > No. The Windows loader does not recognize Cygwin symlinks. Actually, > nothing in Windows does. ;-) Indeed. Thinking it through, as I am specifically wanting gcc-4.5.0 in order to experiment with its implemented C++0x features, I am hardcoding CC=i686-pc-cygwin-gcc-4.5.0 into the makefile anyway, so it's probably a reasonable workaround for the moment to add a `run' target along the lines of: run: $(OUT) @export PATH=/opt/gcc-4.5.0/bin:`printenv PATH` && $< Regards Paul Bibbings -- 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