Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3D0C576F.F032D9C@phekda.freeserve.co.uk>
Date:	Sun, 16 Jun 2002 10:16:31 +0100
From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Clio 2.04 packages
References:	<001601c21399$28e58650$0100a8c0 AT p4> <2110-Sat15Jun2002190312+0300-eliz AT is DOT elta DOT co DOT il> <003201c214f9$6efb9970$0100a8c0 AT p4>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Andrew Cottrell wrote:
[snip]
> I have not found that I have had to do any reconfiguring or source code
> changes to any of the packages, but then again I have not fully tested
> symlinks. Some of the packages install the new symlinks instead of the old
> ones in the bin directory. So far I have not had any problems with symlinks,
> except last year when mixing old and new exes with new symlinks.

Fileutils will definitely need reconfiguring to work properly with DJGPP 2.04.

Incidentally GMP's configure process will use symlinks. It has a bunch of
processor-specific code. When you configure, it creates symlinks from a source
area to the processor-specific code that it will use. Perhaps this would be
useful for testing symlinks. Note that GMP takes a while to build - half an
hour on an Athlon 850MHz, I guess.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -