Zig cc not linking shared libraries correctly

[ccoverstreet]

Version 0.6.0

• Files/
  • foo.c
  • foo.h
  • main.c

Running zig cc -fPIC -c foo.c -o foo.o and zig cc -shared foo.o -o libbar.so successfully creates a shared library; however, when trying to link to the library, zig cc main.c -L. -lbar -o driver, the wrong name is used (libfoo.so.0). It seems like Zig cc uses the first object file of the library instead of the name of the shared library.

This code works fine if I change zig cc -shared foo.o -o libbar.so to zig cc -shared foo.o -o libfoo.so.

[kubkon]

Hmm, I think this might be Elf specific since I cannot replicate the behaviour with MachO minus using libbar.dylib instead of .so.

[LemonBoy]

Hmm, I think this might be Elf specific since I cannot replicate the behaviour with MachO minus using libbar.dylib instead of .so.

It is ELF-specific, the linker invocation done by Zig always includes the -soname flag set to the root object name (foo.o here).
Setting the SONAME should be opt-in and not opt-out, double so if you consider zig cc should behave as cc does and the latter doesn't set it behind your back.

[kubkon]

Good point! I agree with it being an opt-in rather than opt-out, especially if this means we're better aligned with cc.

[andrewrk]

Fixed in 9268972, cherry-picked into 0.7.x in f09f960