All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Maxim Kochetkov <fido_max@inbox.ru>,
	Julien Olivain <ju.o@free.fr>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/postgresql: fix service runtime
Date: Sun, 04 Feb 2024 17:40:14 +0200	[thread overview]
Message-ID: <87il345jah.fsf@tarshish> (raw)
In-Reply-To: <871q9sr42s.fsf@48ers.dk>

Hi Peter,

On Sun, Feb 04 2024, Peter Korsgaard wrote:

>>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>
>  > Julien, All,
>  > On 2024-01-17 22:07 +0100, Julien Olivain spake thusly:
>  >> Since commit 2a8065e "package/postgresql: bump version to 16.1", the
>  >> postgresql service fail to start at runtime with an error:
>  >> 
>  >> FATAL: could not load library
>  >> "/usr/lib/postgresql/dict_snowball.so":
>  >> /usr/lib/postgresql/dict_snowball.so: undefined symbol:
>  >> CurrentMemoryContext
>  >> 
>  >> This is due to the Posgresql autotool configure script trying to
>  >> detect whether the toolchain linker needs --export-dynamic or not.
>  >> This test is done with a runtime execution of a test program, and
>  >> therefore cannot run in cross-compilation. In that case, the
>  >> configure script assumes it is not needed. See commit [1], included
>  >> in PostgreSQL v16.0.
>  >> 
>  >> This commit fixes the issue by forcing the value in _CONF_ENV. The
>  >> package has already a Kconfig dependency on !BR2_STATIC_LIBS, so the
>  >> value can be unconditionally set.
>  >> 
>  >> [1]
>  >> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9db49fc5bfdc0126be03f4b8986013e59d93b91d
>
>  > I've added references to the ML thread upstream, with their position
>  > that cross-compiling is not really a supoprted thing.
>
>  >> Signed-off-by: Julien Olivain <ju.o@free.fr>
>
>  > Applied to master, thanks.
>
> Committed to 2023.11.x, thanks.

Not in 2023.11.x as of commit 7d35d445a1ae ("package/micropython: fix
building after dropping GIT_DIR=. workaround").

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-04 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 21:07 [Buildroot] [PATCH 1/1] package/postgresql: fix service runtime Julien Olivain
2024-01-18  5:30 ` Maxim Kochetkov via buildroot
2024-01-18 18:08 ` Julien Olivain
2024-01-21  9:14 ` Yann E. MORIN
2024-02-04  9:06   ` Peter Korsgaard
2024-02-04 15:40     ` Baruch Siach via buildroot [this message]
2024-02-04 20:59       ` Peter Korsgaard
2024-02-04 20:51     ` Maxim Kochetkov via buildroot
     [not found] <20240117210756.265708-1-ju.o__23021.2395939574$1705525733$gmane$org@free.fr>
2024-01-20 15:30 ` Bernd Kuhls
2024-01-21  9:17   ` Yann E. MORIN

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=87il345jah.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=fido_max@inbox.ru \
    --cc=ju.o@free.fr \
    --cc=peter@korsgaard.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.