| 1 | <?xml version="1.0" encoding="UTF-8"?> |
1 | <?xml version="1.0" encoding="UTF-8"?> |
| 2 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
2 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.13 2008/05/23 20:42:42 swift Exp $ --> |
3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.14 2009/01/26 07:34:41 nightmorph Exp $ --> |
| 4 | |
4 | |
| 5 | <guide link="/doc/en/bugzilla-howto.xml"> |
5 | <guide link="/doc/en/bugzilla-howto.xml"> |
| 6 | <title>Gentoo Bug Reporting Guide</title> |
6 | <title>Gentoo Bug Reporting Guide</title> |
| 7 | |
7 | |
| 8 | <author title="Author"> |
8 | <author title="Author"> |
| … | |
… | |
| 18 | |
18 | |
| 19 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
19 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 20 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
20 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 21 | <license/> |
21 | <license/> |
| 22 | |
22 | |
| 23 | <version>1.11</version> |
23 | <version>1.12</version> |
| 24 | <date>2008-01-31</date> |
24 | <date>2009-01-25</date> |
| 25 | |
25 | |
| 26 | <chapter> |
26 | <chapter> |
| 27 | <title>Introduction</title> |
27 | <title>Introduction</title> |
| 28 | <section> |
28 | <section> |
| 29 | <title>Preface</title> |
29 | <title>Preface</title> |
| … | |
… | |
| 437 | |
437 | |
| 438 | <p> |
438 | <p> |
| 439 | Let's take a look at this very simple <c>emerge</c> error: |
439 | Let's take a look at this very simple <c>emerge</c> error: |
| 440 | </p> |
440 | </p> |
| 441 | |
441 | |
| 442 | <pre caption="emerge Error"> |
442 | <pre caption="emerge Error (long lines are manually wrapped to fit the window)"> |
| 443 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2-7.o foobar2-7.c |
|
|
| 444 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2-8.o foobar2-8.c |
|
|
| 445 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2-9.o foobar2-9.c |
|
|
| 446 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2.o foobar2.c |
443 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
444 | -c -o foobar2-7.o foobar2-7.c |
|
|
445 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
446 | -c -o foobar2-8.o foobar2-8.c |
|
|
447 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
448 | -c -o foobar2-9.o foobar2-9.c |
|
|
449 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
450 | -c -o foobar2.o foobar2.c |
| 447 | foobar2.c:1:17: ogg.h: No such file or directory |
451 | foobar2.c:1:17: ogg.h: No such file or directory |
| 448 | make: *** [foobar2.o] Error 1 |
452 | make: *** [foobar2.o] Error 1 |
| 449 | |
453 | |
| 450 | !!! ERROR: sys-apps/foobar2-1.0 failed. |
454 | !!! ERROR: sys-apps/foobar2-1.0 failed. |
| 451 | !!! Function src_compile, Line 19, Exitcode 2 |
455 | !!! Function src_compile, Line 19, Exitcode 2 |
| … | |
… | |
| 457 | The program is compiling smoothly when it suddenly stops and presents an error |
461 | The program is compiling smoothly when it suddenly stops and presents an error |
| 458 | message. This particular error can be split into 3 different sections, The |
462 | message. This particular error can be split into 3 different sections, The |
| 459 | compile messages, the build error, and the emerge error message as shown below. |
463 | compile messages, the build error, and the emerge error message as shown below. |
| 460 | </p> |
464 | </p> |
| 461 | |
465 | |
| 462 | <pre caption="Parts of the error"> |
466 | <pre caption="Parts of the error (long lines are manually wrapped to fit the window)"> |
| 463 | <comment>(Compilation Messages)</comment> |
467 | <comment>(Compilation Messages)</comment> |
| 464 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2-7.o foobar2-7.c |
|
|
| 465 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2-8.o foobar2-8.c |
|
|
| 466 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2-9.o foobar2-9.c |
|
|
| 467 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod -c -o foobar2.o foobar2.c |
468 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
469 | -c -o foobar2-7.o foobar2-7.c |
|
|
470 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
471 | -c -o foobar2-8.o foobar2-8.c |
|
|
472 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
473 | -c -o foobar2-9.o foobar2-9.c |
|
|
474 | gcc -D__TEST__ -D__GNU__ -D__LINUX__ -L/usr/lib -I/usr/include -L/usr/lib/nspr/ -I/usr/include/fmod \ |
|
|
475 | -c -o foobar2.o foobar2.c |
| 468 | |
476 | |
| 469 | <comment>(Build Error)</comment> |
477 | <comment>(Build Error)</comment> |
| 470 | foobar2.c:1:17: ogg.h: No such file or directory |
478 | foobar2.c:1:17: ogg.h: No such file or directory |
| 471 | make: *** [foobar2.o] Error 1 |
479 | make: *** [foobar2.o] Error 1 |
| 472 | |
480 | |
| … | |
… | |
| 522 | most likely have to create it. If you do not, portage will fail to write the |
530 | most likely have to create it. If you do not, portage will fail to write the |
| 523 | logs. |
531 | logs. |
| 524 | </note> |
532 | </note> |
| 525 | |
533 | |
| 526 | <pre caption="emerge-ing With PORT_LOGDIR"> |
534 | <pre caption="emerge-ing With PORT_LOGDIR"> |
| 527 | # <i>PORT_LOGDIR=/var/log/portage emerge foobar2</i> |
535 | # <i>PORT_LOGDIR=/var/log/portage emerge cate-gory/foobar2</i> |
| 528 | </pre> |
536 | </pre> |
| 529 | |
537 | |
| 530 | <p> |
538 | <p> |
| 531 | Now the emerge fails again. However, this time we have a log we can work with, |
539 | Now the emerge fails again. However, this time we have a log we can work with, |
| 532 | and attach to the bug later on. Let's take a quick look at our log directory. |
540 | and attach to the bug later on. Let's take a quick look at our log directory. |
| … | |
… | |
| 535 | <pre caption="PORT_LOGDIR Contents"> |
543 | <pre caption="PORT_LOGDIR Contents"> |
| 536 | # <i>ls -la /var/log/portage</i> |
544 | # <i>ls -la /var/log/portage</i> |
| 537 | total 16 |
545 | total 16 |
| 538 | drwxrws--- 2 root root 4096 Jun 30 10:08 . |
546 | drwxrws--- 2 root root 4096 Jun 30 10:08 . |
| 539 | drwxr-xr-x 15 root root 4096 Jun 30 10:08 .. |
547 | drwxr-xr-x 15 root root 4096 Jun 30 10:08 .. |
| 540 | -rw-r--r-- 1 root root 7390 Jun 30 10:09 2115-foobar2-1.0.log |
548 | -rw-r--r-- 1 root root 7390 Jun 30 10:09 cate-gory:foobar2-1.0:20090110-213217.log |
| 541 | </pre> |
549 | </pre> |
| 542 | |
550 | |
| 543 | <p> |
551 | <p> |
| 544 | The log files have the format [counter]-[package name]-[version].log. Counter |
552 | The log files have the format [category]:[package name]-[version]:[date].log. A |
| 545 | is a special variable that is meant to state this package as the n-th package |
|
|
| 546 | you've emerged. This prevents duplicate logs from appearing. A quick look at |
|
|
| 547 | the log file will show the entire emerge process. This can be attached later |
553 | quick look at the log file will show the entire emerge process. This can be |
| 548 | on as we'll see in the bug reporting section. Now that we've safely obtained |
554 | attached later on as we'll see in the bug reporting section. Now that we've |
| 549 | our information needed to report the bug we can continue to do so. However, |
555 | safely obtained our information needed to report the bug we can continue to do |
| 550 | before we get started on that, we need to make sure no one else has reported |
556 | so. However, before we get started on that, we need to make sure no one else |
| 551 | the issue. Let's take a look at searching for bugs. |
557 | has reported the issue. Let's take a look at searching for bugs. |
| 552 | </p> |
558 | </p> |
| 553 | |
559 | |
| 554 | </body> |
560 | </body> |
| 555 | </section> |
561 | </section> |
| 556 | </chapter> |
562 | </chapter> |