Dne st 23. března 2022 Dr. Nikolaus Klepp napsal(a):
Ok, this was a nobrainer:
There is a slightly wrong path in
imlib/files/patch-search-system-include-for-xshm.diff. Please change
"/usr/include/X11/extensions/XShm.h" to
"/usr/local/include/X11/extensions/XShm.h" (note the /local/ part in it)
and compile. This at least fixed the problem for my system :)
Nik
$ diff patch-search-system-include-for-xshm.diff~
patch-search-system-include-for-xshm.diff 8c8
< + if test -f "$x_includes/X11/extensions/XShm.h" || test -f
"/usr/include/X11/extensions/XShm.h"; then ---
+ if test -f
"$x_includes/X11/extensions/XShm.h" || test -f
"/usr/local/include/X11/extensions/XShm.h"; then
On my test system:
# ll /usr/local/include/X11/extensions/XShm.h
-rw-r--r-- 1 root wheel 3735 Apr 8
2021 /usr/local/include/X11/extensions/XShm.h
And from my build.log:
checking sys/shm.h usability... yes
checking sys/shm.h presence... yes
checking for sys/shm.h... yes
checking whether shmctl IPC_RMID allowes subsequent attaches... yes
checking X11/extensions/XShm.h... yes
checking for jpeg_destroy_decompress in -ljpeg... yes
checking for jpeglib.h... yes
By visiting your make.log I see that the problem probably has the beginning
already in the detection of Xorg. While on my system is:
checking for X... libraries /usr/local/lib, headers /usr/local/include
On your system is:
checking for X... libraries , headers
It is a question of whether it is the correct behavior or whether there
should be listed paths, as you can see in my case. This is not specific to
imlib - this is the result of the call AC_PATH_X macro from automake.
Cheers
As I did a clean install with minimal packages I assume that all users will run into this
problem.
Could it be that you have a symlink from /usr/include/X11 to /usr/local/include/X11 ?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...