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 Date: Tue, 28 Dec 2004 14:12:54 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: gcc installation problem and solution Message-ID: <20041228191254.GB5767@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <1849635026@web.de> <41D19E50.301@familiehaase.de> <20041228181127.GA5767@trixie.casa.cgf.cx> <41D1AF3D.9030909@familiehaase.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D1AF3D.9030909@familiehaase.de> User-Agent: Mutt/1.4.1i On Tue, Dec 28, 2004 at 08:08:45PM +0100, Gerrit P. Haase wrote: >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. tar is a unix utility. Symlinks in tar files are stored as... symlinks. The creation of symlinks is handled by whatever is interpreting the tar file. cgf -- 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/