On 1/4/22 10:13 AM, Ben Jones wrote:

> So I think I need to specify that I want to explicitly include libc when
> I link it.  `-lc` didn't seem to work.

Did you add -lc and -lpthread on the linker line?

> ld build/*.o -L. -lphobos2 -o build/executable

Ali

On Tuesday, 4 January 2022 at 18:26:41 UTC, Ali Çehreli wrote:
> On 1/4/22 10:13 AM, Ben Jones wrote:
>
> > So I think I need to specify that I want to explicitly
> include libc when
> > I link it.  `-lc` didn't seem to work.
>
> Did you add -lc and -lpthread on the linker line?
>
> > ld build/*.o -L. -lphobos2 -o build/executable
>
> Ali

Maybe it's a mac thing and that will work when I get to linux, but I did try that and ld couldn't find the lib:

```
ld: library not found for -lc
```

Same result for -lpthread, and for -pthread (no l)

On Tuesday, 4 January 2022 at 18:13:56 UTC, Ben Jones wrote:
> clang -c -o source/assignment1.o source/assignment1.c

you might have better luck just telling clang to link it too

like

clang source/assignment1.o -lphobos2 build/*.o # etc

since there's a bunch of default search paths and libs etc the compiler pass to the linker.

otherwise if you do need to use the linker directly worth remembering the order of args matter too. you need to put the more derived dependencies first followed by more general ones at the end

On Tuesday, 4 January 2022 at 18:37:25 UTC, Adam D Ruppe wrote:
> On Tuesday, 4 January 2022 at 18:13:56 UTC, Ben Jones wrote:
>> clang -c -o source/assignment1.o source/assignment1.c
>
> you might have better luck just telling clang to link it too
>
> like
>
> clang source/assignment1.o -lphobos2 build/*.o # etc
>
> since there's a bunch of default search paths and libs etc the compiler pass to the linker.
>
> otherwise if you do need to use the linker directly worth remembering the order of args matter too. you need to put the more derived dependencies first followed by more general ones at the end

Using clang seems to work better.  It sounds like Apple basically hides system libraries since Big Sur, and I guess their clang knows the magic flags to pass to find them.

Thanks!

On Tuesday, 4 January 2022 at 18:45:37 UTC, Ben Jones wrote:
> On Tuesday, 4 January 2022 at 18:37:25 UTC, Adam D Ruppe wrote:
>> On Tuesday, 4 January 2022 at 18:13:56 UTC, Ben Jones wrote:
>>> clang -c -o source/assignment1.o source/assignment1.c
>>
>> you might have better luck just telling clang to link it too
>>
>> like
>>
>> clang source/assignment1.o -lphobos2 build/*.o # etc
>>
>> since there's a bunch of default search paths and libs etc the compiler pass to the linker.
>>
>> otherwise if you do need to use the linker directly worth remembering the order of args matter too. you need to put the more derived dependencies first followed by more general ones at the end
>
> Using clang seems to work better.  It sounds like Apple basically hides system libraries since Big Sur, and I guess their clang knows the magic flags to pass to find them.
>
> Thanks!

All good, except now simpledisplay is segfaulting on XDisplayConnection.get again (you helped me before by specifying a DISPLAY environment variable, but that's not working now, with either :0 or the longer value set by xquartz when opening an xterm).  I'm not sure how it can segfault since there are null checks in that method... maybe I should just head to the linux lab and stop fighting Apple.

On Tuesday, 4 January 2022 at 19:10:25 UTC, Ben Jones wrote:
> All good, except now simpledisplay is segfaulting on XDisplayConnection.get again

run it in the debugger; do a -g build and run it in gdb or lldb and do check the exact line it is on.

could be that the Xlib things didn't dynamically load. I thought I tested that but could have missed a spot and Apple has a bad habit of movign things so who knows.