Displaying 2 results from an estimated 2 matches for "xhnjjnsi3bgr667b4".
2014 May 23
1
Bug#749060: klibc: ppc64el needs static binaries as well
...eu2CV6H8tM+WnR9AO086Kk01h64NoggUwXYPXXfDZKUYxzROaKWGrX315
4p9Nkd3DCtiyITXmLEtcH4D7iQJvtAOyWwq2XxYVo74AdrOQLZv6KIzEISOFhQZr
unBIe8vUo4cGVb+MjtGRVLDl9b/F4gRn/lGSTYSsI9tb76VRdHIn4qeKIXGqLbbH
ovfrWqLISC5V7FfG0/933+Ye/x/DH3MNWD/ZGJxuPm/2DL8uUOEvOi7OHqESR83V
vecWcR8cpepeuwRVfrFlFbzoeHvUtW9IqCU9KGmy1jOyiT/XhnJjNSi3BgR667B4
T4Fm+lRDixzE8yCxans4
=tyKt
-----END PGP SIGNATURE-----
2014 May 23
2
Bug#749060: klibc: ppc64el needs static binaries as well
Hi,
On Fri, May 23, 2014 at 10:57:31AM -0300, Mauricio Faria de Oliveira wrote:
>
> The ppc64el port needs klibc's static binaries, like ppc64.
This segfaulting is a bug in klibc that needs investigation.
> This patch enables the ARCH=ppc64 make env var in debian/rules, in order
> for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too.
I have no problem