Re: [guppi-list] Re: guppi segfault




On Wed, 30 Jun 1999, Thomas R. Shannon wrote:
> 
> Hmmm.  I suppose this means that if I'm willing to compile guile from
> source, I can get this to work.  I really don't want to do that.  I
> lose track of what's rom and what isn't.
>

You shouldn't have to if Red Hat's dependencies are correct. That is, they
should have a Guile that matches the new libraries. Perhaps you only need
to recompile Goose? Did you compile it or part of of it before upgrading?
I would be sure you have the latest header files (does RH put these in
-devel packages?) and then make clean and rebuild everything. 

> Why does guppi run on the machine that had the clean RH6 install?
> That is the one that wasn't upgraded from RH5.2?
> 

Because something is broken about the install or how Guppi was compiled -
that's all I can think of to say. :-( It's fairly hard to track down this
sort of problem; what happens is that the library isn't what the program
expects, so the program tries to read or write some memory that isn't
there, and it causes a segmentation fault in some random location. The
random location doesn't really give a clue about which library is at fault
or what part of the program expected the old library. I'm guessing
libstdc++ simply because libc 2.1 seems to be binary compatible in many
other instances.

Havoc




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