From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Reza Arbab <arbab@linux.ibm.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/skeleton: create lib64 symlink on s390x
Date: Sun, 29 Dec 2024 22:10:26 +0100 [thread overview]
Message-ID: <20241229221026.0f184fed@windsurf> (raw)
In-Reply-To: <20241211170341.450579-1-arbab@linux.ibm.com>
On Wed, 11 Dec 2024 11:03:41 -0600
Reza Arbab <arbab@linux.ibm.com> wrote:
> Building on a s390x host, we currently end up with:
>
> output/host/lib
> output/host/lib32 -> lib
> output/host/lib64
>
> host-libopenssl installs to lib64, but since the kernel build doesn't
> explicitly search there, it breaks:
>
> >>> linux 6.6.32 Building
> [...]
> HOSTCC scripts/sign-file
> /usr/bin/ld: cannot find -lcrypto: No such file or directory
> collect2: error: ld returned 1 exit status
>
> Fix this by creating a lib64 link instead of lib32, so we get:
>
> output/host/lib
> output/host/lib64 -> lib
>
> Signed-off-by: Reza Arbab <arbab@linux.ibm.com>
> ---
> package/skeleton/skeleton.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
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:[~2024-12-29 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 17:03 [Buildroot] [PATCH] package/skeleton: create lib64 symlink on s390x Reza Arbab
2024-12-29 21:10 ` Thomas Petazzoni via buildroot [this message]
2025-01-06 14:03 ` 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=20241229221026.0f184fed@windsurf \
--to=buildroot@buildroot.org \
--cc=arbab@linux.ibm.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