1 |
On 02/09/2015 06:57, 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 |
>>> |
6 |
>>>> He was told what the problem was on his first post about |
7 |
>>>> libjpeg-turbo, he didn't just ignore it but posted the wrong |
8 |
>>>> solution with a big SOLVED on the subject that only serves to |
9 |
>>>> mislead future users of this list. On his last post about this |
10 |
>>>> same error (different package) I politely told him to go back |
11 |
>>>> and follow the advise on that post, again he ignored it and |
12 |
>>>> posted a bogus solution (it worked because he rebuilt tiff, |
13 |
>>>> perl had nothing to do with it). revdep-rebuild may (or may |
14 |
>>>> not) fix it now, but the right solution is to remove or fix the |
15 |
>>>> obsolete package to depend on virtual/jpeg, update world |
16 |
>>>> properly, and then revdep-rebuild to undo this mess. |
17 |
> |
18 |
>> Apology if I didn't most enough information. I know should have |
19 |
>> post "emerge --info" but when it comes to error log. It is very, |
20 |
>> very long and email wouldn't be able to accept it; so I cat the |
21 |
>> ending message as this is the point it stop compiling. |
22 |
> |
23 |
> For large files, you can either paste the file to a pastebin service |
24 |
> and give us the URL, compress it with gzip or bzip2 and attach that, |
25 |
> or give us the last 250 lines or so. |
26 |
|
27 |
|
28 |
Every list has their own particular preference to things. Here on |
29 |
gentoo-user, since the very beginning, list users have preferred to not |
30 |
use pastebin services - they go away and the real information is forever |
31 |
lost. |
32 |
|
33 |
There's never a good reason for use needing an entire build log if it's |
34 |
big, it's fine to find the first error in the log and send from there to |
35 |
the end. Users quickly discover how to find the first error. |
36 |
|
37 |
-- |
38 |
Alan McKinnon |
39 |
alan.mckinnon@×××××.com |