1 |
Thanks for the feedback, I will look into what you said.
|
2 |
|
3 |
> On 20/01/2017, at 18:52, Benda Xu <heroxbd@g.o> wrote: |
4 |
> |
5 |
> Hi François, |
6 |
> |
7 |
> François Bissey <francois.bissey@×××××××××××××.nz> writes: |
8 |
> |
9 |
>> I have been experimenting putting RAP on |
10 |
>> a fresh SLES11SP1 install on ppc64... |
11 |
> |
12 |
> Is it SUSE 11.1? Is the closest community distribution OpenSUSE-11.1? |
13 |
> |
14 |
> We have only tested on OpenSUSE-42.1[1]. It is nice to have another test |
15 |
> environment. |
16 |
> |
17 |
> https://en.wikipedia.org/wiki/SUSE_Linux_distributions |
18 |
> |
19 |
|
20 |
Yes it is the same thing as SuSE 11.1 (SLES = SuSE Linux Enterprise Server)
|
21 |
|
22 |
When I discovered I didn’t have a profile I did go back
|
23 |
to [1] and discovered the intel-ness of the testing. For those
|
24 |
interested the base is
|
25 |
kernel 2.6.32
|
26 |
gcc-4.3.4
|
27 |
glibc-2.11.1
|
28 |
|
29 |
>> Yes it is not supported by default I realised |
30 |
>> pretty fast. After generating a profile that |
31 |
>> looked OK I moved on the various stages. |
32 |
> |
33 |
> No problem, that means we have new things to play with :) |
34 |
> |
35 |
> The profile is relatived to the gcc failure below. Could you please |
36 |
> show in detail the profile you created? |
37 |
> |
38 |
|
39 |
I copied
|
40 |
usr/portage/profiles/prefix/linux/ppc64
|
41 |
to
|
42 |
usr/portage/profiles/prefix/linux-standalone/ppc64
|
43 |
and then replaced
|
44 |
usr/portage/profiles/prefix/linux-standalone/ppc64/make.default
|
45 |
by the amd64 one and copied the legacy folder from the amd64 one
|
46 |
also.
|
47 |
|
48 |
>> My first real issue was building sed in stage 1. |
49 |
>> I had to compile xz and link to /usr/bin for |
50 |
>> the latest sed to unpack without error. |
51 |
>> There should probably be some dependency there |
52 |
>> since `xz` was merged a few minutes later. |
53 |
>> |
54 |
>> Similarly bison initially failed because I didn't |
55 |
>> have help2man installed on the host system. |
56 |
>> |
57 |
>> I had to keyword baselayout-prefix ~ppc64. |
58 |
>> |
59 |
>> But all those are quite minor overall, |
60 |
> |
61 |
> Yeah. Let's upstream them for a better ppc64 support in the future. |
62 |
> |
63 |
>> so I am now in stage 3 and gcc-5.4.0-r2 fails to build. It fails |
64 |
>> during its own "stage 2" with: build/genmatch --gimple |
65 |
>> /shared/work_no_backup/ppc64-prefix/tmp/var/tmp/portage/sys-devel/gcc-5.4.0-r2/work/gcc-5.4.0/gcc/match.pd |
66 |
>> \ |
67 |
>>> tmp-gimple-match.c |
68 |
>> build/genmatch: /lib64/ld64.so.1: version `GLIBC_2.22' not found |
69 |
>> (required by build/genmatch) |
70 |
> |
71 |
> The compiled elf does not have interpreter field prefixed. It should be |
72 |
> |
73 |
> $EPREFIX/lib64/ld64.so.1 (gentoo glibc) instead of /lib64/ld64.so.1 (host glibc) |
74 |
> |
75 |
>> make[3]: *** [s-match] Error 1 |
76 |
> |
77 |
>> so it didn't look for my RAP glibc are there |
78 |
>> any RAP specific patches that are applied to |
79 |
>> gcc? |
80 |
> |
81 |
> The hack are in |
82 |
> |
83 |
> https://gitweb.gentoo.org/repo/gentoo.git/tree/profiles/prefix/linux-standalone/profile.bashrc |
84 |
> |
85 |
> esp. line 14. |
86 |
> |
87 |
|
88 |
Looking into it ASAP,
|
89 |
François |