Chris Seawood wrote:
>
> Stuart Ballard wrote:
> >
>
> > Now it won't even configure because the --enable-crypto is incompatible
> > with not having MOZ_NSS_AUTOCONF. Or at least that's what it says.
> > Should this not be true any longer?
>
> That's definitely not true any longer. It sounds like your tree didn't
> get completely updated from 0.9.
> What happens when you do 'cvs up -A client.mk' and then try to repull ?
cvs up -A client.mk has no effect (returns to the prompt without giving
a U or P line for client.mk). So I already had the latest client.mk.
Last time I did a pull (a few hours ago) nothing got pulled (using make
-f client.mk checkout), except for the NSS stuff when I commented out
NSS_AUTOCONF which produced a whole bunch of conflicts (because
Makefiles got pulled and autoconf had generated them). I removed these
and re-pulled and all I got was NSS.
Is it possible that I need to do some clobbering beyond what "make -f
client.mk clobber" does? (actually I got the NSS_AUTOCONF
incompatibility message from make clobber because it seems to run
configure before it runs clobber...)
Thoughts?
Stuart.
PS Thanks for the help so far - sorry nothing's worked yet
