I'm trying to build a bugfixed anaconda package for 5.3 x84_64, but there are some fairly basic failures, like pkg-config .pc files not being found. When I modify the spec file accordingly, linking fails because installed libraries are not found.
$ rpmbuild -ba anaconda.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.25019 + umask 022 + cd /usr/src/redhat/BUILD + LANG=C + export LANG + unset DISPLAY + cd /usr/src/redhat/BUILD + rm -rf anaconda-11.1.2.168 + /usr/bin/bzip2 -dc /usr/src/redhat/SOURCES/anaconda-11.1.2.168.tar.bz2 + tar -xf - ... for d in isys wlite stubs loader2 po textw utils scripts bootdisk installclasses iw pixmaps isomd5sum command-stubs ui fonts; do make -C $d depend; done make[1]: Entering directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/isys' grep NFS_MOUNT_VERSION /usr/include/linux/nfs_mount.h | sed -e 's/NFS/KERNEL_NFS/' > nfs_mountversion.h Package libdhcp6client was not found in the pkg-config search path. Perhaps you should add the directory containing `libdhcp6client.pc' to the PKG_CONFIG_PATH environment variable Package 'libdhcp6client', required by 'libdhcp', not found cc -E -M -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -Werror -D_GNU_SOURCE =1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -DUSESELINUX=1 -I/usr/include/python2.4 -I.. -DHAVE_NFS nfsmount.c nfsmount_clnt.c nfsmount_xdr.c imount.c smp.c devnodes.c cpio.c uncpio.c dasd.c lang.c isofs.c dns.c linkdetect.c vio.c ethtool.c wireless.c eddsupport.c nl.c str.c auditd. c isys.c > .depend In file included from isys.c:55: /usr/include/libdhcp/pump.h:78:22: error: dhcp_nic.h: No such file or directory make[1]: *** [depend] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/isys' make[1]: Entering directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/wlite' make[1]: *** No rule to make target `depend'. Stop. make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/wlite' make[1]: Entering directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/stubs' make[1]: Nothing to be done for `depend'. make[1]: Leaving directory `/usr/src/redhat/BUILD/anaconda-11.1.2.168/stubs' Package libdhcp6client was not found in the pkg-config search path. Perhaps you should add the directory containing `libdhcp6client.pc' to the PKG_CONFIG_PATH environment variable Package 'libdhcp6client', required by 'libdhcp', not found ...
etc. Any ideas how to fix this? The same package builds find under i386.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
lhecking@users.sourceforge.net writes:
I'm trying to build a bugfixed anaconda package for 5.3 x84_64, but there are some fairly basic failures, like pkg-config .pc files not being found. When I modify the spec file accordingly, linking fails because installed libraries are not found.
Nevermind. I figured out out it's a good idea to use mock, and it builds cleanly.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
On 08/21/2009 05:57 PM, lhecking@users.sourceforge.net wrote:
I'm trying to build a bugfixed anaconda package for 5.3 x84_64,
What bugs are you trying to fix here ?
Karanbir Singh writes:
On 08/21/2009 05:57 PM, lhecking@users.sourceforge.net wrote:
I'm trying to build a bugfixed anaconda package for 5.3 x84_64,
What bugs are you trying to fix here ?
Borked kickstart build in 5.2/5.3. I didn't follow the issue closely, but a patch for it was finally posted.
http://bugs.centos.org/view.php?id=2975 https://bugzilla.redhat.com/show_bug.cgi?id=448006
What I'm really trying to do is build a new stage2.img :)
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
On 08/23/2009 01:36 PM, lhecking@users.sourceforge.net wrote:
http://bugs.centos.org/view.php?id=2975 https://bugzilla.redhat.com/show_bug.cgi?id=448006 What I'm really trying to do is build a new stage2.img :)
afaict, that should be usable with just an updates.img - you dont need to rebuild the whole installer for just that.
Karanbir Singh writes:
On 08/23/2009 01:36 PM, lhecking@users.sourceforge.net wrote:
http://bugs.centos.org/view.php?id=2975 https://bugzilla.redhat.com/show_bug.cgi?id=448006 What I'm really trying to do is build a new stage2.img :)
afaict, that should be usable with just an updates.img - you dont need to rebuild the whole installer for just that.
Interesting, never knew about that :-)
What are the contents of updates.img, just the files from the anaconda+ runtime packages? Not sure it'll work, though; I have just tested the new stage2.img, and I still get the same "no bootfile" message. But I don't know if my method of rebuilding stage2 only is correct.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
Karanbir Singh writes:
On 08/23/2009 01:36 PM, lhecking@users.sourceforge.net wrote:
http://bugs.centos.org/view.php?id=2975 https://bugzilla.redhat.com/show_bug.cgi?id=448006 What I'm really trying to do is build a new stage2.img :)
afaict, that should be usable with just an updates.img - you dont need to rebuild the whole installer for just that.
I've done that - dropped in the updates.img with anaconda+runtime on ext2. But I'm still getting the same installer error that the patch is supposed to fix.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
On 08/24/2009 06:16 PM, lhecking@users.sourceforge.net wrote:
I've done that - dropped in the updates.img with anaconda+runtime on ext2. But I'm still getting the same installer error that the patch is supposed to fix.
are you sure its being used ? apart from that, you really are better off working with the issue on the bugtracker, the anaconda developers would also mostly like to get feedback if the patch isnt working.
are you sure its being used ? apart from that, you really are better off working with the issue on the bugtracker, the anaconda developers would also mostly like to get feedback if the patch isnt working.
You are right. I got a response from David Cantrell and he pointed out how I was going about this completely the wrong way. Will hopefully get this working tomorrow.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
Joseph L. Casale writes:
You are right. I got a response from David Cantrell and he pointed out how I was going about this completely the wrong way. Will hopefully get this working tomorrow.
Please post your procedure, I have been following this thread with interest!
In brief:
The bug I referenced is in the loader. It is built as part of anaconda, but the copy of it that runs at install time is in initrd.img. So, the procedure is to grab the latest anaconda srpm and the patch from bugzilla, build the rpms, extract the loader from anaconda-runtime, and replace the one in initrd.img. The latter can be done with the upd-initrd script from the anaconda srpm. You need to make sure that all the bits and pieces are built for the same arch.
My error was that I assumed this bug was in the stage2 image because that's where I found anaconda.
I was able to build the anaconda.i386, but not x86_64, which I needed. That's where mock came in handy, I used it with the srpm generated by the i386 build to create the x86_64 rpms.
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
-
Joseph L. Casale -
Karanbir Singh -
lhecking＠users.sourceforge.net