-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dennis Gilmore wrote:
> Hey all,
>
> I have a odd situtation that im trying to work out the best way to handle.
> gcc on sparc needs glibc for sparc and sparc64 but it gets built as sparc.
> somehow i need to have sparc64 glibc in the buildroot only for gcc. even
> though the target is sparc.
>
> Dennis
>
I've started three replies to this and have bogged down every time. Sigh.
If I'm correct here, the problem is that you need both 32-bit and 64-bit
glibc's in the same chroot to build gcc for a sparc. I looked on a
x86_64 FC5 system and it has two glibc-2.4-8 packages, but if you list
them both, one is the 64 bit version and the other is the 32-bit
version. This implies to me that they were both "installed" as opposed
to "updated". I can't really see an easy way to force mock/yum to do
this, so I think the only way will be multiple invocations of mock and
rpm. Something like:
$ mock -r fedora-devel-sparc-core init
$ rpm --root /var/lib/mock/fedora-development-sparc-core/root \
-ihv glibc-2.4-8.sparc64.rpm
$ mock -r fedora-devel-sparc-core --no-clean <path-to-gcc-srpm>
You can't install the 64-bit rpm while inside the chroot, because you're
using the native RPM to do all RPM manipulations; hence the invocation
of rpm.
It's ugly, but I'm not sure I see any other way to do what you're asking.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFE5gtvHyuj/+TTEp0RAucgAKCjoJxHbTxh0mOQPYPRzQco1BLPnwCeNEha
yN19ABYID2WOEmDo10qCbac=
=a50F
-----END PGP SIGNATURE-----
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
