Description of problem:
Lots of 3-rd-party programs specify "-L/usr/X11R6/lib" in their Makefiles in
order to pick up Motif library via "-lXm". Usually the libXm.so->libXm.so.3.0.2
symlink is owned by openmotif-devel*.rpm.
BUT, since there's no openmotif-devel-*.i386.rpm for x86_64, NO PACKAGE creates
/usr/X11R6/lib/libXm.so (yes, /usr/X11R6/lib64/libXm.so does exist).
The right fix would be to add this symlink to regular x86_64's
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ls -l /usr/X11R6/lib/libXm.so
ls: /usr/X11R6/lib/libXm.so: No such file or directory
lrwxrwxrwx 1 root root 14 Sep 2 2005 /usr/X11R6/lib/libXm.so ->
Since FC5 places Motif libraries into /usr/lib* instead of /usr/X11R6/lib*, it
is probably unaffected -- "-lXm" would pick the library anyway. But FC4's
default behaviour is annoying.
The openmotif-devel.i386 package provides this symlink.
Yes, the openmotif-devel.i386 DOES provide this link, but there is NO
openmotif-devel.i386 under FC4/x86_64:
.../fedora/4% find . -name 'openmotif*'
And attempt to install i386's openmotif-devel.i386 would lead to conflict
between files with openmotif-devel.x86_64.
openmotif-devel.i386 from FC4 i386 can be installed to solve this problem.
I wonder why there's no distinct package for FC4 x86_64.
This will be fixed in FC6. Note that any package trying to build x86_64 binaries
by adding -L/usr/X11R6/lib are just broken, and won't link correctly even with
the i386 openmotif-devel shipped.
(In reply to comment #4)
> This will be fixed in FC6. Note that any package trying to build x86_64 binaries
> by adding -L/usr/X11R6/lib are just broken, and won't link correctly even with
> the i386 openmotif-devel shipped.
Yes, that's true. And most Makefiles allow simply passing "CFLAGS=-m32" to
'make', which could fix the problem. But when there's no 32-bit libXm.so,
And, by the way, absence of openmotif-devel.i386 means that one can't build i386
Motif programs on x86_64 machine, which is just nonsence.
Yea, was just wanting to make sure which you're building. For FC4 and FC5 we
only shipped a limited development environment for compat arches (generally, the
LSB set.) For FC6, we're cleaning things up so we can ship a full devel
environment; since this involves some significant cleanup to headers,
<foo>-config scripts, etc., it's a little much to backport to earlier FC releases.