List of targets that currently fail to build with zig cc

[Cloudef]

Zig Version

0.11.0-dev.22+57dbeb90a

Steps to Reproduce and Observed Behavior

#include <stdio.h>
int main() {
   printf("hello world\n");
   return 0;
}

zig cc -target target-here hello.c

Or to take into account the libc musl builds:

• On x86_64 linux system with nix-build installed
• Clone this repo https://github.com/Cloudef/nix-zig-stdenv
• Go to test folder and run ./run build-package-for-all-targets master super-simple

Expected Behavior

zig cc produces a working executable for the target.

Additional notes

Musl platforms, also build musl libc

Following targets were not tested as nixpkgs does not seem to support them.

      "csky-unknown-linux-gnueabi"
      "csky-unknown-linux-gnueabihf"
      "x86_64-unknown-linux-gnux32"
      "armeb-unknown-linux-gnueabi"
      "armeb-unknown-linux-musleabi"
      "armeb-unknown-linux-gnueabihf"
      "armeb-unknown-linux-musleabihf"
      "armeb-w64-mingw32"

Attached is raw log of build messages of each failed target
build-package-log.zip

The log can also be viewed here until github purges it: https://github.com/Cloudef/nix-zig-stdenv/actions/runs/3383399186/jobs/5619255104

[PiotrSikora]

This can be also checked using (IMHO) much simpler way:

for target in `zig targets | jq .libc[] | grep -v freestanding | cut -d\" -f2`; do
    echo "$target => `zig cc -target $target hello.c 2>/tmp/zig-cc-$target && echo OK || grep -m1 error: /tmp/zig-cc-$target`";
done

As of 0.11.0-dev.4320+6f0a613b6, the list of failed zig cc targets (grouped by cause):

aarch64_be-linux-gnu => ld.lld: error: unknown emulation: aarch64_be_linux
aarch64_be-linux-musl => ld.lld: error: unknown emulation: aarch64_be_linux
armeb-linux-gnueabi => ld.lld: error: unknown emulation: armebelf_linux_eabi
armeb-linux-gnueabihf => ld.lld: error: unknown emulation: armebelf_linux_eabi
armeb-linux-musleabi => ld.lld: error: unknown emulation: armebelf_linux_eabi
armeb-linux-musleabihf => ld.lld: error: unknown emulation: armebelf_linux_eabi
s390x-linux-musl => ld.lld: error: unknown emulation: elf64_s390
sparc-linux-gnu => ld.lld: error: unknown emulation: elf32_sparc

csky-linux-gnueabi => error: unable to create target: 'No available targets are compatible with triple "csky-unknown-linux-gnueabi"'
csky-linux-gnueabihf => error: unable to create target: 'No available targets are compatible with triple "csky-unknown-linux-gnueabihf"'
m68k-linux-gnu => error: unable to create target: 'No available targets are compatible with triple "m68k-unknown-linux-gnu"'

s390x-linux-gnu => error: unknown target CPU 'generic'; note: valid target CPU values are: arch8, z10, arch9, z196, arch10, zEC12, arch11, z13, arch12, z14, arch13, z15, arch14, z16

arm-windows-gnu => error: Function '__cxa_thread_atexit' uses ARM instructions, but the target does not support ARM mode execution.

aarch64_be-windows-gnu => error: 1Only Win32 target is supported! (in mingw)
armeb-windows-gnu => error: 1Only Win32 target is supported! (in mingw)

mips64el-linux-gnuabi64 => error: unknown type name '__time64_t' (in glibc)
mips64-linux-gnuabi64 => error: unknown type name '__time64_t' (in glibc)

mips64el-linux-gnuabin32 => error: call to undeclared function '__cp_kstat_stat64_t64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] (in glibc)
mips64-linux-gnuabin32 => error: call to undeclared function '__cp_kstat_stat64_t64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] (in glibc)

riscv64-linux-gnu => error: unknown directive .cfi_label .Ldummy (in glibc)

sparc64-linux-gnu => lots of errors around types (in glibc)

thumb-linux-gnueabi => lots of errors around types (in glibc)
thumb-linux-gnueabihf => lots of errors around types (in glibc)

m68k-linux-musl => Trace/breakpoint trap (core dumped)

[alexrp]

arc, csky, m68k, and xtensa are not relevant here as they are experimental LLVM targets. 99% of Zig users can't compile for these because we don't build the support into Zig releases.

For the rest, I don't think we really need this meta-issue as we're already tracking them over here: https://github.com/ziglang/zig-bootstrap?tab=readme-ov-file#supported-triples

[Cloudef]

Yeah I realized the support matrix is on the release pages too
https://ziglang.org/download/0.13.0/release-notes.html