5 messages in com.perforce.jamming[jamming] Library rule quirks with LO...
FromSent OnAttachments
John...@nanaon-sha.co.jp30 Jun 2000 01:00 
Dave...@vignette.com03 Jul 2000 11:14 
Dian...@yahoo.com03 Jul 2000 20:07 
Dave...@creo.com04 Jul 2000 14:18 
Roesler07 Jul 2000 18:28 
Subject:[jamming] Library rule quirks with LOCATE
From:Dave...@vignette.com (Dave@vignette.com)
Date:07/03/2000 11:14:51 AM
List:com.perforce.jamming

> Has anyone run in to the following? A known bug? I'm running on linux with > recent binutils.

we have not encountered this on solaris or nt.

> > When LOCATE is set on a library target (or MakeLocate rule used), strange > things start happening: > > * The target is always remade even when it's current. Setting NOARSCAN > option flag seems to fix this (at a performance cost).

I would guess that this means the dependencies are always out of date, possibly because the thing built is not the same thing that the dependency is expressed
on.

> > * If the KEEPOBJS option flag is set, the library won't be created.

dunno about this.

dave

> > --John Belmonte > > > _______________________________________________ > jamming mailing list - jamm@perforce.com > http://maillist.perforce.com/mailman/listinfo/jamming >