Hey all...
I know what is causing it to fail, but I'm not certain why. The what is that mock/yum is not pulling in glibc-devel for i386 into the mock chroot. So it is causing the multi-lib stuff to fail. In my root.log I can see glibc-devel for x86_64 was installed in the chroot. But why is it not pulling glibc-devel.i386 into the chroot?
I'm using mock-0.9.7-1.el5 from EPEL.. mock config file and relevent build.log portion below..
Thanks in advance... Paul...
----------------------
/etc/mock/centos-5-x86_64.cfg:
#!/usr/bin/python -tt import os
config_opts['root'] = 'centos-5-x86_64' config_opts['target_arch'] = 'x86_64'
config_opts['dist'] = 'centos5' # only useful for --resultdir variable subst
# ccache not available on epel5 config_opts['plugin_conf']['ccache_enable'] = False
config_opts['yum.conf'] = """ [main] cachedir=/var/cache/yum debuglevel=1 reposdir=/dev/null logfile=/var/log/yum.log retries=20 obsoletes=1 gpgcheck=0 assumeyes=1 exclude=[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefhijklmnopqrstuvwxyz]*.i*86 g[abcdefghijkmnopqrstuvwxyz]*.i?86 glib2.i?86 glib.i?86 *-devel.i?86 # repos
[os] name=os mirrorlist=http://mirrorlist.centos.org/?release=5&arch=x86_64&repo=os #baseurl=http://mirror.centos.org/centos/5/os/x86_64/
[updates] name=updates mirrorlist=http://mirrorlist.centos.org/?release=5&arch=x86_64&repo=updates #baseurl=http://mirror.centos.org/centos/5/updates/x86_64/
[groups] name=groups baseurl=http://dev.centos.org/centos/buildsys/5/ """
config_opts['macros']['centos_ver'] = '5'
--------------------
mock command output:
[pauls@smith gcc]$ mock -r centos-5-x86_64 --rebuild /net/tomcat/vol/vol1/builds/mirror/centos/5.2/os/SRPMS/gcc-4.1.2-42.el5.src.rpm INFO: mock.py version 0.9.7 starting... State Changed: init plugins State Changed: start INFO: Start(/net/tomcat/vol/vol1/builds/mirror/centos/5.2/os/SRPMS/gcc-4.1.2-42.el5.src.rpm) Config(centos-5-x86_64) State Changed: lock buildroot State Changed: clean State Changed: init State Changed: lock buildroot INFO: enabled root cache INFO: enabled yum cache State Changed: cleaning yum metadata State Changed: running yum State Changed: creating cache State Changed: setup State Changed: build ERROR: Exception(/net/tomcat/vol/vol1/builds/mirror/centos/5.2/os/SRPMS/gcc-4.1.2-42.el5.src.rpm) Config(centos-5-x86_64) 15 minutes 33 seconds INFO: Results and/or logs in: /var/lib/mock//centos-5-x86_64/result ERROR: Command failed. See logs for output. # ['bash', '--login', '-c', 'rpmbuild -bb --target x86_64 --nodeps builddir/build/SPECS/gcc41.spec']
-----------------------------
relevant parts from /var/lib/mock//centos-5-x86_64/result/build.log:
make[4]: *** [32/crtend.o] Error 1 make[4]: *** Waiting for unfinished jobs.... In file included from /usr/include/features.h:352, from /usr/include/stdio.h:28, from ../../gcc/tsystem.h:90, from ../../gcc/crtstuff.c:68: /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory make[4]: *** [32/crtbegin.o] Error 1 make[4]: *** [32/crtendS.o] Error 1 In file included from /usr/include/features.h:352 , from /usr/include/stdio.h:28 , from ../../gcc/tsystem.h:90 , from ../../gcc/crtstuff.c:68 : /usr/include/gnu/stubs.h:7:27:
error: gnu/stubs-32.h: No such file or directory make[4]: *** [32/crtbeginS.o] Error 1 make[4]: Leaving directory `/builddir/build/BUILD/gcc-4.1.2-20080102/obj-x86_64-redhat-linux/gcc' make[3]: *** [extra32] Error 2 make[3]: Leaving directory `/builddir/build/BUILD/gcc-4.1.2-20080102/obj-x86_64-redhat-linux/gcc' make[2]: *** [stmp-multilib] Error 2
Paul B Schroeder wrote:
Hey all...
I know what is causing it to fail, but I'm not certain why. The what is that mock/yum is not pulling in glibc-devel for i386 into the mock chroot. So it is causing the multi-lib stuff to fail. In my root.log I can see glibc-devel for x86_64 was installed in the chroot. But why is it not pulling glibc-devel.i386 into the chroot?
I'm using mock-0.9.7-1.el5 from EPEL.. mock config file and relevent build.log portion below..
this isnt a enduser support list, please take your querry to somewhere relevant.
- KB
On Thu, 2008-06-26 at 20:08 +0100, Karanbir Singh wrote:
Paul B Schroeder wrote:
Hey all...
I know what is causing it to fail, but I'm not certain why. The what is that mock/yum is not pulling in glibc-devel for i386 into the mock chroot. So it is causing the multi-lib stuff to fail. In my root.log I can see glibc-devel for x86_64 was installed in the chroot. But why is it not pulling glibc-devel.i386 into the chroot?
I'm using mock-0.9.7-1.el5 from EPEL.. mock config file and relevent build.log portion below..
this isnt a enduser support list, please take your querry to somewhere relevant.
Hmm.. Not certain if your comment was meant to be as snippy as it came across to me. But apologies from me..
I realize this is not an end user support list. But I'm developing a CentOS based distro, trying to do what y'all just did with 5.2. Thought it might be relevant..
Thanks...Paul..
P.S. I worked it out..
Paul B Schroeder wrote:
I'm using mock-0.9.7-1.el5 from EPEL.. mock config file and relevent build.log portion below..
this isnt a enduser support list, please take your querry to somewhere relevant.
Hmm.. Not certain if your comment was meant to be as snippy as it came across to me. But apologies from me..
No, was not meant to be snappy.
I realize this is not an end user support list. But I'm developing a CentOS based distro,
why ?
P.S. I worked it out..
cool :D
On Thu, 2008-06-26 at 23:18 +0100, Karanbir Singh wrote:
Paul B Schroeder wrote:
I'm using mock-0.9.7-1.el5 from EPEL.. mock config file and relevent build.log portion below..
this isnt a enduser support list, please take your querry to somewhere relevant.
Hmm.. Not certain if your comment was meant to be as snippy as it came across to me. But apologies from me..
No, was not meant to be snappy.
Ok.. Cool..
I realize this is not an end user support list. But I'm developing a CentOS based distro,
why ?
We simply need to make our own customizations for internal stuff that we need to support.
Cheers...Paul...
On Thu, Jun 26, 2008 at 3:10 PM, Paul B Schroeder paul.schroeder@bluecoat.com wrote:
Thanks...Paul..
P.S. I worked it out..
I was going to say you were excluding all -devel.i?86... Was this the source of trouble???
Akemi
On Thu, 2008-06-26 at 15:19 -0700, Akemi Yagi wrote:
On Thu, Jun 26, 2008 at 3:10 PM, Paul B Schroeder paul.schroeder@bluecoat.com wrote:
Thanks...Paul..
P.S. I worked it out..
I was going to say you were excluding all -devel.i?86... Was this the source of trouble???
Actually, no. Looks like I pasted in the wrong mock config... Somehow... At any rate, my mock config is essentially the same (minus the -devel.i?86), but uses our local, rsynced repo. I'm thinking something may be screwy with our local repo.
I'm getting around it, for now, by using this in my mock config: config_opts['chroot_setup_cmd'] = 'install buildsys-build glibc-devel.x86_64 glibc-devel.i386'
Cheers...Paul..
On Fri, Jun 27, 2008 at 8:50 AM, Paul B Schroeder paul.schroeder@bluecoat.com wrote:
On Thu, 2008-06-26 at 15:19 -0700, Akemi Yagi wrote:
P.S. I worked it out..
I was going to say you were excluding all -devel.i?86... Was this the source of trouble???
Actually, no. Looks like I pasted in the wrong mock config... Somehow... At any rate, my mock config is essentially the same (minus the -devel.i?86), but uses our local, rsynced repo. I'm thinking something may be screwy with our local repo.
I'm getting around it, for now, by using this in my mock config: config_opts['chroot_setup_cmd'] = 'install buildsys-build glibc-devel.x86_64 glibc-devel.i386'
I see. That is not a real fix. Well, if we want to continue the talk, we would have to go "somewhere else" before KB kicks us out. ;-P
Akemi