This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Bug in the gcc installation instructions


I'm trying to compile gcc-2.95.2, reading the installation instructions at 
http://gcc.gnu.org/install/configure.html, which seems to be the same
information as in the gcc-2.95.2/install/CONFIGURE file.

It describes one cpplib related option, as follows:

     * --enable-cpplib -- Specify that the functionality of CPP should be
       integrated into the compiler itself. This is still under
       development, but may be useful in limited situations. This option
       is never enabled by default.

>From reading the gcc-2.95.2/gcc/configure.in, this seems wrong. The
text is an accurate description of a different option,
--enable-c-cpplib. The --enable-cpplib option simply switches from the
old preprocessor cppp.c to the newer one based on cpplib. The
instructions should mention both.

To me, --enable-cpplib is actually qite useful. Without it, the
preprocesser can't deal with macro continuation lines that end with
\ CR LF.

At one point I was also confused about whether "We use _srcdir_ to
refer to the toplevel source directory for GCC" referred to
gcc-2.95.2/ or gcc-2.952.2/gcc, but perhaps that's just me. For now,
I'm assuming it refers to the former.

/Niels



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]