From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: [wwwdocs,Java] java/faq.html -- remove non-FAQ covered by installation documentation
Date: Fri, 02 Nov 2012 20:02:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1211022058440.2266@tuna.site> (raw)
This is covered in the installation documentation and really not
specific to GCJ (and probably predates the merge of GCJ into GCC).
Also, it's not really an FAQ in this context.
Better focus on what is really relevant..
Applied.
Gerald
2012-11-02 Gerald Pfeifer <gerald@pfeifer.com>
* faq.html: Remove question about building in the source tree.
Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/faq.html,v
retrieving revision 1.68
diff -u -3 -p -r1.68 faq.html
--- faq.html 1 Nov 2012 23:25:30 -0000 1.68
+++ faq.html 2 Nov 2012 19:58:38 -0000
@@ -37,7 +37,6 @@
<li><a href="#3_1">I need something more recent than the last release; how
should I build it?</a></li>
<li><a href="#3_2">Linker bug on Solaris</a></li>
- <li><a href="#3_3">Can I configure/build in the source tree?</a></li>
</ol>
</li>
<li><a href="#4_0">Gcj Compile/Link Questions</a>
@@ -306,26 +305,6 @@ collect2: ld returned 1 exit status
</dd>
</dl>
- <hr />
- <h3><a name="3_3">3.3 Can I configure/build in the source tree?</a></h3>
- <dl>
- <dd>
- No. You cannot configure/build in the source tree. If you try,
- you'll see something like:
- <pre>
-$ ./configure [...]
-Configuring for a i686-pc-linux-gnu host.
-*** Cannot currently configure in source tree.
- </pre>
- Instead, you must build in another directory. E.g.:
- <pre>
-$ mkdir build
-$ cd build
-$ ../configure [...]
- </pre>
- </dd>
- </dl>
-
<h2><a name="4_0">Gcj Compile/Link Questions</a></h2>
<h3><a name="4_1">4.1 Why do I get <tt>undefined reference to `main'</tt>
reply other threads:[~2012-11-02 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1211022058440.2266@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).