public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: [wwwdocs,Java] Remove five obsolete entries from java/faq.html
Date: Sat, 28 Jun 2014 17:18:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1406281909570.30120@tuna.site> (raw)

REQUEST FOR HELP:  It would be great if one of the Java experts
could advise which further entries to remove or adjust.  I volunteer
to make the actual changes, if that helps.


Now to this patch: Working on the web pages in general, I noticed a 
number of obsolete FAQ entries in our Java FAQ.  Some of them are 
(better) covered in our general documentation, some of them refer 
to really old versions of GCC.

For example, x86-64 is not included in the supported platforms 
mentioned, one entry talks about version before 3.0,...

Applied.

Gerald

2014-06-28  Gerald Pfeifer  <gerald@pfeifer.com>

        * faq.html: Remove five obsolete entries.

Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/faq.html,v
retrieving revision 1.72
diff -u -r1.72 faq.html
--- faq.html	28 Jun 2014 07:45:14 -0000	1.72
+++ faq.html	28 Jun 2014 17:09:44 -0000
@@ -11,8 +11,6 @@
         <li><a href="#1_0">General Questions</a> 
           <ol>
             <li><a href="#1_1">What license is used for libgcj?</a></li>
-            <li><a href="#1_3">How can I contribute to libgcj</a></li>
-            <li><a href="#1_5">Will gcj and libgcj work on my machine?</a></li>
             <li><a href="#1_6">How can I debug my Java program?</a></li>
             <li><a href="#1_7">Can I interface byte-compiled and native java code?</a></li>
           </ol>
@@ -32,12 +30,6 @@
             <li><a href="#2_8">What features of the Java language are/arn't supported</a></li>
           </ol>
         </li>
-        <li><a href="#3_0">Build Issues</a> 
-          <ol>
-            <li><a href="#3_1">I need something more recent than the last release; how
-                  should I build it?</a></li>
-          </ol>
-        </li>
         <li><a href="#4_0">Gcj Compile/Link Questions</a> 
           <ol>
             <li><a href="#4_1">Why do I get <tt>undefined reference to `main'</tt> 
@@ -48,8 +40,6 @@
             <li><a href="#4_4">Where does GCJ look for files? </a></li>
             <li><a href="#4_5">How does gcj resolve wether to compile .class or 
               .java files? </a></li>
-            <li><a href="#4_6">I'm getting link errors!</a></li>
-            <li><a href="#4_7">I'm getting 'undefined symbol: __dso_handle'</a></li>
           </ol>
         </li>
         <li><a href="#5_0">Runtime Questions</a> 
@@ -87,28 +77,6 @@
       </dl>
       
       <hr />
-      <h3><a name="1_3">1.3 How can I contribute to libgcj?</a></h3>
-      <dl> 
-        <dd>
-          You can send simple bug fixes in as patches. Please follow the <a href="http://gcc.gnu.org/contribute.html">GCC 
-          guidelines for submitting patches</a>. For more complex changes, you 
-          must sign copyright over to the Free Software Foundation. See the <a href="contrib.html">contribution</a> 
-          page for details.
-        </dd>
-      </dl>
- 
-      <hr />
-      <h3><a name="1_5">1.5 Will gcj and libgcj work on my machine?</a></h3>
-      <dl> 
-        <dd>
-          Gcj and libgcj are known to work more or less with IA-32 and 
-          SPARC Solaris, Tru64 Unix, as well as IA-32, IA-64, Alpha, and PowerPC 
-          Linux. They might work on other systems. Generally speaking, porting to a new 
-          system should not be hard. This would be a good way to volunteer.
-        </dd>
-      </dl>
- 
-      <hr />
       <h3><a name="1_6">1.6 How can I debug my Java program?</a></h3>
       <dl> 
         <dd>
@@ -267,15 +235,6 @@
         </dd>
       </dl>
       
-      <h2><a name="3_0">Build Issues</a></h2>
-
-      <h3><a name="3_1">3.1 I need something more recent than the last release. 
-          How should I build it?</a></h3>
-      <dl> 
-        <dd>
-          Please read <a href="build-snapshot.html">here</a>.
-        </dd>
-      </dl>
 
       <h2><a name="4_0">Gcj Compile/Link Questions</a></h2>
  
@@ -352,36 +311,6 @@
         </dd>
       </dl>
       
-      <hr />
-      <h3><a name="4_6">4.6 I'm getting link errors</a></h3>
-
-      <dl>
-        <dd>
-          <p>If you get errors at link time that refer to
-          'undefined reference to `java::lang::Object type_info function',
-          verify that you have compiled any CNI C++ files with the
-          -fno-rtti option. This is only required for versions of GCJ earlier 
-          than 3.0.</p>
-        </dd>
-      </dl>
-
-      <hr />
-      <h3><a name="4_7">4.7 I'm getting 'undefined symbol: __dso_handle'</a></h3>
-      <dl>
-        <dd>
-          <p>Some versions of the GNU linker have broken support for the '.hidden'
-          directive, which results in problems with shared libraries built with
-          recent versions of gcc. </p>
-        
-          <p>There are three solutions: </p>
-          <ul>
-            <li>downgrade to binutils that don't support .hidden at all,</li>
-            <li>upgrade to a recent binutils, or</li>
-            <li>undef the HAVE_GAS_HIDDEN definition in gcc's auto-host.h
-            (and rebuild gcc).</li>
-          </ul>
-        </dd>
-      </dl>
       
       <h2><a name="5_0">Runtime Questions</a></h2>
  

                 reply	other threads:[~2014-06-28 17:18 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.LSU.2.11.1406281909570.30120@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).