| 1 |
Britaliope wrote: |
| 2 |
> Thank you very much ! |
| 3 |
> I really did not expect the error to appear so far up in the build.log |
| 4 |
> |
| 5 |
> Regards |
| 6 |
> Bruno MATEU |
| 7 |
> |
| 8 |
|
| 9 |
For future reference. If you use a terminal, like Konsole for example, |
| 10 |
that has a search function, search for error 1. That gets you pretty |
| 11 |
close to the error but just to be sure, I always go up about 30 lines or |
| 12 |
so and start my copy action there. Generally, it is good to just go all |
| 13 |
the way down to the command prompt and paste the whole thing or attach |
| 14 |
it as a file. I'd guess that gets all the needed info 99% of the time. |
| 15 |
While you doing that, see if the error rings a bell and leads to a |
| 16 |
solution without even having to wait on a reply here, forums etc etc. |
| 17 |
Sometimes, the error is one that gives you good clues. Sometimes it |
| 18 |
doesn't. |
| 19 |
|
| 20 |
Back when CPUs were single core, the error messages were fairly close to |
| 21 |
the bottom. After all, it was running one or two pieces of code at a |
| 22 |
time. With newer multi-core/threaded CPUs, that message gets further |
| 23 |
back the more cores/threads you have. |
| 24 |
|
| 25 |
I've never been one to say that the whole log should be attached unless |
| 26 |
it is fairly short, fails really early. Some build logs can get really |
| 27 |
huge. LOo, Firefox and such are just a couple I can think of. Finding |
| 28 |
the first failure and going back 30 lines or so should be a really good |
| 29 |
start. |
| 30 |
|
| 31 |
Hope that helps in the future. |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives