1 |
(Moving to gentoo-dev) |
2 |
|
3 |
On Sun, 2 Dec 2018, Michał Górny wrote: |
4 |
> I think that if there's one package that doesn't work with profiles |
5 |
> (compared to the very large number of packages which just work fine), |
6 |
> it's not the profiles but the package being broken (read: doing silly |
7 |
> assumptions). Therefore, it's not 17.0 profiles being the problem but |
8 |
> the package in question. |
9 |
> |
10 |
> Claiming that people doing any change to Gentoo are required to fix all |
11 |
> the problematic packages is just silly. This is basically saying that |
12 |
> it's fine to add bad quality packages and then demand others to fix them |
13 |
> for you. People who worked on the profile can fix bugs in the profile. |
14 |
> Don't expect them to pursue whatever broken packages you like just |
15 |
> because they happened to change the fragile conditions under which they |
16 |
> worked. |
17 |
See bug #672454. |
18 |
|
19 |
clozurecl compiles and works fine with the upstream-provided compilation |
20 |
flags. So, we cannot ask the upstream to solve our problems for us. |
21 |
|
22 |
clozurecl compiles and works fine (for me this means that it can compile |
23 |
maxima and fricas, and they work) in the 13.0 profile. In the 17.0 one, |
24 |
its compilation loops forever on ~x86; on ~amd64 it compiles, but does not |
25 |
work properly (cannot compile maxima, bug #665364). So, the reason is in |
26 |
the new compilation or linking flags introduced in 17.0. |
27 |
|
28 |
Is it possible to compile one specific package with compilation/linking |
29 |
flags closely following the 13.0 ones? How? |
30 |
|
31 |
> That said, if you insist I'll fix this package. But I'm pretty sure you |
32 |
> won't like my fix. |
33 |
If after this fix it will be able to compile maxima and fricas, and they |
34 |
will work, that would be sufficient for me. |
35 |
|
36 |
Andrey |