mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] wayland: version bump 1.19.0 -> 1.20.0
Date: Fri, 17 Dec 2021 11:53:40 +0100	[thread overview]
Message-ID: <YbxsNOu5Kg4I84DI@pengutronix.de> (raw)
In-Reply-To: <20211210101545.1763794-1-p.zabel@pengutronix.de>

With this applied I get this error in my test builds:

FAILED: bin/wflinfo
: && [...]/arm-v7a-linux-gnueabihf-gcc --std=c99 -Wall -Werror=implicit-function-declaration -fvisibility=hidden -Werror=incompatible-pointer-types -Werror=int-conversion -Werror=missing-prototypes -O2 -g -DNDEBUG -rdynamic
src/utils/CMakeFiles/wflinfo.dir/wflinfo.c.o -o bin/wflinfo  -Wl,-rpath,i[...]/build-target/waffle-1.7.0-build/lib:  lib/libwaffle-1.so.0.7.0 && :
[...]/arm-v7a-linux-gnueabihf/bin/ld: lib/libwaffle-1.so.0.7.0: undefined reference to `wl_proxy_marshal_flags'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
make: *** [[...]/rules/post/ptxd_make_world_compile.make:19: [...]/state/waffle.compile] Error 1

Do you have an idea what happens here?

Michael

On Fri, Dec 10, 2021 at 11:15:45AM +0100, Philipp Zabel wrote:
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
>  rules/wayland.make | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/rules/wayland.make b/rules/wayland.make
> index b237a97016ff..72d1f367bdd5 100644
> --- a/rules/wayland.make
> +++ b/rules/wayland.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_WAYLAND) += wayland
>  #
>  # Paths and names
>  #
> -WAYLAND_VERSION	:= 1.19.0
> -WAYLAND_MD5	:= 5d59ac3d8a8f4e42de2ceb8bb19dfca9
> +WAYLAND_VERSION	:= 1.20.0
> +WAYLAND_MD5	:= 5095264157bf0565b921ceaf9d698d98
>  WAYLAND		:= wayland-$(WAYLAND_VERSION)
>  WAYLAND_SUFFIX	:= tar.xz
>  WAYLAND_URL	:= http://wayland.freedesktop.org/releases/$(WAYLAND).$(WAYLAND_SUFFIX)
> @@ -41,7 +41,8 @@ WAYLAND_CONF_OPT	:= \
>  	-Ddtd_validation=false \
>  	-Dicon_directory= \
>  	-Dlibraries=true \
> -	-Dscanner=true
> +	-Dscanner=true \
> +	-Dtests=false
>  
>  # ----------------------------------------------------------------------------
>  # Install
> -- 
> 2.30.2
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


  reply	other threads:[~2021-12-17 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 10:15 Philipp Zabel
2021-12-17 10:53 ` Michael Olbrich [this message]
2021-12-17 11:24   ` Philipp Zabel
2022-01-06  9:33   ` Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich

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=YbxsNOu5Kg4I84DI@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=p.zabel@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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