public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gcc installation problem and solution
Date: Tue, 28 Dec 2004 19:11:00 -0000	[thread overview]
Message-ID: <20041228191254.GB5767@trixie.casa.cgf.cx> (raw)
In-Reply-To: <41D1AF3D.9030909@familiehaase.de>

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/

  reply	other threads:[~2004-12-28 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 11:23 Rainer Dunker
2004-12-28 13:07 ` Christopher Faylor
2004-12-28 17:56 ` Gerrit P. Haase
2004-12-28 18:09   ` Christopher Faylor
2004-12-28 19:08     ` Gerrit P. Haase
2004-12-28 19:11       ` Christopher Faylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-28  7:40 Rainer Dunker
2004-12-28 10:40 ` Gerrit P. Haase
2004-12-28 19:13 ` Igor Pechtchanski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041228191254.GB5767@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).