gnupic@linuxhacker.org

On Sat, Oct 25, 2003 at 09:09:11PM -0500, Martin McCormick wrote:
> 	One other thing I discovered is that it is best to delete the
> gpsim-0.20.14 directory and untar it again to start fresh.  I did a
> make clean and re-ran configure, but I kept getting the popt.h error
> until I started over.

This will likely be due to caching by configure.  The configure script 
saves it's results to config.cache in the current directory.  If you 
change your system, it is best to either delete the cache or edit it 
to remove the relevant results.  I generally just delete it.

(Two other tools I'm beginning to love are ccache and distcc.  The 
former caches the results of C compile runs using MD5 signatures, and 
the latter distributes the compiles across a set of machines.  My build
environment consists of six machines, two of which are single board
computers that run from 5V and have no other current purpose.  I haven't
tried running gpasm within distcc yet though.  gpasm is just too fast
as it is.  ;-)  )

-- 
James Cameron    mailto:quozl@us.netrek.org     http://quozl.netrek.org/