Hi. I'm using the "normal commands" and getting message "i cannot relocate object of this function in the .o, you need to enable -fPIC or use -Wl,-x,notext" when you make the object.
#1 when I make the object using cc -c, cc uses -d, so i "assume" it should be: "cc a.c -o a.o -Wl,-f,PIC" is that right?
#1.1 I AM NOT PORTING LINUX I AM MAKING A freeBSD native app (I do not want libtool advice) I know since 4.3BSD it's been possible to make .so on freeBSD (up to the switch from gcc to clang, and it was not the same as for linux, but worked).
#2 i've tried every combination of "old rule of thumb" commands all of the result in the same message
#3 I cannot find any documentation for shared lib making for freebsd by google. but the scripts are "pretty hairy" i am looking for a few magic commands (the easy ones not some jargon of selecting readonly reloc per symbol or calculating depends)
#4 i understand (barely) that one has an option of (including and using) /use/shared/mk/bsd.lib.mk or something and took a look at it. i'm not interested in a ubuntu-style robot refusing to work for me base on "not naming my lib properly". right now i just want "foo.so", period. i understand freebsd isn't linux and i may have to learn more, or maybe not. I just want the linker options free and clear of macro jargon and macro "you can't do that on my system" refusals.
#1 when I make the object using cc -c, cc uses -d, so i "assume" it should be: "cc a.c -o a.o -Wl,-f,PIC" is that right?
#1.1 I AM NOT PORTING LINUX I AM MAKING A freeBSD native app (I do not want libtool advice) I know since 4.3BSD it's been possible to make .so on freeBSD (up to the switch from gcc to clang, and it was not the same as for linux, but worked).
#2 i've tried every combination of "old rule of thumb" commands all of the result in the same message
#3 I cannot find any documentation for shared lib making for freebsd by google. but the scripts are "pretty hairy" i am looking for a few magic commands (the easy ones not some jargon of selecting readonly reloc per symbol or calculating depends)
#4 i understand (barely) that one has an option of (including and using) /use/shared/mk/bsd.lib.mk or something and took a look at it. i'm not interested in a ubuntu-style robot refusing to work for me base on "not naming my lib properly". right now i just want "foo.so", period. i understand freebsd isn't linux and i may have to learn more, or maybe not. I just want the linker options free and clear of macro jargon and macro "you can't do that on my system" refusals.