From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Maxim Kochetkov via buildroot <buildroot@buildroot.org>
Cc: Maxim Kochetkov <fido_max@inbox.ru>
Subject: Re: [Buildroot] [PATCH 1/1] package/postgresql: needs threads
Date: Tue, 3 Sep 2024 22:45:42 +0200 [thread overview]
Message-ID: <20240903224542.0ecdef27@windsurf> (raw)
In-Reply-To: <20240903054622.14033-1-fido_max@inbox.ru>
Hello Maxim,
On Tue, 3 Sep 2024 08:46:22 +0300
Maxim Kochetkov via buildroot <buildroot@buildroot.org> wrote:
> Threads are mandantory since bump to version 16.3 in commit
> https://github.com/postgres/postgres/commit/52afe563206e753f4c45c014fee2459ad0855826
to which Buildroot was updated in commit
73dd1d6b96665574607c8b05189426ad3eb05a6f.
> diff --git a/package/postgresql/Config.in b/package/postgresql/Config.in
> index 899907d6a5..9faed419bc 100644
> --- a/package/postgresql/Config.in
> +++ b/package/postgresql/Config.in
> @@ -32,9 +32,9 @@ config BR2_PACKAGE_POSTGRESQL_FULL
>
> endif
>
> -comment "postgresql needs a toolchain w/ dynamic library, wchar"
> +comment "postgresql needs a toolchain w/ dynamic library, wchar, threads"
> depends on BR2_USE_MMU
> - depends on BR2_STATIC_LIBS || !BR2_USE_WCHAR
> + depends on BR2_STATIC_LIBS || !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
>
> comment "postgresql can't be built with Optimize for fast"
> depends on BR2_OPTIMIZE_FAST
Unfortunately, this is not sufficient to add a dependency, you also
need "depends on BR2_TOOLCHAIN_HAS_THREADS" in BR2_PACKAGE_POSTGRESQL.
Then, you need to go through all the reverse dependencies of postgresql:
package/bandwidthd/Config.in: select BR2_PACKAGE_POSTGRESQL
package/collectd/Config.in: select BR2_PACKAGE_POSTGRESQL
package/lighttpd/Config.in: select BR2_PACKAGE_POSTGRESQL
package/php/Config.ext: select BR2_PACKAGE_POSTGRESQL
package/php/Config.ext: select BR2_PACKAGE_POSTGRESQL
package/poco/Config.in: select BR2_PACKAGE_POSTGRESQL
package/python-psycopg2/Config.in: select BR2_PACKAGE_POSTGRESQL
package/qt5/qt5base/Config.in: select BR2_PACKAGE_POSTGRESQL
package/qt6/qt6base/Config.in: select BR2_PACKAGE_POSTGRESQL
package/zabbix/Config.in: select BR2_PACKAGE_POSTGRESQL
and check that they all have a BR2_TOOLCHAIN_HAS_THREADS dependency,
and if not, add it. And then look at their reverse dependencies.
Also, another thing is that postgresql.mk has:
ifneq ($(BR2_TOOLCHAIN_HAS_THREADS_NPTL),y)
POSTGRESQL_CONF_OPTS += --disable-thread-safety
endif
so does it mean that this option is no longer supported? No longer
exists?
Also, does it now need thread support, or NPTL thread support
specifically? (You can figure out by building with a Buildroot
configuration that has BR2_PTHREADS instead of BR2_PTHREADS_NATIVE).
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-09-03 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 5:46 [Buildroot] [PATCH 1/1] package/postgresql: needs threads Maxim Kochetkov via buildroot
2024-09-03 20:45 ` Thomas Petazzoni via buildroot [this message]
2024-09-04 5:52 ` Maxim Kochetkov via buildroot
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=20240903224542.0ecdef27@windsurf \
--to=buildroot@buildroot.org \
--cc=fido_max@inbox.ru \
--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