Re: Compiling with Sqlite3

Frank Guthausen <[email protected]> Sat, 29 Mar 2025 11:04:47 +0100

Newsgroups	gmane.comp.encryption.gpg.devel
Message-ID	<[email protected]>

TL;DR

The issue was solved by installing the missing package `pkgconf'.

On Fri, 28 Mar 2025 18:43:38 -0500
Jacob Bachmeyer via Gnupg-devel <[email protected]> wrote:
> On 3/28/25 08:13, Frank Guthausen wrote:
> > [...]
> >
> > The command line variables as prefix relative to the line above are:
> >
> > SQLITE3_CFLAGS="-I /usr/include" SQLITE3_LIBS="-L
> > /usr/lib/x86_64-linux-gnu -l sqlite3"  
> 
> Usually those options do not have spaces in my experience; could you
> try:
> 
> SQLITE3_CFLAGS="-I/usr/include"
> SQLITE3_LIBS="-L/usr/lib/x86_64-linux-gnu -lsqlite3"

No difference.

> ...and similarly "close up" the spaces for the GnuTLS options.  I am 
> unsure how, but this *might* be somehow confusing ld?

I checked this again, but I never noticed a difference before.
Sometimes it is easier to read with the space added, because
the options `-I' and `-l' can be confused depending on the font.

> (In particular, was it actually linking GnuTLS or was configure 
> rejecting that library after failing to link a test program?)

GnuTLS without Sqlite3 compiled and linked fine. The binary gpg was
created as expected, and dirmngr was created with gnutls usage as ldd
indicated.

Sqlite3 didn't link the gpg binary with or without GnuTLS.

Meanwhile...
With the installed package pkgconf neither of those
settings is required to create the output with both
active.
-- 
kind regards
Frank

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

signature.asc (application/pgp-signature, 659 B)