On Mon, 21 Dec 2020 at 06:27, ToddAndMargo via users <users@lists.fedoraproject.org> wrote:
On 12/20/20 9:09 PM, C Linus Hicks wrote:
> On Sun, 2020-12-20 at 20:39 -0800, ToddAndMargo via users wrote:
>> Hi Cameron,
>>
>> This is my fault for not being clear enough.
>> I can't use a "C" (time.h) library for what
>> I am doing.
>>
>> What I need is a call to something inside
>>       /usr/lib64/libxxxx.so.x
>>
>> And I do not know which one will give me the
>> time.
>>
>> Thank you you anyway! Much appreciated.
>>
>> -T
>
> This still isn't clear. Is there some reason why you can't or don't want to 'use a "C" (time.h)
> library'?
>
> Saying that you want to use something like /usr/lib64/libxxxx.so.x would suggest you have some idea
> about using a library that isn't a standard part of the base distribution, in which case you need to
> install that specific software on your system and know how to make the appropriate call.
>
> C. Linus Hicks

Hi C,

I am using Raku's NativeCall.  It only talks to .so's
and .dll's.

I could use time.h if I was programming in C, but I am
not.  I suppose if I understood C better, I could
root around in time.c and find where time.c call
the system.

-T

I'm not sure if I walked off the beaten track, but does this example help? (i was looking at it out of interest and noticed it)
 https://docs.raku.org/language/nativecall#Specifying_the_native_representation