| 1 |
On Sun, 23 Mar 2014 19:48:38 +0200 |
| 2 |
Nikita Tropin <posixivist32@×××××.com> wrote: |
| 3 |
|
| 4 |
> See `config.log' for more details |
| 5 |
|
| 6 |
More details, warnings and errors can be found by reading the build.log |
| 7 |
from the bottom until you come across them; in this case, the above |
| 8 |
quote reveals that more details are in config.log. If you read up |
| 9 |
from the bottom of config.log, skipping the summary of variables; |
| 10 |
you'll find the actual error. |
| 11 |
|
| 12 |
> Am I need to do smth (e.g. register a bug) or it's my local problem? |
| 13 |
|
| 14 |
Yes, this way, the developers can fix it to avoid it from happening for |
| 15 |
other users too; can you comment with the output of `emerge --info` and |
| 16 |
attach build.log as well as config.log? Thank you in advance. |
| 17 |
|
| 18 |
If needed, resources with extra details about filing bug reports: |
| 19 |
|
| 20 |
- https://wiki.gentoo.org/wiki/Beautiful_bug_reports |
| 21 |
- https://wiki.gentoo.org/wiki/Bugzilla_HOWTO |
| 22 |
|
| 23 |
-- |
| 24 |
With kind regards, |
| 25 |
|
| 26 |
Tom Wijsman (TomWij) |
| 27 |
Gentoo Developer |
| 28 |
|
| 29 |
E-mail address : TomWij@g.o |
| 30 |
GPG Public Key : 6D34E57D |
| 31 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives