1 |
Hello, |
2 |
|
3 |
On Wed, 20 Dec 2017, Helmut Jarausch wrote: |
4 |
>On 12/19/2017 07:13:55 PM, Bas Zoutendijk wrote: |
5 |
>> On Tue 19 Dec 2017 at 16:45:15 +0100, Helmut Jarausch wrote: |
6 |
>> > In addition. I keep gcc-6.4.0 since it can generate PIE-enabled |
7 |
>> > executables AND it it the last compiler with 'gcj'. |
8 |
>> > |
9 |
>> > I don't understand why 'pdftk' and packages depending on that have been |
10 |
>> > masked. |
11 |
>> > |
12 |
>> > They build and run fine here (profile 17.0) |
13 |
>> |
14 |
>> If I read the =app-text/pdftk-2.02 ebuild correctly, it actually uses |
15 |
>> GCC 5.4.0, regardless of what your system compiler is (6.4.0 for |
16 |
>> profile 17.0): |
17 |
>> |
18 |
>> # We need gcc-5 because of Java |
19 |
>> export PATH="$(gcc-config -B 5.4.0):${PATH}" |
20 |
> |
21 |
>Yes, but you can change this to |
22 |
> |
23 |
>RDEPEND="sys-devel/gcc:6.4.0[gcj]" |
24 |
> |
25 |
>which works just fine. |
26 |
|
27 |
But should suffice to be |
28 |
|
29 |
DEPEND="sys-devel/gcc[gcj]" |
30 |
RDEPEND="${DEPEND}" |
31 |
|
32 |
i.e. DEPEND not RDEPEND. The 6.4.x part is implicit by 7.x lacking the |
33 |
gcj USE-flag. OTOH, in my ebuild I explicitly depend on 6.4.0 (but |
34 |
only because I gcc-config'ed to gcc-7.2), so... If you have 6.4.0 |
35 |
selected, that explicit dep could be killed. It's just a matter of |
36 |
'gcj' and 'gcjh' being in the path and found (and a matching gcc too). |
37 |
|
38 |
And BTW, you can't change to java/icedtea, I've looked at the code, |
39 |
it'd be a major rewrite, pdftk uses lots of gcj specific stuff. |
40 |
|
41 |
I'll attach my whole diff to the original 2.02.ebuild. |
42 |
|
43 |
HTH, |
44 |
-dnh |
45 |
|
46 |
-- |
47 |
"Here, in the bare dark face of night / A calm unhurried eye draws sight |
48 |
-- We see in what we think we fear / The cloudings of our thought made clear" |
49 |
"A most interesting contribution, we're sure, but can we keep this just a |
50 |
little more focused?" -- GSV "Wisdom Like Silence" to LSV "Serious Callers Only" |