Re: [gentoo-desktop] Re: [kde-sunset] kmail-3.5.10 crashes

[Nicholas Robbins]

Ok, pulled back to libpng1.2, and still have the crashed. Must have been a case of  post hoc ergo proptor hoc.  Before I rebuild again to get back to libpng1.4. How should I set my cflags and useflags to allow for debugging this?

--- On Thu, 7/8/10, Nicholas Robbins <nickrobbins@×××××.com> wrote:

> From: Nicholas Robbins <nickrobbins@×××××.com>
> Subject: Re: [gentoo-desktop] Re: [kde-sunset] kmail-3.5.10 crashes
> To: gentoo-desktop@l.g.o
> Date: Thursday, July 8, 2010, 5:00 PM
> I don't think I had any traces of
> libpng1.2. I followed these steps for updating my libpng.
>
> http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update
>
> So I had no traces of the old version. I haven't been using
> --as-needed.
>
> I depclean and revdep after every update, I have
> buildpackage in my features. My machine is already doing
> it's revdep back to 1.2. Hopefully it will be done when I
> get back in to work tomorrow. I'll let you know if that
> helps.
>
> --- On Thu, 7/8/10, Duncan <1i5t5.duncan@×××.net>
> wrote:
>
> > From: Duncan <1i5t5.duncan@×××.net>
> > Subject: [gentoo-desktop] Re: [kde-sunset]
> kmail-3.5.10 crashes
> > To: gentoo-desktop@l.g.o
> > Date: Thursday, July 8, 2010, 4:16 PM
> > Nicholas Robbins posted on Thu, 08
> > Jul 2010 08:09:24 -0700 as excerpted:
> >
> > > Just a me-too message. I recently started having
> these
> > crashes as well.
> > > They started about when I upgraded to libpng1.4.
> >
> > Ugh.  Sounds like you still have the earlier
> version,
> > and some library
> > using it, while another pulls in the new version, with
> both
> > used by kmail,
> > so it's pulling in both versions into the same
> executable,
> > and that's a
> > certain recipe for disaster, or at least crashes.
> >
> > I take it you've completed a revdep-rebuild and
> running it
> > now comes up
> > clean?  Do you run with as-needed in your
> > ldflags?  That will certainly
> > help, as will having lafilefixer in your portage
> > post-install hooked
> > routines.  (If you don't know what I'm talking
> about,
> > you may want to read
> > up on flameeyes' blog... the mentioned tricks can
> > definitely save you a
> > **LOT** of trouble.)
> >
> > What about depclean?  Do you use it regularly?
> >
> > If you're not doing that sort of stuff routinely, it
> may be
> > that a
> > complete emerge --emptytree world is needed to get
> the
> > cruft cleaned out,
> > but before you go to that trouble, I'd suggest setting
> up
> > as-needed in
> > your ldflags, lafilefixer in your post-install, doing
> a
> > --depclean --
> > pretend and adding to world what you don't want
> removed,
> > and consider
> > setting FEATURES=buildpkg, before you do the rebuild,
> so
> > that when you're
> > done, you'll have the full world built cleanly with
> those
> > options, and
> > binpkg backups for every package, as well.  After
> that
> > it should be MUCH
> > easier to keep up with routine maintenance, always
> doing a
> > revdep-rebuild
> > and a depclean (I always use ask, to see what it's
> going to
> > do, before
> > letting it go ahead, for both of these), after every
> update
> > or package
> > removal.
> >
> > --
> > Duncan - List replies preferred.   No HTML
> > msgs.
> > "Every nonfree program has a lord, a master --
> > and if you use the program, he is your master." 
> > Richard Stallman
> >
> >
> >
>
>
>
>
>