From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/libdisplay-info: new package
Date: Sun, 18 Jun 2023 18:25:25 +0200 [thread overview]
Message-ID: <20230618162525.GB2754@scaer> (raw)
In-Reply-To: <20230507142319.1001150-2-bernd.kuhls@t-online.de>
Bernd, All,
On 2023-05-07 16:23 +0200, Bernd Kuhls spake thusly:
> Needed for upcoming Kodi version 21.0-Omega.
> Depends on the previous patch to enable staging install of hwdata.
>
> Disable -fPIC on BR2_m68k_cf to avoid build failure:
>
> /tmp/ccgMh4YA.s: Assembler messages:
> /tmp/ccgMh4YA.s: Fatal error: Tried to convert PC relative branch to absolute jump
>
> For details see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101971#c11
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
[--SNIP--]
> diff --git a/package/libdisplay-info/0001-displayid.c-Include-sys-types.h.patch b/package/libdisplay-info/0001-displayid.c-Include-sys-types.h.patch
> new file mode 100644
> index 0000000000..334b786fff
> --- /dev/null
> +++ b/package/libdisplay-info/0001-displayid.c-Include-sys-types.h.patch
> @@ -0,0 +1,36 @@
> +From 648c1cb66b571b037976b61363654f39448f5fac Mon Sep 17 00:00:00 2001
> +From: Bernd Kuhls <bernd.kuhls@t-online.de>
> +Date: Sun, 7 May 2023 14:14:48 +0200
> +Subject: [PATCH] displayid.c: Include sys/types.h
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +Fixes build error
> +../displayid.c:377:10: error: ‘ssize_t’ undeclared (first use in this function); did you mean ‘size_t’?
> +
> +seen with:
> +arc-linux-gcc.br_real (Buildroot 2021.11-4428-g6b6741b) 10.2.0
> +
> +Upstream: https://gitlab.freedesktop.org/emersion/libdisplay-info/-/merge_requests/163
This has now been merged, good! So, when you respin, please update to
use a pointer to the actual commit, not the MR. Thanks!
[--SNIP--]
> diff --git a/package/libdisplay-info/libdisplay-info.mk b/package/libdisplay-info/libdisplay-info.mk
> new file mode 100644
> index 0000000000..d11f682a5a
> --- /dev/null
> +++ b/package/libdisplay-info/libdisplay-info.mk
> @@ -0,0 +1,24 @@
> +################################################################################
> +#
> +# libdisplay-info
> +#
> +################################################################################
> +
> +LIBDISPLAY_INFO_VERSION = 0.1.1
> +LIBDISPLAY_INFO_SOURCE = libdisplay-info-$(LIBDISPLAY_INFO_VERSION).tar.bz2
> +LIBDISPLAY_INFO_SITE = https://gitlab.freedesktop.org/emersion/libdisplay-info/-/archive/$(LIBDISPLAY_INFO_VERSION)
> +LIBDISPLAY_INFO_LICENSE = MIT
> +LIBDISPLAY_INFO_LICENSE_FILES = LICENSE
> +LIBDISPLAY_INFO_INSTALL_STAGING = YES
> +LIBDISPLAY_INFO_DEPENDENCIES = hwdata
> +
> +# workaround for static_assert on uclibc-ng < 1.0.42
> +LIBDISPLAY_INFO_CFLAGS += $(TARGET_CFLAGS) -Dstatic_assert=_Static_assert
So what happens with toolchains using uclibc-ng >= 1.0.42 ?
> +# m68k_cf can't use meson's default -fPIC, so we need to disable it to
> +# avoid a build failure.
> +ifeq ($(BR2_m68k_cf),y)
> +LIBDISPLAY_INFO_CONF_OPTS += -Db_staticpic=false
If static+PIC is really borked on coldfire, then we should do that for
all packages, not just libdisplay-info, no?
If so, then it should go into the meson-package infra, i.e. in
package/pkg-meson.mk around line 158.
Regards,
Yann E. MORIN.
> +endif
> +
> +$(eval $(meson-package))
> --
> 2.39.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-18 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 14:23 [Buildroot] [PATCH 1/2] package/hwdata: install to staging Bernd Kuhls
2023-05-07 14:23 ` [Buildroot] [PATCH 2/2] package/libdisplay-info: new package Bernd Kuhls
2023-06-18 16:25 ` Yann E. MORIN [this message]
[not found] ` <20230618162525.GB2754__2479.91979574493$1687105555$gmane$org@scaer>
2023-06-18 18:34 ` Bernd Kuhls
2023-06-18 16:20 ` [Buildroot] [PATCH 1/2] package/hwdata: install to staging Yann E. MORIN
2023-07-06 10:50 ` 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=20230618162525.GB2754@scaer \
--to=yann.morin.1998@free.fr \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
/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