./configure libxrender errir

[ToddAndMargo2]

Hi All,

What is this error and how do I fix it

-T

config.log
configure:9441: checking for X11/extensions/Xrender.h
configure:9441: gcc -m32 -c -g -O2 conftest.c >&5
configure:9441: $? = 0
configure:9441: result: yes

configure: WARNING: libxrender 32-bit development files not found, XRender won't be supported.

[dimesio]

Look through the rest of the log for the part where it says something was not found. As with libpng, it's probably close to the part you posted.

The answer to any other "not found" question is going to be the same. You have to read the log, not just search for strings.

[ToddAndMargo2]

Look through the rest of the log for the part where it says something was not found. As with libpng, it's probably close to the part you posted.

The answer to any other "not found" question is going to be the same. You have to read the log, not just search for strings.

All 49361 lines? Well, I will search on "not found". And there is it:

configure:9395: gcc -m32 -o conftest -g -O2 conftest.c -lXext -lX11 >&5
/usr/bin/ld: skipping incompatible /usr/lib64/libXext.so when searching for -lXext
/usr/bin/ld: cannot find -lXext
collect2: ld returned 1 exit status
configure:9395: $? = 1

# yum --enablerepo=* install libXext-devel-1.3.2-2.1.el6.i686
Did the trick. I will report the reporting bug over on
https://bugs.winehq.org/show_bug.cgi?id=37534
(I am sure they are tired of me by now.)

Thank you so much for helping me with this!
-T

[ToddAndMargo2]

Just created:
https://bugzilla.redhat.com/show_bug.cgi?id=1162848

[ToddAndMargo2]

Just created:
https://bugzilla.redhat.com/show_bug.cgi?id=1162848

This is actually a Wine bug. Red Hat has responded to the above bug report (1162848):

https://bugzilla.redhat.com/show_bug.cgi?id=1162848

Adam Jackson <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NOTABUG
Last Closed| |2014-11-13 12:05:31



--- Comment #2 from Adam Jackson <[email protected]> ---
(In reply to Todd from comment #0)

> The error from Wine is a bogus error. Wine's "./configure" was missing
> "libXext", which libXrender has a dependency. Installing libXext corrected
> the bogus error.
>
> The bogus error was reported to Wine over on:
> https://bugs.winehq.org/show_bug.cgi?id=37534#c8
>
> Their response was:
>
> Every X11 extension (which libXrender is) depends on libXext, that's
> an X11 dependency, not a Wine one.

But that's not true:

hyoscyamine:~% ldd /usr/lib64/libXrender.so.1
linux-vdso.so.1 => (0x00007fff813fc000)
libX11.so.6 => /lib64/libX11.so.6 (0x0000003f22e00000)
libc.so.6 => /lib64/libc.so.6 (0x0000003f20200000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x0000003f22a00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003f20600000)
/lib64/ld-linux-x86-64.so.2 (0x0000003f1fe00000)
libXau.so.6 => /lib64/libXau.so.6 (0x0000003f22600000)

libXrender doesn't link against libXext at all, nor do any of libXrender's
header files refer to any of libXext's.

The check for libXext appears to come from wine itself, either in the expansion
of AC_PATH_XTRA or from WINE_CHECK_SONAME(Xext, ...) in configure.ac. The
Fedora (and presumably EPEL if it's there) wine spec file explicitly says
BuildRequires: libXext-devel to pull it into the buildroot. It's a shame
wine's configure script isn't better about telling you this error, I agree.

> Would you please add libXext as a dependency in libxslt/libXrender's RPM?

Neither libxslt nor libXrender actually depend on libXext, so it would be wrong
to add it.

[dimesio]

FWIW, on openSUSE, the xorg-X11-devel package pulls in libXext-devel as a dependency.

[ToddAndMargo2]

FWIW, on openSUSE, the xorg-X11-devel package pulls in libXext-devel as a dependency.

How about libXrender in open SUSE? Just curious

[dimesio]

It doesn't directly depend on libXext-devel. However: libXrender-devel requires pkgconfig(xproto), which is provided by xorg-x11-proto-devel, which requires pkgconfig(xextproto), which is provided by libXext-devel. So it would end up pulling in that package if it wasn't installed.