On 2018-10-01, at 3:50 PM, Joshua Root wrote:
> On 2018-9-24 18:22 , Ryan Schmidt wrote:
>> https://github.com/ryandesign/macports-base/commits/MacOSX.sdk
>
> Second, I'm not sure about changing the SDK only some of the time, or
> not changing the deployment target.
> I'm not sure how much of
With a couple of very minor modifications, recent versions of clang will
support thread_local storage including support for complex destructors on
10.6.8 using the same emutls.c system that gcc uses to support it. I'll attach
the (amazingly simple) patches below. It picks up the emutls.c support
running the lrtest binary fails:
brethen-air:examples marbre$ ./lrtest
dyld: Library not loaded: libreduce.so
Referenced from:
/opt/local/share/libreduce/x86_64-mac_10.12_sierra-darwin16.7.0/examples/./lrtest
Reason: image not found
Abort trap: 6
I checked it using otool:
brethen-air:exampl
On Oct 5, 2018, at 15:41, Mark Brethen wrote:
> running the lrtest binary fails:
>
> brethen-air:examples marbre$ ./lrtest
> dyld: Library not loaded: libreduce.so
> Referenced from:
> /opt/local/share/libreduce/x86_64-mac_10.12_sierra-darwin16.7.0/examples/./lrtest
> Reason: image not fo
This is all I found in the Makefile:
libreduce.a: $(OBJ)
rm -f libreduce.a
ar rcs libreduce.a $(OBJ)
libreduce.so: $(OBJ)
rm -f libreduce.so
gcc $(FAT) -shared $(OBJ) -o libreduce.so
RedPy.so: $(OBJ) RedPy.o
gcc $(FAT) -shared $(OBJ) RedPy.o $(shell python
> On Oct 5, 2018, at 16:18, Mark Brethen wrote:
>
> libreduce.so: $(OBJ)
> rm -f libreduce.so
> gcc $(FAT) -shared $(OBJ) -o libreduce.so
On this gcc line is where
-install_name /opt/local/lib/libreduce.so
needs to appear.
I know very little regarding libraries, so thank you! It is building without
errors. I also added a similar line for RedPy.so. What about the static
library, libreduce.a, how is it found?
Mark Brethen
mark.bret...@gmail.com
> On Oct 5, 2018, at 4:20 PM, Ryan Schmidt wrote:
>
>
>
>> On Oc
Static and dynamic libraries are found at build time by the paths specified in
-L arguments, like -L/opt/local/lib. When a library is specified with a -l
flag, like -lreduce, it looks for a file libreduce.dylib or libreduce.so or
libreduce.a in each of the directories specified by -L flags, plus
