Ignore:
Timestamp:
Apr 27, 2004, 8:39:34 PM (21 years ago)
Author:
bird
Message:

GCC v3.3.3 sources.

Location:
branches/GNU/src/gcc
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/GNU/src/gcc

    • Property svn:ignore
      •  

        old new  
        2626configure.vr
        2727configure.vrs
         28dir.info
        2829Makefile
        29 dir.info
        3030lost+found
        3131update.out
  • branches/GNU/src/gcc/faq.html

    • Property cvs2svn:cvs-rev changed from 1.1 to 1.1.1.2
    r1390 r1391  
    1010
    1111<p>The latest version of this document is always available at
    12 <a href="http://www.gnu.org/software/gcc/faq.html">http://www.gnu.org/software/gcc/faq.html</a>.</p>
     12<a href="http://gcc.gnu.org/faq.html">http://gcc.gnu.org/faq.html</a>.</p>
    1313
    1414<p>This FAQ tries to answer specific questions concerning GCC. For
    1515general information regarding C, C++, resp. Fortran please check the
    1616<a href="http://www.eskimo.com/~scs/C-faq/top.html">comp.lang.c FAQ</a>,
    17 <a href="http://www.research.att.com/~austern/csc/faq.html">comp.std.c++
     17<a href="http://www.jamesd.demon.co.uk/csc/faq.html">comp.std.c++
    1818FAQ</a>,
    1919and the <a href="http://www.fortran.com/fortran/info.html">Fortran
     
    3131  <ol>
    3232     <li><a href="#gcc">What is the relationship between GCC and EGCS?</a></li>
    33      <li><a href="#cygnus">What is the relationship between GCC and Cygnus / Red Hat?</a></li>
    3433     <li><a href="#open-development">What is an open development model?</a></li>
    35      <li><a href="#bugreport">How do I report a bug?</a></li>
    3634     <li><a href="#support">How do I get a bug fixed or a feature added?</a></li>
    3735     <li><a href="#platforms">Does GCC work on my platform?</a></li>
     
    4644    <li><a href="#environ">cpp: Usage:... Error</a></li>
    4745    <li><a href="#optimizing">Optimizing the compiler itself</a></li>
     46    <li><a href="#iconv">Why does <code>libiconv</code> get linked into <code>jc1</code> on Solaris?</a></li>
    4847  </ol></li>
    4948
    5049  <li><a href="#testsuite">Testsuite problems</a>
    5150  <ol>
    52     <li><a href="#dejagnu">Unable to run the testsuite</a></li>
    5351    <li><a href="#testoptions">How do I pass flags like
    5452        <code>-fnew-abi</code> to the testsuite?</a></li>
     
    8280targets it could support, it worked well.  It had limitations inherent in
    8381its design that would be difficult to resolve, so a major effort was made
    84 to resolve those limitiations and gcc version 2 was the result.</p>
     82to resolve those limitations and gcc version 2 was the result.</p>
    8583
    8684<p>When we had gcc2 in a useful state, development efforts on gcc1 stopped
     
    9593<a href="steering.html">GCC Steering Committee</a>.</p>
    9694
    97 
    98 <hr />
    99 <h2><a name="cygnus">What is the relationship between GCC and Cygnus / Red Hat?</a></h2>
    100 
    101 <p>It is a common mis-conception that Red Hat controls GCC either
    102 directly or indirectly.</p>
    103 
    104 <p>While Red Hat does donate hardware, network connections, code and
    105 developer time to GCC development, Red Hat does not control GCC.</p>
    106 
    107 <p>Overall control of GCC is in the hands of the
    108 <a href="steering.html">GCC Steering Committee</a>
    109 which includes people from a variety of different organizations and
    110 backgrounds.  The purpose of the steering committee is to make
    111 decisions in the best interest of GCC and to help ensure that no
    112 individual or company has control over the project.</p>
    113 
    114 <p>To summarize, Red Hat contributes to the GCC project, but does not exert
    115 a controlling influence over GCC.</p>
    11695
    11796<hr />
     
    160139  terms:  A <b>cathedral</b> development model versus a <b>bazaar</b>
    161140  development model.  The paper is written by Eric S. Raymond, it is
    162   called ``<a
    163   href="http://www.tuxedo.org/~esr/writings/cathedral-bazaar/">The
    164   Cathedral and the Bazaar</a>''.  The paper is a useful starting point
    165   for discussions.
     141  called ``The Cathedral and the Bazaar''.
     142  The paper is a useful starting point for discussions.
    166143</blockquote>
    167144
    168 
    169 <hr />
    170 <h2><a name="bugreport">How do I report a bug?</a></h2>
    171 
    172 <p>There are complete instructions <a href="bugs.html">here</a>.</p>
    173 
    174 
    175 <hr />
    176 <h2><a name="support">How do I get a bug fixed or a feature added?</a></h2>
     145<hr />
     146<!-- The "bugreport" anchor was used in ICE messages of GCC < 2.95.3. -->
     147<h2 id="bugreport"><a name="support">How do I get a bug fixed or
     148    a feature added?</a></h2>
    177149
    178150<p>There are lots of ways to get something fixed.  The list below may be
    179151incomplete, but it covers many of the common cases.  These are listed
    180 roughly in order of increasing difficulty for the average GCC user,
     152roughly in order of decreasing difficulty for the average GCC user,
    181153meaning someone who is not skilled in the internals of GCC, and where
    182154difficulty is measured in terms of the time required to fix the bug.
     
    185157
    186158<ul>
    187 <li>Hire someone to fix it for you.  There are various companies and
    188     individuals providing support for GCC.  This alternative costs
    189     money, but is relatively likely to get results.</li>
    190 
    191 <li><a href="bugs.html">Report the problem to the GCC GNATS bug tracking system</a>
     159<li>Fix it yourself.  This alternative will probably bring results,
     160    if you work hard enough, but will probably take a lot of time,
     161    and, depending on the quality of your work and the perceived
     162    benefits of your changes, your code may or may not ever make it
     163    into an official release of GCC.</li>
     164
     165<li><a href="bugs.html">Report the problem to the GCC bug tracking system</a>
    192166    and hope that someone will be kind
    193167    enough to fix it for you.  While this is certainly possible, and
     
    196170    from a commercial support organization since the people who read
    197171    GCC bug reports, if they choose to help you, will be volunteering their
    198     time.  This alternative will work best if you follow the directions
    199     on <a href="bugs.html">submitting bugreports</a>.</li>
    200 
    201 <li>Fix it yourself.  This alternative will probably bring results,
    202     if you work hard enough, but will probably take a lot of time,
    203     and, depending on the quality of your work and the perceived
    204     benefits of your changes, your code may or may not ever make it
    205     into an official release of GCC.</li>
     172    time.</li>
     173
     174<li>Hire someone to fix it for you.  There are various companies and
     175    individuals providing support for GCC.  This alternative costs
     176    money, but is relatively likely to get results.</li>
    206177</ul>
    207178
     
    387358<pre>make BOOT_CFLAGS="-O2 -fssa" bootstrap</pre>
    388359
     360<hr />
     361<h2><a name="iconv">Why does <code>libiconv</code> get linked into <code>jc1</code> on Solaris?</a></h2>
     362
     363<p>The Java front end requires <code>iconv</code>.  If the compiler
     364used to bootstrap GCC finds <code>libiconv</code> (because the GNU
     365version of <code>libiconv</code> has been installed in the same prefix
     366as the bootstrap compiler), but the newly built GCC does not find the
     367library (because it will be installed with a different prefix), then a
     368link-time error will occur when building <code>jc1</code>.  This
     369problem does not show up so often on platforms that have
     370<code>libiconv</code> in a default location (like
     371<code>/usr/lib</code>) because then both compilers can find a library
     372named <code>libiconv</code>, even though it is a different
     373library.</p>
     374
     375<p>Using <code>--disable-nls</code> at configure-time does not
     376prevent this problem because <code>jc1</code> uses
     377<code>iconv</code> even in that case.  Solutions include temporarily
     378removing the GNU <code>libiconv</code>, copying it to a default
     379location such as <code>/usr/lib/</code>, and using
     380<code>--enable-languages</code> at configure-time to disable Java.</p>
    389381
    390382<hr />
     
    392384<h1>Testsuite problems</h1>
    393385
    394 <h2><a name="dejagnu">Unable to run the testsuite</a></h2>
    395 
    396 <p>If you get a message about unable to find "standard.exp" when trying to
    397 run the GCC testsuites, then your dejagnu is too old to run the GCC tests.
    398 You will need to get a newer version of dejagnu from
    399 <a href="http://www.gnu.org/software/dejagnu/dejagnu.html">
    400   http://www.gnu.org/software/dejagnu/dejagnu.html</a>.</p>
    401 
    402 <hr />
    403386<h2><a name="testoptions">How do I pass flags like
    404387  <code>-fnew-abi</code> to the testsuite?</a></h2>
Note: See TracChangeset for help on using the changeset viewer.