gEDA: Snapshot 20021022

[Andrew Bardsley <bardslea@cs.man.ac.uk>]

Arrgggh! I hadn't fixed --prefix.  OK, deep breaths, calm thoughts.
OK, here's what I'm doing now:

Firstly find an absolute (well, w/o ${vars}) prefix

if test "x${prefix}" = xNONE; then
	waveprefix="${ac_default_prefix}"
else
	waveprefix="${prefix}"
fi

Then propagate that to exec_prefix and wavedatadir

if test "x${exec_prefix}" = xNONE; then
	exec_prefix="${waveprefix}"
fi

if test "x${datadir}" = "x\${prefix}/share"; then
	wavedatadir="${waveprefix}/share/${PACKAGE}"
else
	wavedatadir="${datadir}/${PACKAGE}"
fi

*Hopefully* this will fix most people's problem (again ;).  I've made a
new snapshot: 20021022.  Again this snapshot is only of interest if you're
having trouble.

Two bugs have become evident while making this `fix':
1) Using spaces in prefix/exec_prefix works fine and dandy with
   configure now but automake/autoconf's DATA install rules don't
   seem too happy with spaces.  This is naturally a prob. for
   those tools in general then.
2) For reasons beyond my current ken, using something like
   ./configure --prefix="/tmp/prefix prefix" (which I tried to test
   out spaces in paths) causes configure to start worrying about
   site configuration scripts.  --prefix="/a a" worked fine!
   (well, apart from the thing about DATA installs)

Phew.  Thanks to all who pointed out these problems.  Please continue
to keep me on my toes.

- Andrew 
    _______________
___/Andrew Bardsley\____________________________________________
University of Manchester Dept. of Computer Science  AMULET Group
Research Associate bardsleyATcs.man.ac.uk  Tel: +44 161 275 6844
Snail: Room IT302, Man. Uni., Oxford Rd, Manchester, M13 9PL, UK