Happy to. Also adding pike@roxen.com <mailto:pike@roxen.com> back in as we'd 
gotten off of it.

Gist of output is here. 
https://gist.github.com/MikeiLL/7b0e1ff30f909a6194908c025234e3a3

> On Mar 10, 2024, at 8:21 PM, William Welliver <will...@welliver.org> wrote:
> 
> Hi Mike,
> 
> I think there’s possibly been a bit of a miscommunication. When you run 
> “make” in the git cloned directory, does that process complete successfully, 
> or do you get an error? A git checkout requires a working pike to compile and 
> may need to build a minimal pike in order to do that. That minimal pike is 
> (if memory serves) called tpike. I’m just trying to understand where you’re 
> having problems. Maybe you can upload the output of the make process 
> somewhere we can refer to?
> 
> For anyone following, tool -L is kind of like ldd on some other systems. You 
> will note that your homebrew copy of pike uses the gmp dynamic library.
> 
> Sent from my iPhone
> 
>> On Mar 10, 2024, at 8:52 PM, Mike Kilmer <m...@mzoo.org> wrote:
>> 
>> 
>> 
>>> 
>>> I don't think there's a problem with your libgmp (actually, it would be the 
>>> libgmp.dylib not libgmp.a unless you've specifically disabled the 
>>> generation of dynamic libraries when building the gmp library), I think 
>>> it's that -lgmp isn't being added when the pike binary is being generated. 
>>> If you can run otool -L on the pike binary in your build directory and send 
>>> that to me, I think we can rule the library in or out.
>> 
>> Hi, William.
>> 
>> Ccing Chris, my Pike (but not Mac) guru.
>> 
>> I believe you had explaining that otool would be run on a binary after 
>> successful build, and the only one of those I have is the brewed one, so ran 
>> on that. Please pardon if I misunderstood.
>> 
>> otool -L ...Cellar.../bin/pike
>> 
>>      /usr/local/opt/gmp/lib/libgmp.10.dylib (compatibility version 15.0.0, 
>> current version 15.1.0)
>>      /usr/lib/libutil.dylib (compatibility version 1.0.0, current version 
>> 1.0.0)
>>      /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
>> version 1319.100.3)
>>      
>> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 
>> (compatibility version 1.0.0, current version 1228.0.0)
>>      
>> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
>>  (compatibility version 150.0.0, current version 1971.0.0)
>> 

Reply via email to