From: ologantr <ologantr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sqlite: update to 3.38.0, fossil: update to 2.18.
Date: Sat, 05 Mar 2022 21:42:48 +0100 [thread overview]
Message-ID: <20220305204248.adMjRmsQCtbavEwD2A_7T6oCP9-MilD37Wi-NJlCMHY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35796@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
New comment by ologantr on void-packages repository
https://github.com/void-linux/void-packages/pull/35796#issuecomment-1059827392
Comment:
> If that is what you want :) As a sidenote: In my tests fossil seems to need both `--disable-internal-sqlite` and -`-with-sqlite="${XBPS_CROSS_BASE}/usr/include/"` in order to use the system sqlite. I may be mistaken, but check it out.
Yes, you're right: without --with-sqlite, configure
falls back to the fossil-provided one even if
--disable-internal-sqlite was used. I've
updated fossil and added this switch.
I've just noticed that common/shlib entry
for sqlite is lagging behind: I'm going to
bump it while here.
next prev parent reply other threads:[~2022-03-05 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 21:47 [PR PATCH] sqlite: update to 3.38.0 ologantr
2022-03-05 7:59 ` mobinmob
2022-03-05 8:01 ` mobinmob
2022-03-05 8:01 ` mobinmob
2022-03-05 19:54 ` ologantr
2022-03-05 20:01 ` mobinmob
2022-03-05 20:30 ` [PR PATCH] [Updated] " ologantr
2022-03-05 20:32 ` ologantr
2022-03-05 20:42 ` ologantr [this message]
2022-03-05 20:47 ` [PR PATCH] [Updated] sqlite: update to 3.38.0, fossil: update to 2.18 ologantr
2022-03-08 21:47 ` [PR PATCH] [Merged]: " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220305204248.adMjRmsQCtbavEwD2A_7T6oCP9-MilD37Wi-NJlCMHY@z \
--to=ologantr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).