On Wednesday 02 Sep 2015 05:57:49 wraeth wrote:
> On 02/09/15 14:24, thelma@sys-concept.com wrote:
> > On 09/01/2015 08:57 PM, wraeth wrote:
> >> On 02/09/15 12:23, Fernando Rodriguez wrote:
> >>> He was told what the problem was on his first post about
> >>> libjpeg-turbo, he didn't just ignore it but posted the wrong
> >>> solution with a big SOLVED on the subject that only serves to
> >>> mislead future users of this list. On his last post about this
> >>> same error (different package) I politely told him to go back
> >>> and follow the advise on that post, again he ignored it and
> >>> posted a bogus solution (it worked because he rebuilt tiff,
> >>> perl had nothing to do with it). revdep-rebuild may (or may
> >>> not) fix it now, but the right solution is to remove or fix the
> >>> obsolete package to depend on virtual/jpeg, update world
> >>> properly, and then revdep-rebuild to undo this mess.
> > 
> > Apology if I didn't most enough information. I know should have
> > post "emerge --info" but when it comes to error log.  It is very,
> > very long and email wouldn't be able to accept it; so I cat the
> > ending message as this is the point it stop compiling.
> 
> For large files, you can either paste the file to a pastebin service
> and give us the URL, compress it with gzip or bzip2 and attach that,
> or give us the last 250 lines or so.
> 
> The reason for this is because the error you see in the logs may not
> be the first error or the one that is causing the build to fail - the
> more information we have, the more information available to help
> resolve an issue.
> 
> Either way, no harm done.
> 
> > Emergeing "x11-libs/wxGTK" did not help.
> 
> I haven't been following along with the threads, but as far as I
> understand there's an obsolete package that has a dependency that
> conflicts with newer packages. If that's the case, you would need to
> deal with that obsolete package.
> 
> There's also been suggestion of using revdep-rebuild - have you tried
> that?

First check that you have not inadvertently added any virtual packages in 
/var/lib/portage/world.  If so remove them, portage will bring them back if 
needed.  Then use:

emerge -uaNDv world
emerge --depclean -p -v
emerge @preserved-rebuild -p
revdep-rebuild -v -- -a

perl-cleaner is also a good to run anytime portage updates any perl packages.

Have a look at 'man qdepends' for direct and reverse dependencies of different 
packages.  In your case jpeg seems to be borked, so investigate jpeg and jpeg 
libraries with the above tools to see what may be causing the problem.  It 
could be that a package is in world that shouldn't be, or it could be that you 
have some USE flag set that forces portage into a knot.

HTH.
-- 
Regards,
Mick