public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Rainer Dunker" <rainer.dunker@web.de>
To: "Gerrit P. Haase" <gp@familiehaase.de>
Cc: cygwin@cygwin.com
Subject: Re: gcc installation problem and solution
Date: Tue, 28 Dec 2004 11:23:00 -0000	[thread overview]
Message-ID: <1849635026@web.de> (raw)

"Gerrit P. Haase" <gp@familiehaase.de> schrieb am 28.12.04 11:40:39:
> > These are supposed to be symbolic links to the executables in the /usr/bin directory, but - for whatever reason - the setup program did not install them in a way that they were used as symlinks afterwards (for example, ar.exe is a text file with contents "!<symlink>/usr/bin/ar.exe"). So I removed them and created symlinks to the proper executables manually; after that, the problem was gone.
> 
> This is the correct content of valid Cygwin Symlinks and for me
> NT Explorer shows them as type "S" for symlink too.  The symlinks
> should work fine from within any Cygwin based shell (bash, zsh, ...).

I remember having seen that on W2K and maybe XP, but on my current NT4 box it's apparently different.
This is how a properly working symlink, created with ln -s, looks like:

As seen by 'ls -l':
lrwxrwxrwx    1 myname     mkgroup_       15 Dec 27 16:00 ar.exe -> /usr/bin/ar.exe

As seen by 'cmd /c dir':
27.12.04  16:00                    116 ar.exe.lnk

This is the hexlified contents of ar.exe.lnk:
00000000: 4c00 0000 0114 0200 0000 0000 c000 0000  L...............
00000010: 0000 0046 0c00 0000 0000 0000 0000 0000  ...F............
00000020: 0000 0000 0000 0000 0000 0000 0000 0000  ................
00000030: 0000 0000 0000 0000 0000 0000 0100 0000  ................
00000040: 0000 0000 0000 0000 0000 0000 0f00 2f75  ............../u
00000050: 7372 2f62 696e 2f61 722e 6578 6515 0048  sr/bin/ar.exe..H
00000060: 3a5c 7075 625c 6379 675c 6269 6e5c 6172  :\pub\cyg\bin\ar
00000070: 2e65 7865                                .exe

The Windows Explorer properly handles this as 'ar.exe',
a shortcut to H:\pub\cyg\bin\ar.exe.

I can't help it, but that's what I see. I have no idea whether this difference
in storing symlinks is a property of different Windows or Cygwin versions -
or whatever.


Best regards,

Rainer

________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193


--
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 11:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 11:23 Rainer Dunker [this message]
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
  -- 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=1849635026@web.de \
    --to=rainer.dunker@web.de \
    --cc=cygwin@cygwin.com \
    --cc=gp@familiehaase.de \
    /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).