Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/4] package/libbpf: fix cross compilation for 32-bit targets
Date: Thu, 27 Oct 2022 08:46:19 +0200	[thread overview]
Message-ID: <20221027084619.67b393b2@windsurf> (raw)
In-Reply-To: <20221020141412.346992-2-tobias@waldekranz.com>

On Thu, 20 Oct 2022 16:14:09 +0200
Tobias Waldekranz <tobias@waldekranz.com> wrote:

> Add upstream patch that sources the library path (lib vs. lib64) from
> the compiler rather than from uname(1).
> 
> Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
> ---
>  ...cross-compilation-for-32-bit-targets.patch | 37 +++++++++++++++++++
>  1 file changed, 37 insertions(+)
>  create mode 100644 package/libbpf/1.0.1/0001-Makefile-Fix-cross-compilation-for-32-bit-targets.patch

Thanks, applied with a rework commit log:

    package/libbpf: install in the correct lib directory
    
    The libbpf build system currently uses the output of "uname -m" to
    determine if the library should be installed in "lib" or
    "lib64". However, uname -m returns the architecture of the build
    machine, which often has nothing to do with the target CPU
    architecture.
    
    A patch has been submitted and accepted upstream to address this
    issue, by using the $(CC) -dumpmachine output instead. This ensures
    libbpf is installed in either "lib" or "lib64" depending on the
    bitness of the target CPU architecture.
    
    Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

The patch was also moved away from the version-specific directory, and
the upstream status of the patch was added in the patch itself.

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

  parent reply	other threads:[~2022-10-27  6:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 14:14 [Buildroot] [PATCH 0/4] package/kmemd: new package Tobias Waldekranz
2022-10-20 14:14 ` [Buildroot] [PATCH 1/4] package/libbpf: fix cross compilation for 32-bit targets Tobias Waldekranz
2022-10-26 20:00   ` Thomas Petazzoni via buildroot
2022-10-26 20:59     ` Tobias Waldekranz
2022-10-26 21:28     ` Thomas Petazzoni via buildroot
2022-10-27  6:46   ` Thomas Petazzoni via buildroot [this message]
2022-10-20 14:14 ` [Buildroot] [PATCH 2/4] package/libbpf: remove architecture restrictions Tobias Waldekranz
2022-10-26 20:10   ` Thomas Petazzoni via buildroot
2022-10-20 14:14 ` [Buildroot] [PATCH 3/4] package/libbpf: extract dependencies to separate kconfig symbol Tobias Waldekranz
2022-10-26 20:15   ` Thomas Petazzoni via buildroot
2022-10-26 21:14     ` Tobias Waldekranz
2022-10-26 22:19       ` Thomas Petazzoni via buildroot
2022-10-20 14:14 ` [Buildroot] [PATCH 4/4] package/kmemd: new package Tobias Waldekranz
2022-10-27  6:49   ` Thomas Petazzoni via buildroot
2022-10-27 20:27     ` Tobias Waldekranz
2022-10-27 21:32       ` Thomas Petazzoni 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=20221027084619.67b393b2@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tobias@waldekranz.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