devuan testing amd64: fail to compile dwm

jr_bob_dobbs · 03-23-2021, 08:25 AM

This is in Devuan 64bit, Testing.

Tried to compile dwm. Got error:

Code:

In file included from drw.c:6:
/usr/include/X11/Xft/Xft.h:39:10: fatal error: ft2build.h: No such file or directory
   39 | #include <ft2build.h>
      |          ^~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:18: drw.o] Error 1

/usr/include/X11/Xft/Xft.h exists and looks to be a system file, in
other words, already installed and nothing to do with dwm, OK?

I looked and yes, this line does occur in Xft.h:

Code:

#include <ft2build.h>

The file ft2build.h does exist:

Code:

$ ls -l /usr/include/freetype2/ft2build.h
-rw-r--r-- 1 root root 990 Dec  5 03:20 /usr/include/freetype2/ft2build.h

Could someone please explain to me how a system include fails to include another system include and how can I overcome this problem?

Thank you.

p.s. Yes, I am aware that dwm is a package in Devuan, but there are patches and colors I like to use and those have to be hard-coded into the source prior to compilation.

shruggy · 03-23-2021, 08:29 AM

Quote:

Originally Posted by jr_bob_dobbs

p.s. Yes, I am aware that dwm is a package in Devuan, but there are patches and colors I like to use and those have to be hard-coded into the source prior to compilation.

Why won't you download the DEB package source, apply the patches, and rebuild?

Code:

apt-get source dwm
sudo build-dep dwm
<patch the source>
debuild

As to the make error, see this Debian patch.

jr_bob_dobbs · 03-26-2021, 05:08 PM

Thank you for the reply.

The patch command failed with nonsense.

So all the patch really does is change

Code:

INCS = -I${X11INC} -I${FREETYPEINC}
LIBS = -L${X11LIB} -lX11 ${XINERAMALIBS} ${FREETYPELIBS}

to

Code:

INCS = -I${FREETYPEINC}
LIBS = -lX11 ${XINERAMALIBS} ${FREETYPELIBS}

So I manually made the needed edit and compiled.

unexpectedly, that did not solve the problem.

I copied in the binary I'd made in the other distro. Ran fine, which was a nice surprise. OK whatever. Not a proper nor elegant solution but it worked so that's my stopping point.