| 1 |
On Wednesday 02 Sep 2015 05:57:49 wraeth wrote: |
| 2 |
> On 02/09/15 14:24, thelma@×××××××××××.com wrote: |
| 3 |
> > On 09/01/2015 08:57 PM, wraeth wrote: |
| 4 |
> >> On 02/09/15 12:23, Fernando Rodriguez wrote: |
| 5 |
> >>> He was told what the problem was on his first post about |
| 6 |
> >>> libjpeg-turbo, he didn't just ignore it but posted the wrong |
| 7 |
> >>> solution with a big SOLVED on the subject that only serves to |
| 8 |
> >>> mislead future users of this list. On his last post about this |
| 9 |
> >>> same error (different package) I politely told him to go back |
| 10 |
> >>> and follow the advise on that post, again he ignored it and |
| 11 |
> >>> posted a bogus solution (it worked because he rebuilt tiff, |
| 12 |
> >>> perl had nothing to do with it). revdep-rebuild may (or may |
| 13 |
> >>> not) fix it now, but the right solution is to remove or fix the |
| 14 |
> >>> obsolete package to depend on virtual/jpeg, update world |
| 15 |
> >>> properly, and then revdep-rebuild to undo this mess. |
| 16 |
> > |
| 17 |
> > Apology if I didn't most enough information. I know should have |
| 18 |
> > post "emerge --info" but when it comes to error log. It is very, |
| 19 |
> > very long and email wouldn't be able to accept it; so I cat the |
| 20 |
> > ending message as this is the point it stop compiling. |
| 21 |
> |
| 22 |
> For large files, you can either paste the file to a pastebin service |
| 23 |
> and give us the URL, compress it with gzip or bzip2 and attach that, |
| 24 |
> or give us the last 250 lines or so. |
| 25 |
> |
| 26 |
> The reason for this is because the error you see in the logs may not |
| 27 |
> be the first error or the one that is causing the build to fail - the |
| 28 |
> more information we have, the more information available to help |
| 29 |
> resolve an issue. |
| 30 |
> |
| 31 |
> Either way, no harm done. |
| 32 |
> |
| 33 |
> > Emergeing "x11-libs/wxGTK" did not help. |
| 34 |
> |
| 35 |
> I haven't been following along with the threads, but as far as I |
| 36 |
> understand there's an obsolete package that has a dependency that |
| 37 |
> conflicts with newer packages. If that's the case, you would need to |
| 38 |
> deal with that obsolete package. |
| 39 |
> |
| 40 |
> There's also been suggestion of using revdep-rebuild - have you tried |
| 41 |
> that? |
| 42 |
|
| 43 |
First check that you have not inadvertently added any virtual packages in |
| 44 |
/var/lib/portage/world. If so remove them, portage will bring them back if |
| 45 |
needed. Then use: |
| 46 |
|
| 47 |
emerge -uaNDv world |
| 48 |
emerge --depclean -p -v |
| 49 |
emerge @preserved-rebuild -p |
| 50 |
revdep-rebuild -v -- -a |
| 51 |
|
| 52 |
perl-cleaner is also a good to run anytime portage updates any perl packages. |
| 53 |
|
| 54 |
Have a look at 'man qdepends' for direct and reverse dependencies of different |
| 55 |
packages. In your case jpeg seems to be borked, so investigate jpeg and jpeg |
| 56 |
libraries with the above tools to see what may be causing the problem. It |
| 57 |
could be that a package is in world that shouldn't be, or it could be that you |
| 58 |
have some USE flag set that forces portage into a knot. |
| 59 |
|
| 60 |
HTH. |
| 61 |
-- |
| 62 |
Regards, |
| 63 |
Mick |
Archives