From: Christopher Faylor <cgf@cygnus.com>
To: mlx@san.rr.com, gnu-win32@cygnus.com
Subject: Re: Soft links givin' me as hard time !!!
Date: Sun, 28 Feb 1999 23:02:00 -0000 [thread overview]
Message-ID: <19990203215336.B12292@cygnus.com> (raw)
Message-ID: <19990228230200.NFOCbj7fQoPZMC700HTVhOA95SnO5eRaQ-ef6XCrj0s@z> (raw)
In-Reply-To: <199902031736.JAA07743@proxyb1-atm.san.rr.com>
On Wed, Feb 03, 1999 at 09:36:53AM -0800, Steve Biskis wrote:
>Hi all,
>
>Trying to build the 20.1 development sources and keep
>hitting a snag. Seems to involve soft links. I didn't
>realize the CygWin stuff supported them - cool, EXCEPT.
>
>After configuring make will choke on any of the little
>"!<symlink> ..." magic files it comes accross.
>
>For instance, during a make, the egcs distribution sets up
>an "ln -s" of ./gcc.c to ./g++.c . This causes the file: g++.c
>with the following contents: !<symlink>./gcc.c .
>
>Now, when make come accross this file, I get:
>
>g++.c:1 parse error before '!'
>
>Now, if I edit the makefile, stopping it from deleting & then
>recreating this "link" and either copy gcc.c to g++.c or do
>an actual UNIX ln -s on the fileserver, I'm OK.
>
>I should mention that all the target files are actually on a
>FreeBSD file system shared with Samba. All the binary
>tools and headers are on the win32 compile host.
Symbolic links need to have the "S"ystem bit set. That probably
is not happening on a Samba drive.
--
cgf@cygnus.com
http://www.cygnus.com/
next prev parent reply other threads:[~1999-02-28 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-03 9:36 Steve Biskis
[not found] ` < 199902031736.JAA07743@proxyb1-atm.san.rr.com >
1999-02-03 18:54 ` Christopher Faylor [this message]
1999-02-28 23:02 ` Christopher Faylor
1999-02-28 23:02 ` Steve Biskis
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=19990203215336.B12292@cygnus.com \
--to=cgf@cygnus.com \
--cc=gnu-win32@cygnus.com \
--cc=mlx@san.rr.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).