I'm using a 64-bit Debian Unstable, and got the source code from here: https://www.scummvm.org/frs/scummvm/1.9.0/scummvm-1.9.0.tar.xz

It doesn't want to make at all, gives me this error:

code:

---

$ make
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
    C++      backends/platform/sdl/sdl.o
In file included from ./backends/platform/sdl/sdl.h:26:0,
                 from backends/platform/sdl/sdl.cpp:31:
./backends/platform/sdl/sdl-sys.h:151:17: fatal error: SDL.h: No such file or directory
 #include <SDL.h>
                 ^
compilation terminated.

---

code:

---

$ make
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
    C++      backends/platform/sdl/sdl.o
backends/platform/sdl/sdl.cpp:31:39: fatal error: backends/platform/sdl/sdl.h: No such file or directory
 #include "backends/platform/sdl/sdl.h"
                                       ^
compilation terminated.
Makefile.common:103: recipe for target 'backends/platform/sdl/sdl.o' failed
make: *** [backends/platform/sdl/sdl.o] Error 1

---

   

Is libsdl-dev (or even better: libsdl2-dev) installed?

Install it, revert your changes and then rerun configure and make.

   

Both libsdl1.2-dev and libsdl2-dev are installed.

code:

---

$ apt policy libsdl1.2-dev
libsdl1.2-dev:
  Installed: 1.2.15+dfsg1-4
  Candidate: 1.2.15+dfsg1-4
  Version table:
     1.2.15+dfsg1-4 500
        500 http://debian.mirror.linux.com unstable/main amd64 Packages
        100 /var/lib/dpkg/status

$ apt policy libsdl2-dev
libsdl2-dev:
  Installed: 2.0.5+dfsg1-1
  Candidate: 2.0.5+dfsg1-1
  Version table:
 *** 2.0.5+dfsg1-1 500
        500 http://debian.mirror.linux.com unstable/main amd64 Packages
        100 /var/lib/dpkg/status

---

   

Oh I think I see why you would think so. I am not a C++ guru but I think the following is correct:

#include <foo.h> means look in INCLUDE directories (which configure would set up)
#include "foo.h" looks at the current directory

(So for SDL2 for example <SDL.h> is actually /usr/include/SDL2/SDL.h)

This why I thought sdl was not installed or that configure couldn't find it.

My sid laptop is still broken, so I'm gonna set up a sid VM later and look at this. In the meantime, can you pastebin (or similar) the output of configure along with the contents of config.log and config.mk?

(Don't paste the raw text in the forum. Use pastebin.com or similar and post the link)

   

quote:

---

Originally posted by tsoliman
In the meantime, can you pastebin (or similar) the output of configure along with the contents of config.log and config.mk?

---

quote:

---

Originally posted by tsoliman
(Don't paste the raw text in the forum. Use pastebin.com or similar and post the link)

---

   

I just realised what the problem was. I've set '--prefix=$HOME' and the fool was looking for SDL's include files in the home folder. It's weird as how configure uses the same prefix for installing and for SDL's files. Luckly the other dependencies' paths seem unaffected. So I ended up adding '--with-sdl-prefix=/usr', and now it compiled as expected.

   

Just curious, why do --prefix=$HOME?

Are you going to do a make install or something?

   

Yes, I prefer to have some of my executables in the home folder, to avoid losing them in case I change the distro, or I have to reinstall the OS.