cvs commit: hints errors.txt

tushar at tushar at
Wed Oct 8 18:15:45 PDT 2003

tushar      03/10/08 19:15:45

  Modified:    .        errors.txt
  Updated Hint: errors
  Revision  Changes    Path
  1.3       +37 -9     hints/errors.txt
  Index: errors.txt
  RCS file: /home/cvsroot/hints/errors.txt,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -u -r1.2 -r1.3
  --- errors.txt	9 Oct 2003 01:14:47 -0000	1.2
  +++ errors.txt	9 Oct 2003 01:15:45 -0000	1.3
  @@ -25,6 +25,14 @@
   I have an error in program <fill in whatever is appropriate>!
  +First of all, is it really an error? If you find the option "-Werror" in the 
  +lines that calls gcc, the "error" you're facing could as well be a warning
  +(-Werror makes gcc handle all warnings as errors). You will often find warning 
  +and error messages mixed before the classical "make[1]: Error". A warning is 
  +something gcc complains about, but continues without error, while an error is 
  +something that stops you from compiling the package you are about to build.
  +To disable distracting warning messages, use "export CFLAGS="-w".
   Mostly further informations about the errors are missing, which is a nuisance
   for both the one who asks and the one who tries to answer, because of the
   annoying dialogue that is often following. I have to admid that the LFS mailing
  @@ -57,9 +65,12 @@
   1. Compile-time Errors
  -When you are about to ./configure && make && make install your package, you
  -sometimes get the error that something is missing or malformed or simply
  +First of all, check the package you are about to compile for files like README
  +and/or INSTALL. You can ship around most errors by strictly following those 
  +When you are about to build your package, you sometimes get the error that 
  +something is missing or malformed or simply uncompileable.
   1.1 ... not found
  @@ -201,7 +212,12 @@
   1.3 Hangup
   Hangups are the most annoying errors there are. Fortunately, they are as seldom
  -as annoying with Linux (unless you use bleeding edge sources only).
  +as annoying with Linux (unless you use bleeding edge sources only). Hangups are
  +mostly caused by endless loops, driver problems that leads to bus lockups, and
  +hardware issues (like defect capacitors in the CPU power supply, check for 
  +bursted ones). Infinite loops are easily spotted by the warnings of most 
  +compilers, the latter is harder to find. Try to downgrade the driver you think 
  +is responsible for the hangup and send a report to the relative mailing list.
   1.3.1 Full Hangup
  @@ -217,10 +233,18 @@
   1.3.2 Program-only Hangup
   If the program hangs up leaving the rest of the system intact, you can use the
  -kill command to get rid of it. 
  +appropriate of the kill/killall/xkill commands to get rid of it.
  +1.4 Other errors
  -Hope this was helpful!
  +If you get an errormessage not covered by this hint, check the relative 
  +mailinglists, enter the error message into google and look 1. if there is a 
  +newer version or 2. if a cvs version, if available, has the same error. If 
  +nothing else helps, ask in IRC or mail to the developers mailinglist or submit
  +a bug report. Remember to describe the error precisely and give enough 
  +informations about the system you are trying to build the package on.
  +May the source be with you!
  @@ -229,5 +253,9 @@
       * Initial Version, small additions.
  -Thanks to teemu for reminding me on "-I" and "-l" :-)
  +  [2003-10-08]
  +    * Almost forgot to give Tushar some credits, little changes and additions.
  +Thanks to teemu for reminding me on "-I" and "-l" as much as Tushar for the 
  +warning about warnings and ringing the bell of the "-w" option :-)

More information about the hints mailing list