zig build -Dtarget= with default target makes dynamic library not found

[jackokring]

Zig Version

0.12.0-dev.415+5af5d87ad

Steps to Reproduce and Observed Behavior

Do a zig build -Dtarget=aarch64-linux-gnu when the default architecture is aarch64-linux so my project zig-kring loads a python dynamic .so. This works fine and builds when no target is specified. Fails for wasm-freestanding and surprisingly for aarch64-linux-gnu the default architecture of this MediaTek HP Chromebook Bookworm Debian.

Expected Behavior

At least to build the default architecture when specified correctly.

(venv) jackokring@penguin:~/zig$ zig build -Dtarget=aarch64-linux
zig build-exe kring Debug aarch64-linux: error: error: unable to find Dynamic system library 'python3.11' using strategy 'paths_first'. searched paths: none

zig build-exe kring Debug aarch64-linux: error: the following command exited with error code 1:
/home/jackokring/zig/zig build-exe /home/jackokring/zig/src/main.zig -lpython3.11 -lc --cache-dir /home/jackokring/zig/zig-cache --global-cache-dir /home/jackokring/.cache/zig --name kring -target aarch64-linux -mcpu generic --mod kring::/home/jackokring/zig/kring/src/main.zig --deps kring -isystem /usr/include/python3.11 --listen=- 
Build Summary: 0/3 steps succeeded; 1 failed (disable with --summary none)
install transitive failure
└─ install kring transitive failure
   └─ zig build-exe kring Debug aarch64-linux failure
error: the following build command failed with exit code 1:
/home/jackokring/zig/zig-cache/o/31f873474002e9affa18b8440b2451bb/build /home/jackokring/zig/zig /home/jackokring/zig /home/jackokring/zig/zig-cache /home/jackokring/.cache/zig -Dtarget=aarch64-linux

Is what happens.

[nektro]

this is because passing target at all tells the compiler to prepare the program in a cross-compile way. thus it does not search your system unless explicitly told to in that mode

[RossComputerGuy]

Wouldn't the solution be to check if the target is the same as host instead if the target argument is passed? Sounds like a pretty simple fix.

[gardc]

this is because passing target at all tells the compiler to prepare the program in a cross-compile way. thus it does not search your system unless explicitly told to in that mode

And what would be the way to tell the compiler to search for libraries when cross compiled? E.g. with a build like this

             switch (target.result.cpu.arch) {
                std.Target.Cpu.Arch.aarch64 => {
                    exe.addObjectFile(b.path("cpp/lib/macos-arm/libPcap++.a"));
                    exe.addObjectFile(b.path("cpp/lib/macos-arm/libPacket++.a"));
                    exe.addObjectFile(b.path("cpp/lib/macos-arm/libCommon++.a"));
                    exe.linkFramework("CoreFoundation");
                    exe.linkFramework("SystemConfiguration");
                    exe.linkSystemLibrary("pcap");
                },
                std.Target.Cpu.Arch.x86_64 => {
                    exe.addObjectFile(b.path("cpp/lib/macos-x64/libPcap++.a"));
                    exe.addObjectFile(b.path("cpp/lib/macos-x64/libPacket++.a"));
                    exe.addObjectFile(b.path("cpp/lib/macos-x64/libCommon++.a"));
                    exe.linkFramework("CoreFoundation");
                    exe.linkFramework("SystemConfiguration");
                    exe.linkSystemLibrary("pcap");
                },
                else => @panic("Unsupported macOS architecture"),
            }

The output is just

zig build -Dtarget=aarch64-macos
install
└─ install monitor-client-service
   └─ zig build-exe monitor-client-service Debug aarch64-macos failure
error: error: unable to find dynamic system library 'pcap' using strategy 'paths_first'. searched paths: none