search for: weak_import

...semi-emulate aliases (at least within one module). My goal is to at least turn them into strong aliases somehow, so I can at a minimum make the musl source compatible with clang on macos. The following compiles but foo is not exported: $ cat a.c #include <stdio.h> void foo() __attribute__((weak_import)) __asm("_bar"); void bar() { printf("bar\n"); } int main() { foo(); } $ cc -c a.c -o a.o $ nm a.o 0000000000000000 T _bar 0000000000000020 T _main U _printf Any ideas how I can get foo as an exported symbol? Is weak alias or plan alias sup...

...least within one module). My goal is to at least turn them into strong aliases somehow, so I can at a minimum make the musl source compatible with clang on macos. The following compiles but foo is not exported: > > $ cat a.c > #include <stdio.h> > > void foo() __attribute__((weak_import)) __asm("_bar"); > > void bar() > { > printf("bar\n"); > } > > int main() > { > foo(); > } > > $ cc -c a.c -o a.o > $ nm a.o > 0000000000000000 T _bar > 0000000000000020 T _main > U _printf >...

...ypervisor.framework, but I was not sure about your use case. If you need full control of the address space (PAGE_ZERO control, overriding the shared cache mappings, etc) that is really the only supported mechanism. > The issue I am having with libSystem.dylib is the lack of weak linkage (versus weak_import) i.e. weak aliases. I don’t want to use a wrapper binary with DYLD_INSERT_LIBRARIES. I want to interpose Libc symbols with some of the symbols present in my binary (memory allocator, mmap). Interposition support is somewhat lacking in the Mach-O toolchain and runtime linker despite the Mach-O forma...

1.6.1 svn 190575: CC="cc" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect make[1]: Entering directory `/home/asterisk/rpmbuild/BUILD/asterisk-1.6.1/menuselect' gcc -m64 -march=native -mtune=native -floop-interchange -floop-strip-mine -floop-block -c -o