Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Message-ID: <41D1AF3D.9030909@familiehaase.de> Date: Tue, 28 Dec 2004 20:08:45 +0100 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; de-AT; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: gcc installation problem and solution References: <1849635026@web.de> <41D19E50.301@familiehaase.de> <20041228181127.GA5767@trixie.casa.cgf.cx> In-Reply-To: <20041228181127.GA5767@trixie.casa.cgf.cx> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Christopher Faylor wrote: > On Tue, Dec 28, 2004 at 06:56:32PM +0100, Gerrit P. Haase wrote: > >>There are two kinds of symlinks, Windows style (with .lnk ending) >>and pure Cygwin symlinks, binutils obviously contains Cygwin stlye >>symlinks. > > > setup.exe only creates pure cygwin symlinks. I suspect that the So symlinks included in the tarball are not simply restored in the same style they were generated / tarred? Interesting. Gerrit -- =^..^= -- 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/