32-bit chroot build environment

[hakonrk]

I have a question about creating a 32-bit chroot build environment on an x86-64 system. I know that mock is usually the best solution for this, but mock is only for SRPMs. I have some programs that work better (or will only work) in 32-bit mode that I can't compile via SRPMs for various reasons (usually that I want the latest CVS/SVN snapshot).

I thought it would be easy to create my own build environment using rpm --root /path/to/buildenv -ivh <list-of-i386-packages>. True, I was able to get a working development environment this way, but everything I run in this environment still detects that the kernel runs in 64-bit mode. For example, uname -m still returns x86_64 and configure claims the system type is x86_64-unknown-linux-gnu.

Is it possible to fool the programs running in the buildenv completely so that they'll behave exactly as if running on a native i386 system?

[leigh123linux]

Originally Posted by hakonrk

I have a question about creating a 32-bit chroot build environment on an x86-64 system. I know that mock is usually the best solution for this, but mock is only for SRPMs. I have some programs that work better (or will only work) in 32-bit mode that I can't compile via SRPMs for various reasons (usually that I want the latest CVS/SVN snapshot).

I thought it would be easy to create my own build environment using rpm --root /path/to/buildenv -ivh <list-of-i386-packages>. True, I was able to get a working development environment this way, but everything I run in this environment still detects that the kernel runs in 64-bit mode. For example, uname -m still returns x86_64 and configure claims the system type is x86_64-unknown-linux-gnu.

Is it possible to fool the programs running in the buildenv completely so that they'll behave exactly as if running on a native i386 system?

Try rebuilding the SRPM ( edit the spec file and replace the source code with the new svn / cvs source code )

su
yum install rpmdevtools

Then as non root

rpmdev-setuptree

This will set up a normal build environment in /home/*/rpmbuild
Then install the SRPM as non root.

rpm -i package.src.rpm

Then edit the spec and change the source code package , then build the spec file in a normal 64 bit environment to see if it builds OK .

rpmbuild -ba  /home/*/rpmbuild/SPECS/package.spec

The above command will produce rpm & srpm packages if successful , then you can build this altered srpm in mock .

[hakonrk]

Thanks again, leigh. Not the answer I was hoping for as I've already got some nice build scripts I wanted to use, but since no-one else had any other suggestions, I guess I have to roll up my sleeves and start customizing spec files...