Can't find libXext when ./configure
hi, just upgraded to SuSE 8 today and installed all the recommended patches via the online update. but for some reason, everytime i try to ./configure anything X related, it tells me it can't find "X includes". so i run "./configure --x-include=/usr/X11/include/ --x-libraries=/usr/X11/lib/" and it works. but now it says: "configure: error: We need a working libXext to proceed. Since configure can't find it itself, we stop here assuming that make wouldn't find them either." but i find the libXext.so.6 stuff in /usr/X11/include. can someone help? thank you, Xiaolei
propheci
just upgraded to SuSE 8 today and installed all the recommended patches via the online update. but for some reason, everytime i try to ./configure anything X related, it tells me it can't find "X includes". so i run "./configure --x-include=/usr/X11/include/ --x-libraries=/usr/X11/lib/" and it works. but now it says:
If you want to pass the directories directly, it should be --x-include=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
but i find the libXext.so.6 stuff in /usr/X11/include.
I seriously doubt that you have it in /usr/X11R6/include ;-)
can someone help?
Yes, install xdevel.rpm. To compile sources you always need these *-devel.rpm packages as those contain headers and the lib<something>.so symlinks the linkers needs to find the library. Philipp
Philipp Thomas
Yes, install xdevel.rpm. To compile sources you always need these *-devel.rpm packages as those contain headers and the lib<something>.so symlinks the linkers needs to find the library.
What is the rational for providing separate *-dev.rpm packages rather than including the headers etc in the "standard" package? The headers do not (normally) take up much space and the libXXX.so.n has to included (in the normal package) in order for programs to use it, so why not include everything in the one package?
Graham Murray
Philipp Thomas
writes:
What is the rational for providing separate *-dev.rpm packages rather than including the headers etc in the "standard" package?
It's mostly saving space.
The headers do not (normally) take up much space
Oh, headers can take up quite a bit of space, specially in the case of xdevel. xdevel is unpacked ~10MiB, with headers taking 2.5 MiB.
and the libXXX.so.n has to included (in the normal package) in order for programs to use it,
It's the symlink libxxx.so that's included in the -devel package.
so why not include everything in the one package?
You forget that -devel packages can contain quite bit of additional stuff: - There's the static libraries (*only* possibly needed when compiling) - additional configuration stuff (in case of xdevel it's /usr/X11R6/lib/X11/config, i.e. the whole imake configury) - Documentation that's only interesting for developers (API docu, man pages for library functions). - Sample code. - Extra development tools (like moc from Qt). That all can sum up quite nicely and even if it's not much for one package, the sum of all development packages does represent a noticeable sum. Why should those that never compile a package of their own waste space for stuff they don't need? Philipp
Le Lundi 10 Juin 2002 05:33, Philipp Thomas a écrit / wrote :
propheci
[ Sun, 9 Jun 2002 21:43:05 -0500]: but i find the libXext.so.6 stuff in /usr/X11/include.
I seriously doubt that you have it in /usr/X11R6/include ;-)
Sure ;-) francis@linux:~> locate libXext /usr/X11R6/lib/libXext.a /usr/X11R6/lib/libXext.so /usr/X11R6/lib/libXext.so.6 /usr/X11R6/lib/libXext.so.6.4 and... francis@linux:~> rpm -q --whatprovides /usr/X11R6/lib/libXext.so.6 xshared-4.2.0-64 Francis
participants (4)
-
Francis Allouchery
-
Graham Murray
-
Philipp Thomas
-
propheci