From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/sunxi-mali: remove sunxi-mali r2p4 kernel module
Date: Mon, 20 Feb 2017 22:52:43 +0100 [thread overview]
Message-ID: <20170220225243.7970a7b3@free-electrons.com> (raw)
In-Reply-To: <20170218145258.10213-2-romain.naour@gmail.com>
Hello,
On Sat, 18 Feb 2017 15:52:58 +0100, Romain Naour wrote:
> sunxi-mali r2p4 kernel module are linked against libUMP.so.2 but libump
A kernel module cannot be linked against a userspace shared library, so
the commit title and this description do not make sense. Perhaps you're
talking about the libGLES library?
> package in Buildroot only provide libUMP.so.3, see [1].
>
> ./r2p4/armhf/x11/libGLESv2.so.2.0
> ./r2p4/armhf/x11/libMali.so
> - 0x00000001 (NEEDED) Shared library: [libUMP.so]
> + 0x00000001 (NEEDED) Shared library: [libUMP.so.2]
> ./r2p4/armhf/x11/libGLESv1_CM.so.1.1
> ./r2p4/armhf/x11/libEGL.so.1.4
> 0x00000001 (NEEDED) Shared library: [libX11.so.6]
> 0x00000001 (NEEDED) Shared library: [libdrm.so.2]
> 0x00000001 (NEEDED) Shared library: [libXfixes.so.3]
> 0x00000001 (NEEDED) Shared library: [libXext.so.6]
> ./r2p4/armel/framebuffer/libGLESv2.so
> ./r2p4/armel/framebuffer/libMali.so
> - 0x00000001 (NEEDED) Shared library: [libUMP.so]
> + 0x00000001 (NEEDED) Shared library: [libUMP.so.2]
> + sunxi-mali r2p4 has been removed since libump package only
> + provide libUMP.so.3 for r3p0 and r3p1 mali kernel module.
kernel module ?
> + r2p4 for ARM EABI systems require libUMP.so.2.
> +
> config BR2_PACKAGE_PERL_DB_FILE
> bool "perl-db-file removed"
> select BR2_LEGACY
> diff --git a/package/sunxi-mali/Config.in b/package/sunxi-mali/Config.in
> index c6754c2..951007a 100644
> --- a/package/sunxi-mali/Config.in
> +++ b/package/sunxi-mali/Config.in
> @@ -1,6 +1,10 @@
> config BR2_PACKAGE_SUNXI_MALI
> bool "sunxi-mali"
> depends on BR2_arm
> + # libump package only provide libUMP.so.3 for r3p0 and r3p1
> + # mali kernel module. r2p4 for ARM EABI systems require
kernel module ?
> -comment "sunxi-mali needs a glibc toolchain"
> +comment "sunxi-mali needs a glibc toolchain w/ armhf enabled"
Please use:
needs an EABIhf glibc toolchain
instead.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-20 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 14:52 [Buildroot] [PATCH 1/2] package/sunxi-mali: reorder select/depends Romain Naour
2017-02-18 14:52 ` [Buildroot] [PATCH 2/2] package/sunxi-mali: remove sunxi-mali r2p4 kernel module Romain Naour
2017-02-18 15:05 ` Yann E. MORIN
2017-02-18 15:16 ` Romain Naour
2017-02-20 21:52 ` Thomas Petazzoni [this message]
2017-02-20 22:33 ` Romain Naour
2017-02-20 21:50 ` [Buildroot] [PATCH 1/2] package/sunxi-mali: reorder select/depends Thomas Petazzoni
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=20170220225243.7970a7b3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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