Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/rsync: fix openssl static build
Date: Mon, 12 Feb 2024 23:04:22 +0100	[thread overview]
Message-ID: <20240212230422.5e1aff0b@windsurf> (raw)
In-Reply-To: <20231229214418.9331-1-fontaine.fabrice@gmail.com>

On Fri, 29 Dec 2023 22:44:18 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Fix the following openssl static build raised since commit
> 80fa5672da85a110e60be0d2143e85f9e08a0f4a:
> 
> /home/buildroot/autobuild/instance-0/output-1/host/lib/gcc/aarch64_be-buildroot-linux-uclibc/12.3.0/../../../../aarch64_be-buildroot-linux-uclibc/bin/ld: /home/buildroot/autobuild/instance-0/output-1/host/aarch64_be-buildroot-linux-uclibc/sysroot/lib/../lib64/libcrypto.a(libcrypto-lib-c_zlib.o): in function `zlib_oneshot_expand_block':
> c_zlib.c:(.text+0xaec): undefined reference to `uncompress'
> 
> Commit b9a062b354953f3fbfee702bb5b5007598299925 can also be reverted as
> pkg-config will also retrieve -latomic to avoid the following build
> failure:
> 
> /home/autobuild/autobuild/instance-1/output-1/host/lib/gcc/sparc-buildroot-linux-uclibc/10.4.0/../../../../sparc-buildroot-linux-uclibc/bin/ld: /home/autobuild/autobuild/instance-1/output-1/host/sparc-buildroot-linux-uclibc/sysroot/usr/lib/libcrypto.a(threads_pthread.o): in function `CRYPTO_atomic_add':
> threads_pthread.c:(.text+0x208): undefined reference to `__atomic_is_lock_free'
> 
> RSYNC_POST_CONFIGURE_HOOKS must be added to call reconfigure and avoid
> the following build failure after autoreconf:
> 
> autoconf -o configure.sh
> autoheader && touch config.h.in
> configure.sh has CHANGED.
> config.h.in is unchanged.
> You may need to run:
>   make reconfigure
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/6c1636f7556e7370a4c9f6d02c63cf3e20dc985c
>  - http://autobuild.buildroot.org/results/49abbaa1eab94b248bff434b40728065d687e278
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...py-in-crypto-lib-instead-of-MD5_Init.patch | 28 +++++++++++
>  ...-pkg-config-to-retrieve-openssl-depe.patch | 48 +++++++++++++++++++
>  package/rsync/rsync.mk                        | 12 +++--
>  3 files changed, 84 insertions(+), 4 deletions(-)
>  create mode 100644 package/rsync/0001-Check-for-EVP_MD_CTX_copy-in-crypto-lib-instead-of-MD5_Init.patch
>  create mode 100644 package/rsync/0002-configure.ac-use-pkg-config-to-retrieve-openssl-depe.patch

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

  reply	other threads:[~2024-02-12 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 21:44 [Buildroot] [PATCH 1/1] package/rsync: fix openssl static build Fabrice Fontaine
2024-02-12 22:04 ` Thomas Petazzoni via buildroot [this message]
2024-03-16 21:09   ` Peter Korsgaard

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=20240212230422.5e1aff0b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=fontaine.fabrice@gmail.com \
    --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