From: Charles Terry <cterry AT plinet DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Installing Allegro
Date: Fri, 17 Apr 1998 16:09:31 -0700
Organization: All USENET -- http://www.Supernews.com
Lines: 33
Message-ID: <3537E12B.4A88@plinet.com>
References: <D1FB30BBA491D1118E6D006097BCAE3927FB0D AT Probe-nt-2a DOT Probe DOT co DOT uk> <353778B9 DOT 825 AT plinet DOT com>
NNTP-Posting-Host: 207.174.3.140
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Charles Terry wrote:
> 
> Shawn Hargreaves wrote:
> >
> > Charles Terry writes:
> > > I don't know exactly why it happend but
> > > when I built the allegro library, <liballeg.a>it created it but
> > > didn't copy it to the %DJDIR%/lib directory.  I did it manually.
> >
> > That is rather worrying. It would be good if someone who has seen
> > this problem could investigate it, and try to find out why the
> > copy call is failing...
> >
> > > make all (i think) will build all the examples,tools,info docs,
> > > and the library, whereas make only builds the library.
> >
> > Not true. The default action is to build everything: you only
> > need to select other targets if you want to specifically recompile
> > a particular program.
> >
> >         Shawn Hargreaves.
Well I deleted the object files and ran make again to check.

This time it ran perrrfict! 

I don't know what happened last time- I've got zero configuration
changes.

Maybe the Microsoft Copy Command doesn't work on Tuesdays :)

Charles Terry