Date:	Tue, 03 Oct 2000 19:35:04 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT inter DOT net DOT il
To:	pavenis AT lanet DOT lv
Message-Id:	<8011-Tue03Oct2000193503+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.5h
CC:	386sx AT my-deja DOT com, djgpp AT delorie DOT com
In-reply-to:	<39DA1504.32069.1631614@localhost> (pavenis@lanet.lv)
Subject:	Re: Building gdb 5.0
References:	<39DA1504 DOT 32069 DOT 1631614 AT localhost>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: pavenis AT lanet DOT lv
> Date: Tue, 3 Oct 2000 17:19:00 +0200
> 
> 2) The same but I set LFN=N for test

This configuration is not guaranteed to work.  Non-LFN build was only
tested on DOS, not on Windows.  (The difference is that on Windows,
the non-DJGPP programs, like COMMAND.COM, do not obey the LFN
environment variable.)

> Unpacking and configuring was Ok (except not significant 
> filename conflicts).

Hmm?  The special batch file which you should use to unpack is
supposed to rename files on the fly to prevent these conflicts.  How
come it didn't work for you?

Which files were in conflict, anyway?  Did you build stock v5.0
distribution or some snapshot?

>  Make failed due to attempt to make symbolic link
> (subdirectory bfd and perhaps others). Adding
> 	export ac_cv_prog_LN_S="cp -p"
> to djconfig.sh fixed that

???  Don't you have a share/config.site file?  It comes with Bash and
sets LN_S=ln.  This is what should take care of this problem, I think.

> (I think the time we'll able to expect symbolic
> links to be supported is not so near)

I didn't mean for the build to depend on symlinks.

- Raw text -