These instructions are deprecated, do not use this approach on newer Fedora Variants or with 2.4 and higher versions of CDE
CDE now builds on Red Hat but the build is trickier than normal. David Cantrell sent along these note for building CDE. These tips also apply for Fedora 17.
1.) When doing a build, I am doing "make World.dev 2>&1 | tee world.log"
because if I try to do a regular World build, the docs do not build properly
and cause the build to fail. Not sure what I'm missing here.
2.) To install xbitmaps:
yum install xorg-x11-xbitmaps
RHEL ships with OpenMotif, which works fine to build CDE. Fedora users
need to get the source and install it themselves (or get the SRPM from RHEL
and build and install it locally).
Building on a 64-bit system causes some problems when linking. The build
does actually run to completion, it just ends up missing many things. Most
notably dtwm, which gave me the "hung up at dthello" symptom that I see
people reporting. The issue is that the Imakefiles end up trying to look in
/usr/lib for libraries, which is wrong on these systems. To get around
this, I created edited config/cf/host.def and added:
#define UsrLibDir /usr/lib64
That caused everything to build and link correctly.
3.) To run rpcbind in insecure mode on RHEL, you can create a file called
/etc/sysconfig/rpcbind and add this line:
RPCBIND_ARGS="-i"
NOTE: This is no longer necessary with CDE version 2.2.4a and above.
4.) I did everything with SELinux disabled, I advise disabling SELinux if you
want to use CDE.
5.) Likewise, I had to disable iptables and ip6tables to get the session to
launch the background daemons (like the messaging daemon). I would like to
figure out what iptables rules to add that allow it to work rather than
using the big hammer of disabling it entirely. Still, it was enough to work
around the problem for now.
David is also building RPMs for Red Hat and Fedora here:
https://github.com/dcantrell/cderpm
Wiki: LinuxBuild
Wiki: SupportedPlatforms
For version 2.5.1, on Fedora 38 or newer you can compile by following instructions below:
Thanks! starting the rpcbind service fixed the "desktop messaging system could not be started" error I was getting