Errors
From CBLFS
Contents |
What to do about Errors
This is a question we are asked a lot on IRC and through the mailing lists. In this document we will tell you what information you can give us to provide enough detail on what has happened.
How to Ask for Help
If you would like our help with your issue, there are a few things will will need.
In IRC, you can put your error into a tool called pastebin, at http://pastebin.cross-lfs.org. This will visually show us what your seeing. When you click on the Send Button it will update the link. Write down the number that appears after http://pastebin.cross-lfs.org/. Our bot Sploosh on IRC can tell us the link using the following command:
!pastebin #
Compiler Errors
If you're optimizing more than the book says, or using a different package or version than the book says, please try again following the book's instructions.
Read what the error says, as it usually gives you a tell tail sign.
Common Information Needed for Assistance
What we will need to see to help is the error and the last 10 entries in your bash history.
This command will show your your last 10 bash entries.
history | tail -n 10
We will also need the following information so the right Developer can help you. This is also recommended information for opening a trac ticket at http://trac.cross-lfs.org.
Architecture : Sparc
Host Operating System : {Host Operating System Name and Version}
Which CLFS Book : {Embedded, Standard, Sysroot} {Release # or SVN}
32, 64, or Multilib : {32 bit, 64 bit, or Multilib}
What Section : {Section of the Book and the Name of the Section}
Command : {The exact command as typed in that gave the error}
Error Message : {Put in Exact Error}
For Cross-Tools Section up to Final-System also provide the information from the version-check Script on the Host System Prerequisites page.
Typos in Book
If you find a typo in a book, open up a Trac ticket. Explain the typo and we will correct it. To open up a ticket go to http://trac.cross-lfs.org.
What Not To Do
When giving information, in particular package version(s) or commands you used, please do NOT just say you "used what the book says" or anything similar, and do not simply paste commands from the book. This kind of response is typically just ignored, and if you do this, you will most likely be asked again to provide the needed info.
Never send anything directly to a developer. Use the mailing lists, IRC, or Trac. I would recommend always using Trac to make sure there is a record of your issue. If you send something directly it may get lost.
