Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Reza Arbab <arbab@linux.ibm.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/skeleton: create lib64 symlink on s390x
Date: Mon, 06 Jan 2025 15:03:31 +0100	[thread overview]
Message-ID: <87msg4ghu4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20241211170341.450579-1-arbab@linux.ibm.com> (Reza Arbab's message of "Wed, 11 Dec 2024 11:03:41 -0600")

>>>>> "Reza" == Reza Arbab <arbab@linux.ibm.com> writes:

 > 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>

Committed to 2024.02.x and 2024.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2025-01-06 14:03 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
2025-01-06 14:03 ` Peter Korsgaard [this message]

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=87msg4ghu4.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=arbab@linux.ibm.com \
    --cc=buildroot@buildroot.org \
    /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