| 1 |
Alan McKinnon wrote: |
| 2 |
> On 02/09/2015 06:57, wraeth wrote: |
| 3 |
>> On 02/09/15 14:24, thelma@×××××××××××.com wrote: |
| 4 |
>>> On 09/01/2015 08:57 PM, wraeth wrote: |
| 5 |
>>>> On 02/09/15 12:23, Fernando Rodriguez wrote: |
| 6 |
>>>> |
| 7 |
>>>>> He was told what the problem was on his first post about |
| 8 |
>>>>> libjpeg-turbo, he didn't just ignore it but posted the wrong |
| 9 |
>>>>> solution with a big SOLVED on the subject that only serves to |
| 10 |
>>>>> mislead future users of this list. On his last post about this |
| 11 |
>>>>> same error (different package) I politely told him to go back |
| 12 |
>>>>> and follow the advise on that post, again he ignored it and |
| 13 |
>>>>> posted a bogus solution (it worked because he rebuilt tiff, |
| 14 |
>>>>> perl had nothing to do with it). revdep-rebuild may (or may |
| 15 |
>>>>> not) fix it now, but the right solution is to remove or fix the |
| 16 |
>>>>> obsolete package to depend on virtual/jpeg, update world |
| 17 |
>>>>> properly, and then revdep-rebuild to undo this mess. |
| 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 |
>> 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 |
> Every list has their own particular preference to things. Here on |
| 27 |
> gentoo-user, since the very beginning, list users have preferred to not |
| 28 |
> use pastebin services - they go away and the real information is forever |
| 29 |
> lost. |
| 30 |
> |
| 31 |
> There's never a good reason for use needing an entire build log if it's |
| 32 |
> big, it's fine to find the first error in the log and send from there to |
| 33 |
> the end. Users quickly discover how to find the first error. |
| 34 |
> |
| 35 |
|
| 36 |
|
| 37 |
I have found that it is usually "Error 1". That's what I put in the |
| 38 |
Find thingy to look for IF it is not real close by. I generally go up a |
| 39 |
few lines and then start my copy and paste. |
| 40 |
|
| 41 |
I can't count how many times I have searched for a problem and run into |
| 42 |
paste bin links that no longer work. It is really aggravating when you |
| 43 |
think you found something and it turns out it has disappeared. |
| 44 |
|
| 45 |
Dale |
| 46 |
|
| 47 |
:-) :-) |
Archives