After installing maintenance pack 3 on OSR507, GNU configure for at
least two X11 packages, xpdf (v3.0) and ImageMagick (v6.0x), does the
wrong thing when determining where to find X11 libraries and headers.
I suspect other X packages will also have this problem.

If configure is invoked without the --x-* options, it will use the
X11R6 libraries in /usr/X11R6/lib and the X11R5 headers from
/usr/include. This mix will cause the compilation to fail. Solution
is to force use of either X11R5 or X11R6 components using:

--x-libraries=/usr/lib
--x-includes=/usr/include
or
--x-libraries=/usr/X11R6/lib
--x-includes=/usr/X11R6/include

In the case of xpdf 3.0, using the X11R6 components allows the build
to finish, but the resulting xpdf executable produces a memory
fault/core dump on invocation. The fault occurs in the call to
XtAppInitialize() at line 119 of XPDFApp.cc. xpdf built with the
X11R5 components works.
--
Roger Cornelius rac@tenzing.org

rac@tenzing.org (Roger Cornelius) wrote in message news:<450ab60f.0408090802.28d5dd60@posting.google. com>...
> After installing maintenance pack 3 on OSR507, GNU configure for at
> least two X11 packages, xpdf (v3.0) and ImageMagick (v6.0x), does the
> wrong thing when determining where to find X11 libraries and headers.
> I suspect other X packages will also have this problem.
>
> If configure is invoked without the --x-* options, it will use the
> X11R6 libraries in /usr/X11R6/lib and the X11R5 headers from
> /usr/include. This mix will cause the compilation to fail. Solution
> is to force use of either X11R5 or X11R6 components using:
>
> --x-libraries=/usr/lib
> --x-includes=/usr/include
> or
> --x-libraries=/usr/X11R6/lib
> --x-includes=/usr/X11R6/include

This is a known issue, but it's really in "configure", which is using
one approach to detect the X11 headers and another approach to detect
the X11 libraries. Since OSR 5.0.7 supp 3 has two sets of X11 libraries
on it, the problem results. I guess you'll just have to carry on with
this work-around.

Jonathan Schilling

"J. L. Schilling" wrote:
>
> rac@tenzing.org (Roger Cornelius) wrote in message news:<450ab60f.0408090802.28d5dd60@posting.google. com>...
> > After installing maintenance pack 3 on OSR507, GNU configure for at
> > least two X11 packages, xpdf (v3.0) and ImageMagick (v6.0x), does the
> > wrong thing when determining where to find X11 libraries and headers.
> > I suspect other X packages will also have this problem.
> >
> > If configure is invoked without the --x-* options, it will use the
> > X11R6 libraries in /usr/X11R6/lib and the X11R5 headers from
> > /usr/include. This mix will cause the compilation to fail. Solution
> > is to force use of either X11R5 or X11R6 components using:
> >
> > --x-libraries=/usr/lib
> > --x-includes=/usr/include
> > or
> > --x-libraries=/usr/X11R6/lib
> > --x-includes=/usr/X11R6/include
>
> This is a known issue, but it's really in "configure", which is using
> one approach to detect the X11 headers and another approach to detect
> the X11 libraries. Since OSR 5.0.7 supp 3 has two sets of X11 libraries
> on it, the problem results. I guess you'll just have to carry on with
> this work-around.

I figured it was a configure problem. I just wanted to get this
archived so the next person won't have to figure it out.
--
Roger Cornelius racpop@tenzing.org

J. L. Schilling typed (on Tue, Aug 10, 2004 at 02:21:57PM -0700):
| rac@tenzing.org (Roger Cornelius) wrote in message news:<450ab60f.0408090802.28d5dd60@posting.google. com>...
| > After installing maintenance pack 3 on OSR507, GNU configure for at
| > least two X11 packages, xpdf (v3.0) and ImageMagick (v6.0x), does the
| > wrong thing when determining where to find X11 libraries and headers.
| > I suspect other X packages will also have this problem.
| >
| > If configure is invoked without the --x-* options, it will use the
| > X11R6 libraries in /usr/X11R6/lib and the X11R5 headers from
| > /usr/include. This mix will cause the compilation to fail. Solution
| > is to force use of either X11R5 or X11R6 components using:
| >
| > --x-libraries=/usr/lib
| > --x-includes=/usr/include
| > or
| > --x-libraries=/usr/X11R6/lib
| > --x-includes=/usr/X11R6/include
|
| This is a known issue, but it's really in "configure", which is using
| one approach to detect the X11 headers and another approach to detect
| the X11 libraries. Since OSR 5.0.7 supp 3 has two sets of X11 libraries
| on it, the problem results. I guess you'll just have to carry on with
| this work-around.

I just grabbed the source for ghostscript-8.31. I did NOT use either of
those sets of --x-* options when I ran configure. Compilation was no
problem (except for some nonsense regarding bool if I didn't exclude
jasper).

Explicitly, I did NOT see that "... without the --x-* options,it will
use the X11R6 libraries in /usr/X11R6/lib and the X11R5 headers from
/usr/include. This mix will cause the compilation to fail." It didn't
fail at all.

I've now got a gs binary about which ldd reports:

/usr/local/bin/gs needs:
/usr/X11R6/lib/libXt.so.6.0
/usr/X11R6/lib/libSM.so.6.0
/usr/X11R6/lib/libICE.so.6.3
/usr/X11R6/lib/libXext.so.6.4
/usr/X11R6/lib/libX11.so.6.2
/usr/lib/libsocket.so.2
/usr/lib/libpng.so.2
/usr/lib/libjpeg.so.62
/usr/lib/libz.so.1
/usr/lib/libm.so.1
/usr/lib/libc.so.1

The binary runs just fine.

--
JP

Jean-Pierre Radley wrote:
>
> J. L. Schilling typed (on Tue, Aug 10, 2004 at 02:21:57PM -0700):
> | rac@tenzing.org (Roger Cornelius) wrote in message news:<450ab60f.0408090802.28d5dd60@posting.google. com>...
> | > After installing maintenance pack 3 on OSR507, GNU configure for at
> | > least two X11 packages, xpdf (v3.0) and ImageMagick (v6.0x), does the
> | > wrong thing when determining where to find X11 libraries and headers.
> | > I suspect other X packages will also have this problem.
> | >
> | > If configure is invoked without the --x-* options, it will use the
> | > X11R6 libraries in /usr/X11R6/lib and the X11R5 headers from
> | > /usr/include. This mix will cause the compilation to fail. Solution
> | > is to force use of either X11R5 or X11R6 components using:
> | >
> | > --x-libraries=/usr/lib
> | > --x-includes=/usr/include
> | > or
> | > --x-libraries=/usr/X11R6/lib
> | > --x-includes=/usr/X11R6/include
> |
> | This is a known issue, but it's really in "configure", which is using
> | one approach to detect the X11 headers and another approach to detect
> | the X11 libraries. Since OSR 5.0.7 supp 3 has two sets of X11 libraries
> | on it, the problem results. I guess you'll just have to carry on with
> | this work-around.
>
> I just grabbed the source for ghostscript-8.31. I did NOT use either of
> those sets of --x-* options when I ran configure. Compilation was no
> problem (except for some nonsense regarding bool if I didn't exclude
> jasper).
>
> Explicitly, I did NOT see that "... without the --x-* options,it will
> use the X11R6 libraries in /usr/X11R6/lib and the X11R5 headers from
> /usr/include. This mix will cause the compilation to fail." It didn't
> fail at all.
>
> I've now got a gs binary about which ldd reports:
>
> /usr/local/bin/gs needs:
> /usr/X11R6/lib/libXt.so.6.0
> /usr/X11R6/lib/libSM.so.6.0
> /usr/X11R6/lib/libICE.so.6.3
> /usr/X11R6/lib/libXext.so.6.4
> /usr/X11R6/lib/libX11.so.6.2
> /usr/lib/libsocket.so.2
> /usr/lib/libpng.so.2
> /usr/lib/libjpeg.so.62
> /usr/lib/libz.so.1
> /usr/lib/libm.so.1
> /usr/lib/libc.so.1
>
> The binary runs just fine.

If you check config.log you will see that the X11R6 libs were used but
with the X11R5 headers. At least that is the case when I build it. The
fact it compiles and runs is a fluke. Mixing versions is asking for
problems.
--
Roger Cornelius racpop@tenzing.org