Can't find correct X libraries on x86-64 (SUSE)

RESOLVED WORKSFORME

Status

defect
RESOLVED WORKSFORME
14 years ago
a year ago

People

(Reporter: roc, Assigned: roc)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

On SUSE 9.2 x86-64, the X libraries are in /usr/X11/lib64. configure does not
look in this directory for X libraries. It finds the 32-bit X libs in
/usr/X11/lib, and tries to use them. Naturally that causes the build to fail.

I resolved the problem by specifying --x-libraries=/usr/X11/lib64, but I'm not
sure how to fix this for real.
In fact it looks like the code that searches for the X libraries, and hence the
problem, might be in autoconf itself. Hmm. Blizzard, is that true?
I'm not sure.  I would ask cls, I think he wrote that code originally.  I wonder
what rhat and the other distros do with the X libraries with multilib.
Patch for the rh spec files, fwiw:


--- SPECS/thunderbird.spec-old  2004-12-11 19:20:02.261825536 -0800
+++ SPECS/thunderbird.spec      2004-12-11 19:22:06.147991976 -0800
@@ -75,6 +75,7 @@
 %setup -q -n mozilla
 cp -f %{SOURCE4} .mozconfig
 echo "ac_add_options --libdir=%{_libdir}" >> .mozconfig
+echo "ac_add_options --x-libraries=/usr/X11R6/%{_lib}" >> .mozconfig
 echo "ac_add_options --with-default-mozilla-five-home=%{tbdir}" >> .mozconfig
 echo "mk_add_options MOZ_MAKE_FLAGS='%{?_smp_mflags}'" >> .mozconfig
 cp -f %{SOURCE5} . 

Comment 4

14 years ago
Actually, the code that searches for the X libraries is a standard autoconf
macro (AC_PATH_XTRA).  I think the only fix is to use --x-libaries for 64bit
builds.  Looking at the autoconf 2.59-75.1 rpm from SLES9 x86_64, there is no
mention of lib64 anywhere so other programs must have to explicitly add that path.
While investigation why this works for me without having any special configure
options like x-libraries, I found that the configure script determines the
location of the X includes and libs by using imake/xmkmf stuff.
This works for me now; configure gets the correct paths via an xmkmf hack. I'm
not sure what was wrong before. Maybe the autoconf on the Mozilla.org machine
that generates 'configure' was updated.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME

Updated

a year ago
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.