Fix relative path error for compiler wrappers in fuzzer Justfiles

[rifatarefin]

Problem

Multiple fuzzer Justfile recipes fail during the lib task while running just run:

/bin/bash: line 2: target/release/libafl_cc: No such file or directory
make[1]: *** [Makefile:1196: contrib/tools/pngfix.o] Error 127

Root Cause

LIBAFL_CC and LIBAFL_CXX were defined as relative paths (e.g., CARGO_TARGET_DIR / PROFILE_DIR / "libafl_cc"). Invoking make -C <subdir> later in the recipe resolves the relative path from the target subdirectory instead of the project root, resulting in an invalid compiler path.

Solution

Wrap compiler wrapper definition with absolute_path() so the path remains valid regardless of working directory change:

CARGO_TARGET_DIR := absolute_path(env("CARGO_TARGET_DIR", "target"))

This ensures that when make -C changes into other directory, the compiler path is still correct.

Affected Fuzzers

• inprocess/libfuzzer_libmozjpeg
• inprocess/libfuzzer_libpng_accounting
• inprocess/libfuzzer_libpng_norestart
• inprocess/libfuzzer_libpng_tcp_manager
• structure_aware/nautilus_sync

Testing

After the fix, just run completes successfully on all affected fuzzers without path resolution errors.