This one also...
--
Jon Trulson
"If the Martian rope-a-dope don't get him, he'll get himself, he'll
come in too fast and punch himself out."
- one of my brothers, referring to the Curiosity landing.
---------- Forwarded message ----------
From: David Cantrell <david.l.cantr...@gmail.com>
Date: Fri, 17 Aug 2012 10:04:17 -0400
Subject: Re: CDE from git master working on RHEL 6.3 x86_64
To: Jon Trulson <j...@radscan.com>
Cc: peter.howk...@marutan.net
X-Spam-Status: No, hits=0.8 required=5.0 tests=BAYES_50=0.8,
FREEMAIL_FROM=0.001,SPF_PASS=-0.001,T_DKIM_INVALID=0.01 autolearn=no
version=3.3.2
On Thu, Aug 16, 2012 at 05:29:52PM -0600, Jon Trulson wrote:
> On Tue, 14 Aug 2012, David Cantrell wrote:
>
> Hi, sorry for the delay...
Not a problem.
>>Just an email to let you know that I am currently running CDE built on my
>>RHEL 6.3 x86_64 system. I built from git master that I cloned today (HEAD
>>is currently at commit 441a25b36173068e8d3466268b73c1d454224294).
>>
>>Following your instructions at:
>>http://sourceforge.net/p/cdesktopenv/wiki/LinuxBuild/
>>
>>Was helpful. Here are my own notes:
>>
>>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.
>>
>
> There seem to be differing methods of installing/generating locale
> data on various platforms... You can avoid building any of the locales
> (other than C) by (in theory) emptying out DtLocalesToBuild in
> config/site.def
Sufficient for now, thanks.
>>2) A Red Hat or Fedora user would be able to figure out most packages that
>>need to be installed to build CDE. I will get a complete list once I can do
>>a full build in our build system, but two that caught me immediate were:
>>
>> yum install imake
>> yum install xorg-x11-xbitmaps
>>
>
> We recommend installing a dist provided imake since CDE seems to want
> to use it's own, and has cde specific config files...
>
> Did you have any problems with the cde version?
No, I just saw the Imakefiles and assumed I needed xmkmf. However, despite
installing the package, the CDE build still used its own, so that's fine.
>>The former gives you the xmkmf and imake commands (no surprise). The latter
>>gives you /usr/include/X11/bitmaps/root_weave, which is needed to build the
>>DtHelp library.
>>
>
> Interesting.
Yeah, fun one to track down.
>>3) 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.
>>
>
> Hmm... I'm curious about this - do you have a mixed 64/32b system?
> I've always expected the linker to handle this properly (usually
> depending on -m32/64...
I do. x86_64 systems running RHEL or Fedora are all multilib by default.
> I don't think anyone else has had to do this for 64b or 32b builds...
> It should 'just work'... If you are using a mixed system, then it
> might be that a specific '-m32' or '-m64' needs to be added to the
> default cc options.
I tried -m64 initially and it didn't work, however I just tried on a clean
tree and it did work. Didn't clean the tree properly.
>>4) To run rpcbind in insecure mode on RHEL, you can create a file called
>>/etc/sysconfig/rpcbind and add this line:
>>
>> RPCBIND_ARGS="-i"
>>
>
> There may be another option in the future - tirpc... At least I am now
> using this on kubuntu and I no longer need to run in insecure mode. I
> think this is default in new Fedora's (17) - at least according to one
> person in irc, who clued me into it.
Indeed, Fedora uses tirpc as does RHEL. This has been present since Fedora
Core 6. I should give this a try and see if running with -i works.
>>6) 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.
>>
>
> ok. Hmm, well at a minimum, portmapper (111). But I don't have a
> comprehensive list.
Yeah, will work on collecting the list later.
>>Lastly, I created a gdm session file for CDE following these instructions:
>>http://sourceforge.net/p/cdesktopenv/wiki/Createxses
>>
>>It integrates nicely with the stock RHEL install.
>>
>>Current things I've made a note of:
>>* The calendar application fails because it's trying to use rpc.cmsd or
>> something like that.
>
> Yes, rpc.cmsd needs to be started at boot time.
Easy enough.
>>* I'd like to get dtksh building, perhaps even with current upstream ksh93
>> source.
>
> There has been some work on that front, mainly via the bsd porting
> efforts. There seems to be some disagreement on whether we would be
> able to use upstream ksh (or libshell) due to it's license...
>
> It's still disabled on linux currently, not sure anyones tried it
> since the recent large dtksh patches went in.
Yeah, I noticed the patches that went in to master the other day. Going to
give a build a try today. Using the upstream ksh93 source should be fine
given that CDE is LGPLv2+.
>>* I'd like to figure out what I need installed to build docs.
>>* I'd like to test dtlogin and see if I can replace gdm with it.
>>* Clean up compiler warnings as I get bored and come across them.
>
> Excellent.
>
>>
>>I work for Red Hat in engineering. My ultimate goal is to create an RPM of
>>CDE. Not in a rush though, just wanted to pass along my findings to you.
>>It's fun seeing CDE open sourced. I remember it fondly from so long ago. I
>>used it for many many years at previous jobs.
>>
>>
>
> Thanks for the input. Would you mind if I forwarded this on to the
> development list? There are others using RHEL/Fedora, and the docs guy
> wants to keep track of what works on which OS's, and what's required
> to 'make it so'.
>
> If not, I will just pass on the general info so it might help others.
Absolutely, share this with others. I have started a project here:
https://github.com/dcantrell/cderpm
This is for specifically tracking the work I need to do to package CDE on
RHEL and Fedora. I intend to submit patches for general bug fixes directly
to you guys.
--
David Cantrell <david.l.cantr...@gmail.com>
WH6DSN | http://blog.burdell.org/
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
