1 |
Friday 29 November 2002 19:43 skrev Karl Trygve Kalleberg: |
2 |
> On Fri, 29 Nov 2002 18:41:12 +0100 |
3 |
> |
4 |
> Per Wigren <wigren@××××.se> wrote: |
5 |
> > Is it OK to add dev-lang/tcc as a build-dependancy? |
6 |
> |
7 |
> This makes for a _VERY_ interesting case. I think we should toy with this |
8 |
> concept a bit, as we can save ~3hrs compilation time (provided your |
9 |
> results are good, which I have all reason to think) and it's on a |
10 |
> non-critical package. |
11 |
> |
12 |
> I suggest: |
13 |
> 1) Only use tcc on platforms you have tested it on, so check ARCH and have |
14 |
> a x86? dev-lang/tcc-<version> in your DEPEND. |
15 |
|
16 |
I only tested with a manual build of tcc-0.9.14.. The latest in portage is |
17 |
0.9.7 which is very outdated and 0.9.14 needs adding a #define in a file to |
18 |
make it compile on gcc 3.x so I think we should wait for 0.9.15 because that |
19 |
is already fixed in cvs so there will be no need for sed-hacking then... |
20 |
|
21 |
> 2) Only leave tcc in the DEPEND= and specifically exclude it in RDEPEND |
22 |
> (the assumption I make is that a tcc-compiled binary doesn't depend on a |
23 |
> tcc runtime); all too often, build-time tools end up in RDEPEND, which is |
24 |
> completely and utterly wrong. |
25 |
|
26 |
I know, I always do that. I'm also annoyed with people not separating |
27 |
DEPEND/RDEPEND... |
28 |
|
29 |
> 3) Depending on how many packages can benefit from tcc, we may want to |
30 |
> introduce a useflag for it. May, as it increases the total maintenance |
31 |
> cost of the tree. |
32 |
|
33 |
We should only try do it for packages that takes more than 10-15 minutes to |
34 |
compile on a fairly fast machine... |
35 |
|
36 |
> Have you done any tests to see how many of the "regular" packages compile |
37 |
> nicely with tcc ? Can we compile XFree with it ? (Obviously mozilla is not |
38 |
> a candidate, as it's largely written in C++). |
39 |
|
40 |
I don't know about XFree, but I don't think there should be a problem.. TCC |
41 |
supports 100% of ANSI-C, 90% of C99-specific things and the most common |
42 |
GCC-extensions.. I read somewhere that they pass all test but 10 or so in |
43 |
GCC's testsuite (which has THOUSANDS of tests!).. |
44 |
|
45 |
> |
46 |
> |
47 |
> Kind regards, |
48 |
> |
49 |
> Karl T |
50 |
> |
51 |
> -- |
52 |
> gentoo-dev@g.o mailing list |
53 |
|
54 |
|
55 |
-- |
56 |
gentoo-dev@g.o mailing list |