| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 02/09/15 14:24, thelma@×××××××××××.com wrote: |
| 5 |
> On 09/01/2015 08:57 PM, wraeth wrote: |
| 6 |
>> On 02/09/15 12:23, Fernando Rodriguez wrote: |
| 7 |
>> |
| 8 |
>>> He was told what the problem was on his first post about |
| 9 |
>>> libjpeg-turbo, he didn't just ignore it but posted the wrong |
| 10 |
>>> solution with a big SOLVED on the subject that only serves to |
| 11 |
>>> mislead future users of this list. On his last post about this |
| 12 |
>>> same error (different package) I politely told him to go back |
| 13 |
>>> and follow the advise on that post, again he ignored it and |
| 14 |
>>> posted a bogus solution (it worked because he rebuilt tiff, |
| 15 |
>>> perl had nothing to do with it). revdep-rebuild may (or may |
| 16 |
>>> not) fix it now, but the right solution is to remove or fix the |
| 17 |
>>> obsolete package to depend on virtual/jpeg, update world |
| 18 |
>>> properly, and then revdep-rebuild to undo this mess. |
| 19 |
> |
| 20 |
> Apology if I didn't most enough information. I know should have |
| 21 |
> post "emerge --info" but when it comes to error log. It is very, |
| 22 |
> very long and email wouldn't be able to accept it; so I cat the |
| 23 |
> ending message as this is the point it stop compiling. |
| 24 |
|
| 25 |
For large files, you can either paste the file to a pastebin service |
| 26 |
and give us the URL, compress it with gzip or bzip2 and attach that, |
| 27 |
or give us the last 250 lines or so. |
| 28 |
|
| 29 |
The reason for this is because the error you see in the logs may not |
| 30 |
be the first error or the one that is causing the build to fail - the |
| 31 |
more information we have, the more information available to help |
| 32 |
resolve an issue. |
| 33 |
|
| 34 |
Either way, no harm done. |
| 35 |
|
| 36 |
> Emergeing "x11-libs/wxGTK" did not help. |
| 37 |
|
| 38 |
I haven't been following along with the threads, but as far as I |
| 39 |
understand there's an obsolete package that has a dependency that |
| 40 |
conflicts with newer packages. If that's the case, you would need to |
| 41 |
deal with that obsolete package. |
| 42 |
|
| 43 |
There's also been suggestion of using revdep-rebuild - have you tried |
| 44 |
that? |
| 45 |
|
| 46 |
- -- |
| 47 |
wraeth <wraeth@×××××××××.au> |
| 48 |
GnuPG Key: B2D9F759 |
| 49 |
-----BEGIN PGP SIGNATURE----- |
| 50 |
Version: GnuPG v2 |
| 51 |
|
| 52 |
iF4EAREIAAYFAlXmgckACgkQXcRKerLZ91l+PQD+MpIWSe42Zy4FwRTpNYT8WLoS |
| 53 |
lSW4GdI7lOxtvmZ/TSEA/AvddwqMPOvbot6CUjlEi3NPMJTOnANCGXKbDMgR9ZUt |
| 54 |
=mtuq |
| 55 |
-----END PGP SIGNATURE----- |
Archives