This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
LANGUAGES vs --enable-languages (was: Testsuite documentation)
- To: Tim Prince <tprince at computer dot org>
- Subject: LANGUAGES vs --enable-languages (was: Testsuite documentation)
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Tue, 28 Nov 2000 10:04:47 +0100 (CET)
- cc: <gcc at gcc dot gnu dot org>
On Mon, 27 Nov 2000, Tim Prince wrote:
> I've been confused myself on the --enable-languages and where it is meant to
> work. Even if that is used, the LANGUAGES option is useful to avoid
> building those components which cause bootstrap to fail;
This is exactly what --enable-languages is for, according.
<http://gcc.gnu.org/install/>.
In fact, according to that documentation, LANGUAGES is completely
unnecessary for regular users. (I think I understand what you are doing,
but I am not sure whether we want to expose such detail to the regular
users and whether this is "officially" supported at all.)
If this is not correct and LANGUAGES should be officially supported,
could someone please submit a documentation update for
<http://gcc.gnu.org/install/>?
> The environment variables which we have been required to set for testsuite
> on cygwin, when the gcc builds were working on that target, are:
>
> TCL_LIBRARY=/usr/share/tcl8.0
> DEJAGNULIBS=/usr/share/dejagnu
>
> I don't know whether there are other targets for which the necessary
> environment settings don't just happen.
Would you mind submitting a patch for install/test.html?
Thanks!
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/