#libtool
Live, measured metrics for the hashtag #libtool from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #libtool
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 13:27 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 13:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:27 UTCEverything below is measured over the latest 10 public posts (spanning ~61993 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 1.6
Top of the latest posts
Today's bug is a `libtool` bug: https://savannah.gnu.org/support/index.php?111193 There `libtool` fails to supply enough compiler runtime libraries for `clang`+`compiler-rt` build toolchain. #libtool #bug
Not all surprises are bad: #libtool maintainers have finally applied my patch first submitted in June 2011 today (https://savannah.gnu.org/patch/?8843). This is my personal record (and by far) for the longest time between patch submission a
Trying to wrap my head around the #libtool and #pkgconf vs pkg-config situation. What is going on? Why is libtool bad, what is wrong with .la files, what does libtool do that pkgconf doesn't, and what does pkg-config do that neither of them
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/libtool