[Bug bootstrap/26259] toplevel directories should be assocaited at the toplevel with a language being built instead of with a subdirectory of gcc

2006-02-16 Thread pinskia at gcc dot gnu dot org


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

   Severity|normal  |enhancement
Summary|--enable-languages=c,c++ not|toplevel directories should
   |working as expected,|be assocaited at the
   |documented when removing|toplevel with a language
   |gcc/ada and libada but not  |being built instead of with
   |gnattools   |a subdirectory of gcc


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26259



[Bug bootstrap/26259] toplevel directories should be assocaited at the toplevel with a language being built instead of with a subdirectory of gcc

2006-02-16 Thread pinskia at gcc dot gnu dot org


--- Comment #34 from pinskia at gcc dot gnu dot org  2006-02-16 16:11 
---
This bug was orginally opened and not really explaining what happened until
comment #2 and even then it was really You tell the doctor, it hurts when I do
this and the doctor explains, do not that then.  The reason for that reason
was simple, this is how it works.  Now if the person was not removing gcc/ada,
it would be a different issue but since it is removal of this directory which
caused it, it is not a matter of what is the correct behavior for documented
behavior (as it is documented that config-lang.in controls the association).

This is a dup of bug 26323 which explains what really wants to be changed
instead of going in circuls of the current correct behavior.

*** This bug has been marked as a duplicate of 26323 ***


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26259



[Bug bootstrap/26259] toplevel directories should be assocaited at the toplevel with a language being built instead of with a subdirectory of gcc

2006-02-16 Thread pinskia at gcc dot gnu dot org


--- Comment #35 from pinskia at gcc dot gnu dot org  2006-02-16 16:11 
---
(In reply to comment #34)
 This is a dup of bug 26323 which explains what really wants to be changed
 instead of going in circles of the current correct [documented] behavior.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26259