X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/66a69320b2185caae6d56734f715a018337022ce..dda7aa54b68eab08eec6f5279637ed047cacfcdd:/doc/FAQ diff --git a/doc/FAQ b/doc/FAQ index 5dbd665f..1e10be1d 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -12,9 +12,23 @@ A1. If you're looking for a guarantee or certification, I can't ---------------------------------------------------------------------- -Q2. I'm having trouble using Bison. Where can I find help? +Q2. I can't build Bison because "make" complains that "msgfmt" is not + fund. What should I do? + +A2. Like most GNU packages with internationalization support, that + feature is turned on by default. If you have problems building + in the "po" subdirectory, it indicates that your system's + internationalization support is lacking. You can re-configure + Bison with "--disable-nls" to turn off this support, or you can + install GNU gettext from ftp://ftp.gnu.org/gnu/gettext/ and + re-configure Bison. See the file "ABOUT-NLS" for more + information. -A2. First, read the fine manual which comes with bison. Beyond that, +---------------------------------------------------------------------- + +Q3. I'm having trouble using Bison. Where can I find help? + +A3. First, read the fine manual which comes with bison. Beyond that, you can send mail to . This mailing list is intended to be populated with people who are willing to answer questions about using and installing Bison. Please keep in mind @@ -27,9 +41,9 @@ A2. First, read the fine manual which comes with bison. Beyond that, ---------------------------------------------------------------------- -Q3. I found a bug. What should I include in the bug report? +Q4. I found a bug. What should I include in the bug report? -A3. Before you send a bug report, make sure you are using the latest +A4. Before you send a bug report, make sure you are using the latest version. Check ftp://ftp.gnu.org/pub/gnu/bison/ or one of its mirrors. Be sure to include the version number in your bug report. If the bug is present in the latest version but not in a @@ -37,7 +51,9 @@ A3. Before you send a bug report, make sure you are using the latest did not contain the bug. If the bug is parser-related, you should include the smallest - grammar you can which demonstrates the bug. The smaller and + grammar you can which demonstrates the bug. The grammar file + should also be complete (i.e., I should be able to run it through + Bison without having to edit or add anything). The smaller and simpler the grammar, the easier it will be to fix the bug. Include information about your compilation environment, including @@ -56,23 +72,22 @@ A3. Before you send a bug report, make sure you are using the latest ---------------------------------------------------------------------- -Q4. Will Bison ever have C++ support? +Q5. Will Bison ever have C++ support? -A4. Yes, it's in the works. I will need beta testers, however (and - people haven't exactly been lining up for the task). When this - feature is ready to be tested, it will be announced on the - bug-bison mailing list. If you're interested in testing C++ - support when it becomes available, please consider subscribing to - the list, especially if you are willing to beta test other - releases as well. +A5. Yes, it's in the works. Things are very chaotic right now, but + what little information floats around is posted to the bug-bison + mailing list. If you're interested in testing C++ support when + it becomes available, please consider subscribing to the list, + especially if you are willing to beta test other releases as + well. ---------------------------------------------------------------------- -Q5. What is involved in being a beta tester? +Q6. What is involved in being a beta tester? -A5. It's not terribly involved. Basically, you would download a test +A6. It's not terribly involved. Basically, you would download a test release, compile it, and use it to build and run a parser or two. - After that, you would either submit a bug report or a message + After that, you would submit either a bug report or a message saying that everything is okay. It is important to report successes as well as failures because test releases eventually become mainstream releases, but only if they are adequately @@ -86,9 +101,9 @@ A5. It's not terribly involved. Basically, you would download a test ---------------------------------------------------------------------- -Q6. How do I join the help-bison and bug-bison mailing lists? +Q7. How do I join the help-bison and bug-bison mailing lists? -A6. See http://www.gnu.org/ (the section about "GNU mailing lists") +A7. See http://www.gnu.org/ (the section about "GNU mailing lists") for more information. ----------------------------------------------------------------------