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

    • Property cvs2svn:cvs-rev changed from 1.1 to 1.1.1.2
    r1390 r1391  
    33
    44   The latest version of this document is always available at
    5    [1]http://www.gnu.org/software/gcc/faq.html.
     5   [1]http://gcc.gnu.org/faq.html.
    66
    77   This FAQ tries to answer specific questions concerning GCC. For
     
    1717    1. [7]General information
    1818         1. [8]What is the relationship between GCC and EGCS?
    19          2. [9]What is the relationship between GCC and Cygnus / Red Hat?
    20          3. [10]What is an open development model?
    21          4. [11]How do I report a bug?
    22          5. [12]How do I get a bug fixed or a feature added?
    23          6. [13]Does GCC work on my platform?
    24     2. [14]Installation
    25          1. [15]How to install multiple versions of GCC
    26          2. [16]Dynamic linker is unable to find GCC libraries
    27          3. [17]libstdc++/libio tests fail badly with --enable-shared
    28          4. [18]GCC can not find GNU as/GNU ld
    29          5. [19]cpp: Usage:... Error
    30          6. [20]Optimizing the compiler itself
    31     3. [21]Testsuite problems
    32          1. [22]Unable to run the testsuite
    33          2. [23]How do I pass flags like -fnew-abi to the testsuite?
    34          3. [24]How can I run the test suite with multiple options?
    35     4. [25]Older versions of GCC
    36          1. [26]Is there a stringstream / sstream for GCC 2.95.2?
    37     5. [27]Miscellaneous
    38          1. [28]Friend Templates
    39          2. [29]dynamic_cast, throw, typeid don't work with shared
     19         2. [9]What is an open development model?
     20         3. [10]How do I get a bug fixed or a feature added?
     21         4. [11]Does GCC work on my platform?
     22    2. [12]Installation
     23         1. [13]How to install multiple versions of GCC
     24         2. [14]Dynamic linker is unable to find GCC libraries
     25         3. [15]libstdc++/libio tests fail badly with --enable-shared
     26         4. [16]GCC can not find GNU as/GNU ld
     27         5. [17]cpp: Usage:... Error
     28         6. [18]Optimizing the compiler itself
     29         7. [19]Why does libiconv get linked into jc1 on Solaris?
     30    3. [20]Testsuite problems
     31         1. [21]How do I pass flags like -fnew-abi to the testsuite?
     32         2. [22]How can I run the test suite with multiple options?
     33    4. [23]Older versions of GCC
     34         1. [24]Is there a stringstream / sstream for GCC 2.95.2?
     35    5. [25]Miscellaneous
     36         1. [26]Friend Templates
     37         2. [27]dynamic_cast, throw, typeid don't work with shared
    4038            libraries
    41          3. [30]Why do I need autoconf, bison, xgettext, automake, etc?
    42          4. [31]Why can't I build a shared library?
    43          5. [32]When building C++, the linker says my constructors,
     39         3. [28]Why do I need autoconf, bison, xgettext, automake, etc?
     40         4. [29]Why can't I build a shared library?
     41         5. [30]When building C++, the linker says my constructors,
    4442            destructors or virtual tables are undefined, but I defined
    4543            them
    46          6. [33]Will GCC someday include an incremental linker?
     44         6. [31]Will GCC someday include an incremental linker?
    4745     _________________________________________________________________
    4846
     
    5452   targets it could support, it worked well. It had limitations inherent
    5553   in its design that would be difficult to resolve, so a major effort
    56    was made to resolve those limitiations and gcc version 2 was the
     54   was made to resolve those limitations and gcc version 2 was the
    5755   result.
    5856
     
    6664   official GCC maintainers. The net result was a single project which
    6765   carries forward GCC development under the ultimate control of the
    68    [34]GCC Steering Committee.
    69      _________________________________________________________________
    70 
    71 What is the relationship between GCC and Cygnus / Red Hat?
    72 
    73    It is a common mis-conception that Red Hat controls GCC either
    74    directly or indirectly.
    75 
    76    While Red Hat does donate hardware, network connections, code and
    77    developer time to GCC development, Red Hat does not control GCC.
    78 
    79    Overall control of GCC is in the hands of the [35]GCC Steering
    80    Committee which includes people from a variety of different
    81    organizations and backgrounds. The purpose of the steering committee
    82    is to make decisions in the best interest of GCC and to help ensure
    83    that no individual or company has control over the project.
    84 
    85    To summarize, Red Hat contributes to the GCC project, but does not
    86    exert a controlling influence over GCC.
     66   [32]GCC Steering Committee.
    8767     _________________________________________________________________
    8868
    8969What is an open development model?
    9070
    91    We are using a bazaar style [36][1] approach to GCC development: we
     71   We are using a bazaar style [33][1] approach to GCC development: we
    9272   make snapshots publicly available to anyone who wants to try them; we
    9373   welcome anyone to join the development mailing list. All of the
     
    127107     two terms: A cathedral development model versus a bazaar
    128108     development model. The paper is written by Eric S. Raymond, it is
    129      called ``[37]The Cathedral and the Bazaar''. The paper is a useful
     109     called ``The Cathedral and the Bazaar''. The paper is a useful
    130110     starting point for discussions.
    131      _________________________________________________________________
    132 
    133 How do I report a bug?
    134 
    135    There are complete instructions [38]here.
    136111     _________________________________________________________________
    137112
     
    140115   There are lots of ways to get something fixed. The list below may be
    141116   incomplete, but it covers many of the common cases. These are listed
    142    roughly in order of increasing difficulty for the average GCC user,
     117   roughly in order of decreasing difficulty for the average GCC user,
    143118   meaning someone who is not skilled in the internals of GCC, and where
    144119   difficulty is measured in terms of the time required to fix the bug.
    145120   No alternative is better than any other; each has its benefits and
    146121   disadvantages.
    147      * Hire someone to fix it for you. There are various companies and
    148        individuals providing support for GCC. This alternative costs
    149        money, but is relatively likely to get results.
    150      * [39]Report the problem to the GCC GNATS bug tracking system and
    151        hope that someone will be kind enough to fix it for you. While
    152        this is certainly possible, and often happens, there is no
    153        guarantee that it will. You should not expect the same response
    154        from this method that you would see from a commercial support
    155        organization since the people who read GCC bug reports, if they
    156        choose to help you, will be volunteering their time. This
    157        alternative will work best if you follow the directions on
    158        [40]submitting bugreports.
    159122     * Fix it yourself. This alternative will probably bring results, if
    160123       you work hard enough, but will probably take a lot of time, and,
     
    162125       of your changes, your code may or may not ever make it into an
    163126       official release of GCC.
     127     * [34]Report the problem to the GCC bug tracking system and hope
     128       that someone will be kind enough to fix it for you. While this is
     129       certainly possible, and often happens, there is no guarantee that
     130       it will. You should not expect the same response from this method
     131       that you would see from a commercial support organization since
     132       the people who read GCC bug reports, if they choose to help you,
     133       will be volunteering their time.
     134     * Hire someone to fix it for you. There are various companies and
     135       individuals providing support for GCC. This alternative costs
     136       money, but is relatively likely to get results.
    164137     _________________________________________________________________
    165138
     
    169142   information about known problems with installing or using GCC on
    170143   particular platforms. These are included in the sources for a release
    171    in INSTALL/specific.html, and the [41]latest version is always
    172    available at the GCC web site. Reports of [42]successful builds for
     144   in INSTALL/specific.html, and the [35]latest version is always
     145   available at the GCC web site. Reports of [36]successful builds for
    173146   several versions of GCC are also available at the web site.
    174147     _________________________________________________________________
     
    217190
    218191   If you use --prefix, GCC may have difficulty locating a GNU assembler
    219    or linker on your system, [43]GCC can not find GNU as/GNU ld explains
     192   or linker on your system, [37]GCC can not find GNU as/GNU ld explains
    220193   how to deal with this.
    221194
     
    283256
    284257   To ensure that GCC finds the GNU assembler (the GNU loader), which are
    285    required by [44]some configurations, you should configure these with
     258   required by [38]some configurations, you should configure these with
    286259   the same --prefix option as you used for GCC. Then build & install GNU
    287260   as (GNU ld) and proceed with building GCC.
     
    330303     _________________________________________________________________
    331304
     305Why does libiconv get linked into jc1 on Solaris?
     306
     307   The Java front end requires iconv. If the compiler used to bootstrap
     308   GCC finds libiconv (because the GNU version of libiconv has been
     309   installed in the same prefix as the bootstrap compiler), but the newly
     310   built GCC does not find the library (because it will be installed with
     311   a different prefix), then a link-time error will occur when building
     312   jc1. This problem does not show up so often on platforms that have
     313   libiconv in a default location (like /usr/lib) because then both
     314   compilers can find a library named libiconv, even though it is a
     315   different library.
     316
     317   Using --disable-nls at configure-time does not prevent this problem
     318   because jc1 uses iconv even in that case. Solutions include
     319   temporarily removing the GNU libiconv, copying it to a default
     320   location such as /usr/lib/, and using --enable-languages at
     321   configure-time to disable Java.
     322     _________________________________________________________________
     323
    332324                              Testsuite problems
    333 
    334 Unable to run the testsuite
    335 
    336    If you get a message about unable to find "standard.exp" when trying
    337    to run the GCC testsuites, then your dejagnu is too old to run the GCC
    338    tests. You will need to get a newer version of dejagnu from
    339    [45]http://www.gnu.org/software/dejagnu/dejagnu.html.
    340      _________________________________________________________________
    341325
    342326How do I pass flags like -fnew-abi to the testsuite?
     
    372356
    373357   Yes, it's at:
    374    [46]http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream.
     358   [39]http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream.
    375359     _________________________________________________________________
    376360
     
    471455
    472456   For more details about the way that GCC implements these and other C++
    473    features, please read the [47]ABI specification. Note the
     457   features, please read the [40]ABI specification. Note the
    474458   std::typeinfo_t objects which must be resolved all begin with "_ZTS".
    475459   Refer to ld's documentation for a description of the "-E" &
     
    502486
    503487   In general, the current versions of these tools from
    504    [48]ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not
     488   [41]ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not
    505489   supported, and you will need to use Autoconf 2.13; work is in progress
    506490   to fix this problem. Also look at
    507    [49]ftp://gcc.gnu.org/pub/gcc/infrastructure/ for any special versions
     491   [42]ftp://gcc.gnu.org/pub/gcc/infrastructure/ for any special versions
    508492   of packages.
    509493     _________________________________________________________________
     
    561545References
    562546
    563    1. http://www.gnu.org/software/gcc/faq.html
     547   1. http://gcc.gnu.org/faq.html
    564548   2. http://www.eskimo.com/~scs/C-faq/top.html
    565    3. http://www.research.att.com/~austern/csc/faq.html
     549   3. http://www.jamesd.demon.co.uk/csc/faq.html
    566550   4. http://www.fortran.com/fortran/info.html
    567551   5. http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html
     
    569553   7. http://gcc.gnu.org/faq.html#general
    570554   8. http://gcc.gnu.org/faq.html#gcc
    571    9. http://gcc.gnu.org/faq.html#cygnus
    572   10. http://gcc.gnu.org/faq.html#open-development
    573   11. http://gcc.gnu.org/faq.html#bugreport
    574   12. http://gcc.gnu.org/faq.html#support
    575   13. http://gcc.gnu.org/faq.html#platforms
    576   14. http://gcc.gnu.org/faq.html#installation
    577   15. http://gcc.gnu.org/faq.html#multiple
    578   16. http://gcc.gnu.org/faq.html#rpath
    579   17. http://gcc.gnu.org/faq.html#rpath
    580   18. http://gcc.gnu.org/faq.html#gas
    581   19. http://gcc.gnu.org/faq.html#environ
    582   20. http://gcc.gnu.org/faq.html#optimizing
    583   21. http://gcc.gnu.org/faq.html#testsuite
    584   22. http://gcc.gnu.org/faq.html#dejagnu
    585   23. http://gcc.gnu.org/faq.html#testoptions
    586   24. http://gcc.gnu.org/faq.html#multipletests
    587   25. http://gcc.gnu.org/faq.html#old
    588   26. http://gcc.gnu.org/faq.html#2.95sstream
    589   27. http://gcc.gnu.org/faq.html#misc
    590   28. http://gcc.gnu.org/faq.html#friend
    591   29. http://gcc.gnu.org/faq.html#dso
    592   30. http://gcc.gnu.org/faq.html#generated_files
    593   31. http://gcc.gnu.org/faq.html#picflag-needed
    594   32. http://gcc.gnu.org/faq.html#vtables
    595   33. http://gcc.gnu.org/faq.html#incremental
    596   34. http://gcc.gnu.org/steering.html
    597   35. http://gcc.gnu.org/steering.html
    598   36. http://gcc.gnu.org/faq.html#cathedral-vs-bazaar
    599   37. http://www.tuxedo.org/~esr/writings/cathedral-bazaar/
    600   38. http://gcc.gnu.org/bugs.html
    601   39. http://gcc.gnu.org/bugs.html
    602   40. http://gcc.gnu.org/bugs.html
    603   41. http://gcc.gnu.org/install/specific.html
    604   42. http://gcc.gnu.org/buildstat.html
    605   43. http://gcc.gnu.org/faq.html#gas
    606   44. http://gcc.gnu.org/install/specific.html
    607   45. http://www.gnu.org/software/dejagnu/dejagnu.html
    608   46. http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream
    609   47. http://www.codesourcery.com/cxx-abi/
    610   48. ftp://ftp.gnu.org/gnu/
    611   49. ftp://gcc.gnu.org/pub/gcc/infrastructure/
     555   9. http://gcc.gnu.org/faq.html#open-development
     556  10. http://gcc.gnu.org/faq.html#support
     557  11. http://gcc.gnu.org/faq.html#platforms
     558  12. http://gcc.gnu.org/faq.html#installation
     559  13. http://gcc.gnu.org/faq.html#multiple
     560  14. http://gcc.gnu.org/faq.html#rpath
     561  15. http://gcc.gnu.org/faq.html#rpath
     562  16. http://gcc.gnu.org/faq.html#gas
     563  17. http://gcc.gnu.org/faq.html#environ
     564  18. http://gcc.gnu.org/faq.html#optimizing
     565  19. http://gcc.gnu.org/faq.html#iconv
     566  20. http://gcc.gnu.org/faq.html#testsuite
     567  21. http://gcc.gnu.org/faq.html#testoptions
     568  22. http://gcc.gnu.org/faq.html#multipletests
     569  23. http://gcc.gnu.org/faq.html#old
     570  24. http://gcc.gnu.org/faq.html#2.95sstream
     571  25. http://gcc.gnu.org/faq.html#misc
     572  26. http://gcc.gnu.org/faq.html#friend
     573  27. http://gcc.gnu.org/faq.html#dso
     574  28. http://gcc.gnu.org/faq.html#generated_files
     575  29. http://gcc.gnu.org/faq.html#picflag-needed
     576  30. http://gcc.gnu.org/faq.html#vtables
     577  31. http://gcc.gnu.org/faq.html#incremental
     578  32. http://gcc.gnu.org/steering.html
     579  33. http://gcc.gnu.org/faq.html#cathedral-vs-bazaar
     580  34. http://gcc.gnu.org/bugs.html
     581  35. http://gcc.gnu.org/install/specific.html
     582  36. http://gcc.gnu.org/buildstat.html
     583  37. http://gcc.gnu.org/faq.html#gas
     584  38. http://gcc.gnu.org/install/specific.html
     585  39. http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream
     586  40. http://www.codesourcery.com/cxx-abi/
     587  41. ftp://ftp.gnu.org/gnu/
     588  42. ftp://gcc.gnu.org/pub/gcc/infrastructure/
Note: See TracChangeset for help on using the changeset viewer.