1 |
"Achim Gottinger" <achim@g.o> writes: |
2 |
|
3 |
> > |
4 |
> > hi achim, |
5 |
> > |
6 |
> > <snip> |
7 |
> > > I agree and already too a short look. looks like all these packages need |
8 |
> > > gcc-core and the additional sub-package. |
9 |
> > > how do you think about an eclass for these builds? |
10 |
> > </snip> |
11 |
> > |
12 |
> Hi Johannes, |
13 |
> |
14 |
> the problem ist that gcc (the binary) must be build with java,fortran,ada |
15 |
> support, |
16 |
> otherwise gcj... do not work, so it's not possible to use the separated |
17 |
|
18 |
IIRC, only C and C++ support need to be built for GCJ (at least this |
19 |
is the case for the GCC-3.3 branch from CVS). |
20 |
|
21 |
|
22 |
When I first saw this "too many languages" complaint in bugzilla, I |
23 |
had a WTF kind of reaction. If f77, objc were made USE flags, what |
24 |
happens when the user tries to emerge something months from now which |
25 |
depends on f77 -- it would fail at ./configure most likely. |
26 |
|
27 |
Now I see this thread has solved that problem by proposing |
28 |
gcc-{objc,java,f77} which is kinda messy like the VIM thing and mostly |
29 |
un-Gentoo-like IMO, but anyway. What happens when the user has |
30 |
gentoo-core, and emerge, say, octave which requires gcc-f77 to be |
31 |
emerged. Can f77 truly be built outside GCC's own build system? If its |
32 |
possible, what about java,objc,ada? |
33 |
|
34 |
If not, then gcc-{c++,java,objc,ada} are merely aliases for emerging |
35 |
gcc all-over, correct? |
36 |
|
37 |
Personally, I feel the GCC we build should be as complete and |
38 |
featureful as possible. After all, your compiler is the most important |
39 |
part of a source-based distro. |
40 |
|
41 |
My second preference is actually the USE flag approach. Only our more |
42 |
knowledgeable users are going to tweak compiler USE flags and when |
43 |
their ebuilds break with "Checking for a working |
44 |
f77... (no)\n***Error: no fortran compiler found.***" they will know |
45 |
exactly what to do (adjust their USE flags and re-emerge gcc). |
46 |
|
47 |
Yes it seems a bit manual. Some support in portage might be need to |
48 |
make it automatic (but I won't guess how hard that would be for |
49 |
carpaski). |
50 |
|
51 |
BTW, if we want to future proof ourselves a bit, some of the other |
52 |
front ends currently in development are: GPC (pascal), Cobol, G95 |
53 |
(fortran 95), modula 2 and ghdl (like vhdl). |
54 |
|
55 |
Matt |
56 |
|
57 |
-- |
58 |
Matthew Kennedy |
59 |
Gentoo Linux Developer |
60 |
|
61 |
|
62 |
-- |
63 |
gentoo-dev@g.o mailing list |