Re: [WBEL-users] Anyone know about 64-bit build hosts?

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0234460194==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig62DB39F42BCE098A0B6A6E1B"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig62DB39F42BCE098A0B6A6E1B
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Vic wrote:
> Hi All.
>=20
> I hope someone can point out my glaring mistake(s) here...
>=20
> Now that the last[1] 64-bit package has finished building[2], I want to=

> integrate my build environments - at present, I've got a 32-bit
> installation and a 64-bit installation, and I choose the appropriate on=
e
> at boot time.
>=20
> What I want to do is to be able to build the 32-bit packages in the 64-=
bit
> install. Which should be easy - but I can't get the hang of it.
>=20
> I've tried "setarch i386" on the command line. I've tried "--target=3Di=
386".
> I've added %_arch, %_target, and %_target_cpu to my rpmmacros. Still my=

> test build is trying to link to a 64-bit output file[3] :-(
>=20
> Anyone know what incredibly obvious thing I've forgotten?
>=20
> Everything Google finds for me tells me to use mock - but as I'm
> bootstrapping the distribution, I don't think that will work. It'll als=
o
> be *incredibly* slow...
>=20
> Thanks!
>=20
> Vic.
>=20
> [1] Well, except for openCryptoki, which really doesn't want to build -=

> and I'm not suifficiently interested in it to spend much more time on i=
t.
>=20
> [2] openoffice only takes 10 hours to build on my new box. And it only
> failed 3 times. Grrr.
>=20
> [3] Specifically, I get warnings from ld saying stuff like "i386
> architecture of input file `.libs/xa_map.o' is incompatible with
> i386:x86-64 output"

Vic,

Your best bet is to use mock on x86_64 to build i386 packages.

Fedora uses mock to build all their packages and RHEL uses something=20
similar (brewbuild).  CentOS builds all CentOS-4 and CentOS-5 packages=20
in mock, and Scientific Linux also uses mock.

When you build x86_64 packages, you need to do so in a clean buildroot=20
with only x86_64 packages (and glibc.i686 or glibc-devel.i386 if=20
required for a couple packages).

Mock allows you to do both (a clean buildroot for all packages and i386=20
buildroots on x86_64 machines).

Thanks,
Johnny Hughes
CentOS Developer


--------------enig62DB39F42BCE098A0B6A6E1B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFI1OwyTKkMgmrBY7MRAk7hAKCHysB4w+cvzHzqOKjPPBX1tSCDPACgmfC7
/32Pb6UnMkZe9xEeGs/YCN4=
=OGo5
-----END PGP SIGNATURE-----

--------------enig62DB39F42BCE098A0B6A6E1B--

--===============0234460194==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Whitebox-users mailing list
[email protected]
http://beau.org/mailman/listinfo/whitebox-users

--===============0234460194==--