From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Sat, 14 Jul 2001 11:59:56 +0200
To:	djgpp-workers AT delorie DOT com
Cc:	Andrew Cottrell <acottrel AT ihug DOT com DOT au>
Subject:	Re: Comments on GCC 3.0 distribution
Message-ID:	<20010714115956.B264@lauras.lt>
Mail-Followup-To:	djgpp-workers AT delorie DOT com,
	Andrew Cottrell <acottrel AT ihug DOT com DOT au>
References:	<2427-Wed11Jul2001195622+0300-eliz AT is DOT elta DOT co DOT il> <3B4DF103 DOT 11332 DOT D60645 AT localhost> <2593-Thu12Jul2001220335+0300-eliz AT is DOT elta DOT co DOT il> <005401c10c04$124ccc70$0a02a8c0 AT acceleron> <1438-Sat14Jul2001100741+0300-eliz AT is DOT elta DOT co DOT il>
Mime-Version:	1.0
In-Reply-To:	<1438-Sat14Jul2001100741+0300-eliz@is.elta.co.il>
User-Agent:	Mutt/1.3.18i
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> In addition to using ln.exe built with CVS libc, as Martin said, you
> should test this with files that are not programs.  Functions such as
> open, opendir, remove, rename, etc. should DTRT with symlinks.

And functions which are mere wrappers about int 0x21 calls (_open etc.)
do not understand symlinks by design. This may expose misuse of such
functions in programs, i.e. _open when open is required.

> 
> Compiling and linking a bunch of files in a directory that is a
> symlink might test quite a few of these functions.  In fact, you could
> try making the DJGPP installation directory be a symlink, and see if
> anything breaks, but that requires that you rebuild _everything_ with
> CVS libc.

Interesting suggestion. I think I should have to try it here.

Laurynas

- Raw text -