-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/28/2013 08:44 AM, Stephen Gallagher wrote:
On 06/28/2013 01:50 AM, Peter Lemenkov wrote:
> Hello. I've got bugreport that Erlang doesn't work on EL6 PPC64
> achitecture.
>
https://bugzilla.redhat.com/show_bug.cgi?id=958953
> I don't have resources to fix this issue, and nobody volunteered
> to fix it so far, so I'd like to limit Erlang, and Erlang
> applications and libraries on EL6 to x86/x86_64, where they
> works for sure. It's not the only issue with Erlang and PPC64 -
> it also has limited support for Java which prevented Erlang-Java
> bridge from being built successfully. Reducing Erlang on EL6 to
> architectures where it works even allows me to drop one patch
> and remove a couple of ifdefs from spec so this will simplify
> things a bit.
> Is there any documentation which describes the process of package
> removal from a particular EL hardware branch? -- With best
> regards, Peter Lemenkov.
Your best bet would be to add ppc64 to the ExclusiveArch on
erlang, rebuild it, get it pushed to stable, then the broken deps
would make it clear what packages were descended from it (and can
also be patched then to exclude ppc64).
Of course, I meant that you should be using
ExclusiveArch: %{ix86} x86_64
Adding ppc64 to that list would be the opposite of what you want...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlHNiSMACgkQeiVVYja6o6MCzACfUCq6Jt7NSVPJsVS+VBcp1LtL
QVEAnRLRd44q5dOC5Sj2hpfAr7TxzncU
=vbHa
-----END PGP SIGNATURE-----