From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next v2 01/16] package/berkeleydb: add option for historic dbm interface
Date: Wed, 9 Aug 2023 20:26:05 +0200 [thread overview]
Message-ID: <20230809202605.1fbe18f9@windsurf> (raw)
In-Reply-To: <20230809173334.2514813-2-bernd@kuhls.net>
On Wed, 9 Aug 2023 19:33:19 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Berkeley DB support in python depends on dbm, when missing python fails
> to detect libdb:
> https://github.com/python/cpython/blob/d2340ef25721b6a72d45d4508c672c4be38c67d3/configure.ac#L4002
>
> quoting python configure log:
> checking for libdb... no
>
> quoting python config.log:
> conftest.c:(.text.startup+0x8): undefined reference to `__db_ndbm_open'
>
> This patch provides a configure option for the historic dbm interface
> to be used by the python package.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/berkeleydb/Config.in | 5 +++++
> package/berkeleydb/berkeleydb.mk | 1 +
> 2 files changed, 6 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-09 18:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 17:33 [Buildroot] [PATCH/next v2 00/16] Update infrastructure to disable the build of certain extensions Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 01/16] package/berkeleydb: add option for historic dbm interface Bernd Kuhls
2023-08-09 18:26 ` Thomas Petazzoni via buildroot [this message]
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 02/16] package/python3: berkeleydb support needs the " Bernd Kuhls
2023-08-09 18:28 ` Thomas Petazzoni via buildroot
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 03/16] package/python3: use upstream build system to disable berkeleydb module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 04/16] package/python3: use upstream build system to disable uuid module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 05/16] package/python3: use upstream build system to disable bzip2/zlib/xz modules Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 06/16] package/python3: use upstream build system to disable curses/readline modules Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 07/16] package/python3: use upstream build system to disable ssl module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 08/16] package/python3: use upstream build system to disable ossaudiodev module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 09/16] package/python3: use upstream build system to disable unicodedata module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 10/16] package/python3: use upstream build system to disable nis module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 11/16] package/python3: use upstream build system to disable decimal module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 12/16] package/python3: use upstream build system to disable CJK codecs Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 13/16] package/python3: use upstream build system to disable pyexpat module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 14/16] package/python3: use upstream build system to disable tk module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 15/16] package/python3: use upstream build system to disable sqlite3 module Bernd Kuhls
2023-08-09 17:33 ` [Buildroot] [PATCH/next v2 16/16] package/python3: Remove infrastructure to disable the build of certain extensions Bernd Kuhls
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=20230809202605.1fbe18f9@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.com \
/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