1 |
Marc Giger wrote: [Fri Feb 06 2004, 02:14:11PM EST] |
2 |
> Yeah, it looks like:-) but I was wrong... I removed this check and ran |
3 |
> into troubles. The Macro __GLIBC_HAVE_LONG_LONG must not be defined |
4 |
> with ccc. |
5 |
|
6 |
But why not? I thought your earlier logic made sense. |
7 |
|
8 |
> So this check is totally ok! It has nothing to do with |
9 |
> "long long". Sorry... I was searching for the reason why I couldn't |
10 |
> compile python with ccc. |
11 |
> After some time I found it! The attached patch solves the problem. Now |
12 |
> I'm running python 2.3 compiled with ccc:-) |
13 |
|
14 |
I understand what the patch is doing, but I don't understand why |
15 |
defining __GLIBC_HAVE_LONG_LONG wouldn't be a better solution? |
16 |
|
17 |
> This seems not to be the right place neither. I think this is useless |
18 |
> anyway. The right place to fix it is in "create-comp-config.sh". I tried |
19 |
> to change it but it seems that a shell-script and regex guru is |
20 |
> needed;-) The same should be changed by cxx (preventing). |
21 |
|
22 |
Okay, I think I fixed it. Try out ccc-6.5.9.001-r1.ebuild when it |
23 |
arrives at your nearest mirror... Let me know what you think. |
24 |
|
25 |
> With these two fixes, I'm able to compile a lot more packages with the |
26 |
> compaq compiler. |
27 |
|
28 |
I'd like to be more certain about the sysmacros.h fix before putting it |
29 |
in since it modifies glibc. It seems like if that fix is needed then |
30 |
other header files would need a similar fix! |
31 |
|
32 |
Regards, |
33 |
Aron |
34 |
|
35 |
-- |
36 |
Aron Griffis |
37 |
Gentoo Linux Developer (alpha / ia64 / ruby / vim) |
38 |
Key fingerprint = E3B6 8734 C2D6 B5E5 AE76 FB3A 26B1 C5E3 2010 4EB0 |