this is only cosmetic but I find it easier to have several optional packages
than a big one

for exemple libjava is optional, we should be able to compile it without
recompile everything and more without having to redownload everything too

same apply to libiberty : this lib can be found in binutils, and is installed by
this package, but gcc component fail to build (if we do the ./configure into gcc
dir) if ../libiberty/liberty.a isn't present

we can do the same remarks for the c++ lib and most of subtree subpackages

doing this will ease to understand why crosscompile fail (at this time I found
that libjava don't take the right headers, but that in order to have him take
the right header I have to compile it differently than the rest of the 
package...)

I think that big package was the attribute of old fashioned projects and then
that all lib provided into gcc should now be provided as separate packages....
because this is cleaner and that we'll have a better view of what's going on

best regards and thank you for providing such quality tool

-- 
           Summary: splitt the package into parts will ease compile step
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jlm_devel at laposte dot net
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu


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

Reply via email to