Dag-Erling Smørgrav wrote:
> In any case, this particular failure is most likely a result of not
> re-running autogen.sh and configure after updating the source tree.
>
Doh!
You're right. I usually do, I'm not sure how I overlooked that. Oh well,
sorry for the mailing list noise.
Thanks!
--
Denis Ahrens <[EMAIL PROTECTED]> writes:
> James Quacinella <[EMAIL PROTECTED]> writes:
> > I know tracking trunk is typically a bad idea, but I just wanted to
> > post this up. It seems the latest revision is giving me errors on
> > startup ("Cannot create working directory NONE/var/$hostname") bu
On 27.06.2007, at 23:16, James Quacinella wrote:
> Hello everyone.
>
> I know tracking trunk is typically a bad idea, but I just wanted to
> post
> this up. It seems the latest revision is giving me errors on startup
> ("Cannot create working directory NONE/var/$hostname") but I haven't
> chang
James Quacinella <[EMAIL PROTECTED]> writes:
> I know tracking trunk is typically a bad idea, but I just wanted to
> post this up. It seems the latest revision is giving me errors on
> startup ("Cannot create working directory NONE/var/$hostname") but I
> haven't changed the startup command line pa
Hello everyone.
I know tracking trunk is typically a bad idea, but I just wanted to post
this up. It seems the latest revision is giving me errors on startup
("Cannot create working directory NONE/var/$hostname") but I haven't
changed the startup command line parameters, which are as such:
va
