On Wed, Nov 7, 2012 at 4:32 PM, Herbert Graeber
Am 07.11.2012 13:21, schrieb Dinar Valeev:
Why each arch should have own tarball? isn't ghc-src not sufficient? It is not sufficient for boot-strapping. GHC has to be compiled by itself., so we have to solve the hen and egg problem by injecting a binary version of the compiler for the first compilation. Is there a way to produce such tarball manually?
The reason that it even not trying to compile on ppc Factory. error: File /home/abuild/rpmbuild/SOURCES/ghc-7.4.1-ppc64-unknown-linux.tar.bz2: No such file or directory This is the binary compiler you need for the first compilation. When the first build of ghc in Factory has succeeded, the binary will be removed again.
After everything works for x86 and x86_64 we may repeat the bootstrap for other architecture, too.
https://build.opensuse.org/package/live_build_log?arch=ppc64&package=ghc&project=openSUSE%3AFactory%3APowerPC&repository=standard If you download the file from the ghc website and add it to the package you are able to do the bootstrap yourself. After first compilation, you can remove the binary again and turn bootstrap mode off. After this ghc compilation is self contained. There is no ppc version available.
Also I took a look how Fedora doing this.. They just use ghc-src tarball.
[...] Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org