I'm about to take delivery of a ruggadised processor which ships with a version of Fedora Core 4 but contains no development tools as part of its Linux distribution. The manual says a vanilla Fedora Core 4 installation can be used to compile up any applications. Noticing that FC4 is archived I looked at using Fedora Core 9 to compile up all my source code.

In particular I'm looking to use the GTK+ libraries, so if I download all the necessary libraries and dependencies and build from scratch, can I
compile using the default FC9 development tool chain, making sure I use the correct header files and libraries, and copy the resulting application across to FC4 and it will work?

Do I have to recompile the tool chain (gcc, libtool etc) with FC4 kernel headers and then compile the GTK sources?

Each version of Fedora uses a different version of GCC(and a lot of libs too). Without another FC4 box you are going to run into a lot of little(and some not so little) gotchas.

This is super easy. All you need to do is make a new folder on your system and copy over the contents of the / partition from a FC4 system. Then use the 'chroot' command to go into that folder and you can even use yum to install more packages!

For example.

On the FC4 system use the rsync command to copy it to your system at 192.168.1.10 into the /home/fc4/ folder by:

rsync -av --progress --stats / root@192.168.1.10:/home/fc4/

Once it is all copied over get a root terminal open on your FC9 box and do this:

chroot /home/fc4/

And you'll have every tool that was installed on that FC4 box available!

anonbomber

Apparently you missed that part(above). Almost all(if not all) the FC4 repos are gone now.

You could just dual boot your machine with FC4: http://www.filewatcher.com/b/ftp/ftp...6/iso.0.0.html

You probably would have to stick with the initial install versions of all the packages, unless you could find a FC4 repo that was still around(long shot).

You can build your program on the FC9 then pack it using Ermine (http://magicErmine.com) or statifier (http://statifier.sf.net)
Resulting executable should work on nearly all Linux disro without need to install any shared library

Thanks for the help.

I was wondering how to get the chroot command to 'stick', I didn't want to run as root in a terminal after the chroot command is executed to compile the source code up.

I then found this link which solves the problem http://www.kegel.com/crosstool/curre...gin-howto.html