Re: [guppi-list] Re: help me test Guppi




On Sat, 15 May 1999, Teemu Ikonen wrote:
> 
> I tried to build guppi2 last night, but it didn't build out of the box  
> (ie. directly from the CVS). I had to copy goose.m4 from goose CVS to
> ./macros and after that autogen.sh ran fine.

You could also solve this by copying goose.m4 to
aclocalprefix/share/aclocal or by setting the ACLOCAL_FLAGS environment
variable to '-I gooseprefix/share/aclocal' - otherwise Guppi doesn't know
where to look for Goose, short of "find / -name goose.m4"

> I had to edit src/Makefile as
> I didn't want to build the component-guppi,

Crap, if you don't have Bonobo it is supposed to detect that
automatically. I'll try to improve this.

> but otherwise the build
> completed succesfully, although with a myriad of warnings.
> 	

They are almost all pointless const warnings (where the object is
logically const, but updates some kind of internal data structure).
They should be harmless. The other big slew of warnings is from the Guile
header files (the one about text after #endif and the ones about asm
volatile).

> When executing, I get to the splash screen and then it segfaults.
> 

Ouch. Can you get a backtrace? (If you don't know how, let me know.)
This is almost certainly a problem with libraries, but it could be a Guppi
bug.

> I used the gnome libraries from debian unstable, gnome-print and goose
> were compiled fresh from the CVS.
> 

I'm right now compiling on a fresh machine with that exact combination, so
if it doesn't work I'll let you know what was wrong.

Thanks for the info!

Havoc





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]