`configure:3793: error: C compiler cannot create executables`''

Does gcc actually work, try it separately from configure? If it does then are you trying to run the build in a directory you don't have write access to?

The interesting part is ``` configure:3744: gcc conftest.c >&5 /tmp/ccr38YUW.s: Assembler messages: /tmp/ccr38YUW.s:8: Error: unsupported instruction `push' /tmp/ccr38YUW.s:11: Error: unsupported instruction `movq' /tmp/ccr38YUW.s:14: Error: unsupported instruction `pop' configure:3748: $? = 1 ```

I've never seen this, and my best guess is indeed that the compiler setup is broken (emitting assembly for another arch?). Can you try manually building the same thing the *same way* (e.g. just `gcc file.c`)? ```console $ cd /tmp $ cat > conftest.c <<EOF /* confdefs.h */ #define PACKAGE_NAME "Geany" #define PACKAGE_TARNAME "geany" #define PACKAGE_VERSION "1.35" #define PACKAGE_STRING "Geany 1.35" #define PACKAGE_BUGREPORT "https://github.com/geany/geany/issues" #define PACKAGE_URL "" #define PACKAGE "geany" #define VERSION "1.35" /* end confdefs.h. */

int main () {

; return 0; } EOF $ gcc conftest.c ```

If you're compiling as root, you could try using a regular user instead, with a clean checkout/tarball.

Also if you could run try and compile above `conftest.c` like this:

```bash $gcc -S -o result.S conftest.c ```

And paste the contents of `result.S` to see if it's generating valid assembly for your architecture.

One interesting bit that might or might not be related is that uname reports processor and hardware architecture, which it does not for me.

Nah, I get the same almost identical string.

Closed #2040.