The Blue Meanie wrote:
> On Sun, 3 Jul 2005 13:54:28 +0200,
> Christian Biere <[EMAIL PROTECTED]> wrote:
> > Do you have a stacktrace, the relevant log output or at least the
> > old fileinfo file? Otherwise, I'm not sure whether that's been fixed
> > or not.

> I'm afraid the only meaningful piece of data I have left is the assertion
> failure message:
 
> ** ERROR **: file glib-missing.c: line 379: assertion failed:
> (strlen(buf) < FILENAME_MAXBYTES)

That's most-likely sufficient. There were two bugs in this function
which I've just fixed. I recommend to download the CVS tarball and
re-compile gtk-gnutella.

> > You don't have to play the text adventure. Just run

> >   ./Configure -Oders [other options...]

> Ok, I'll go spend some time with the readme and see if I can get an
> all-in-one-pass config/build.  Is there an option for a file containing
> Configure options, or just command-line?

Configure creates config.sh. That's where you can also look for other
options you might want to pass with -D which are not mentioned in the
README. I don't think preserving this config.sh is such a good idea
but I'm not sure about that. Usually you don't have to re-run Configure.
Just run make depend and then make after a CVS update. Un-tar-ing
the CVS tarball over your current sources shouldn't be a problem.

> My answers are pretty consistent,
> and just using a file with settings would be way convenient.

You can always use a wrapper or the like.

-- 
Christian

Attachment: pgpSXknVdELmB.pgp
Description: PGP signature

Reply via email to