This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
static sqlite makes the library way too big #5
Comments
Only if somebody comes up with support for another database, which is very robust, stable, well maintained, fits with the licenses, etc. |
How does the original lastlog achieve this?
And what about utmpx or whatever? Same conundrum?
bless,
g
From: Thorsten Kukuk
Sent: Tuesday, 9 May 2023 11:59 PM
To: thkukuk/lastlog2
Reply To: thkukuk/lastlog2
Cc: gagan sidhu; Author
Subject: Re: [thkukuk/lastlog2] static sqlite makes the library way too big (Issue #5)
is there any way i can use lastlog2 while keeping the size down?
Only if somebody comes up with support for another database, which is very robust, stable, well maintained, fits with the licenses, etc.
I haven't found an alternative and thus I have no plans to add support for other databases.
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AITLEG6XM2TPOWFC6HB4GN3XFMVEVANCNFSM6AAAAAAX32XW5U>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
sparse files and direct seek access, which is one of the problems why this is not fixable for Y2038.
With glibc: utmp = utmpx |
thanks thorsten, i guess i'll just have to use regular lastlog for now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
hi,
since i use lastlog in my embedded firmware, i thought maybe looking ahead would be helpful.
however using sqlite is prohibitive as it adds another megabyte i cannot afford to my build.
when i try to link statically, as you'd imagine, the shared library blows up to ~1.1M since it needs a lot of the calls from sqlite.
is there any way i can use lastlog2 while keeping the size down?
The text was updated successfully, but these errors were encountered: