Re: PATCH to pre-select languages to be build

[Jeffrey A Law <law at cygnus dot com>]

  In message <13842.2446.855496.247677@slsvhmt>you write:
  > Well, I could  implement this in  addition, too. But there's a problem
  > with this approach: let's suppose  Craig wants to  build the C and the
  > F77 (only! no c++ ...) compilers, hence he wants to disable c++ (note,
  > this name is used for $(LANGUAGES)!);  thus he adds `--disable-c++' to
  > his configure command. I guess you know the result:
  > 
  > >From the toplevel configure file:
  > 
  >   sh: enable_c++=no: command not found
  > 
  > and inside the gcc subdirectory:
  > 
  >   configure: error: c++: invalid feature name
  > 
  > This is caused by `c++' not being a  valid shell variable name. OK, we
  > can hack our toplevel configure script replacing  '+' with 'x', but we
  > would have to do this  for autoconf, too, and  I believe this might be
  > hard to get a  fixed autoconf in  time... .  Another solution might be
  > to use different name, i.e.   `--disable-cxx', but  then we'd have  to
  > use "c++" for $(LANGUAGES)    and "cxx" for the   --enable-/--disable-
  > stuff :-(
Ugh.  I'd almost prefer to replace + with x as needed.  The code is really
simpler than your approach.

  > My  argument concerning new compilers in   a new tarball still stands,
  > too.  The  average test user gets  a new egcs-x.y.tar.gz  file, untars
  > it, and calls his usual build script/comand, e.g.
By default we should build all languages.  The user must explicitly specify
that they do not want particular languages.  I think we've agreed on that.

jeff