Thanks -- the following
Code:
yum --installroot=/media/OS/home/f14 install kernel-headers kernel-devel
yum --installroot=/media/OS/home/f14 install gcc
worked, but there's one loose end -- the module that provided ld ended up creating the following:
Code:
cd /media/OS/home/f14/usr/bin
ls -laF ld
ld -> /etc/alternatives/ld
cd /media/OS/home/f14/etc/alternatives
ls -laF ld*
ld -> /usr/bin/ld.bfd
The above is strange since the use of absolute paths in the links means that there will be issues when the modules are installed in a non-default location (as is being done in the installation under discussion)!
Workaround: Modify the soft-links to use relative paths:
Code:
cd /media/OS/home/f14/etc/alternatives
ln -s ../../usr/bin/ld.bfd ld
ln -s ../../usr/bin/ld.bfd ld.bfd
cd /media/OS/home/f14/usr/bin
# Should have used a relative path in the next command
# Even better, could have just done: ln -s ld.bfd ld
ln -s /media/OS/home/f14/etc/alternatives/ld ld
Question: Why doesn't the module that provides ld use relative paths in the soft links -- thereby allowing that module to be easily installed in a non-standard location?