This is 9.1.1845. I am now seeing some annoying spam at the beginning of the make
step that I've never seen before, having to do with wayland:
Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src && make first
make[1]: Entering directory '/opt/bld/vim/src'
/bin/sh install-sh -c -d objects
CC="gcc -Iproto -DHAVE_CONFIG_H -I/usr/include/x86_64-linux-gnu " srcdir=. sh ./osdef.sh
cd auto/wayland; make
cd auto/wayland; make
cd auto/wayland; make
cd auto/wayland; make
make[2]: Entering directory '/opt/bld/vim/src/auto/wayland'
wayland-scanner private-code protocols/ext-data-control-v1.xml ext-data-control-v1.c
make[2]: Entering directory '/opt/bld/vim/src/auto/wayland'
wayland-scanner private-code protocols/ext-data-control-v1.xml ext-data-control-v1.c
make[2]: Entering directory '/opt/bld/vim/src/auto/wayland'
wayland-scanner private-code protocols/ext-data-control-v1.xml ext-data-control-v1.c
make[2]: Entering directory '/opt/bld/vim/src/auto/wayland'
wayland-scanner private-code protocols/ext-data-control-v1.xml ext-data-control-v1.c
creating auto/pathdef.c
wayland-scanner private-code protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.c
wayland-scanner private-code protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.c
wayland-scanner private-code protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.c
wayland-scanner private-code protocols/wlr-data-control-unstable-v1.xml wlr-data-control-unstable-v1.c
wayland-scanner private-code protocols/wlr-data-control-unstable-v1.xml wlr-data-control-unstable-v1.c
touch objects/.dirstamp
wayland-scanner private-code protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.c
wayland-scanner private-code protocols/wlr-data-control-unstable-v1.xml wlr-data-control-unstable-v1.c
wayland-scanner private-code protocols/xdg-shell.xml xdg-shell.c
wayland-scanner private-code protocols/xdg-shell.xml xdg-shell.c
wayland-scanner private-code protocols/xdg-shell.xml xdg-shell.c
wayland-scanner client-header protocols/ext-data-control-v1.xml ext-data-control-v1.h
wayland-scanner client-header protocols/ext-data-control-v1.xml ext-data-control-v1.h
wayland-scanner private-code protocols/xdg-shell.xml xdg-shell.c
wayland-scanner client-header protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.h
wayland-scanner client-header protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.h
wayland-scanner client-header protocols/wlr-data-control-unstable-v1.xml wlr-data-control-unstable-v1.h
wayland-scanner client-header protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.h
wayland-scanner client-header protocols/ext-data-control-v1.xml ext-data-control-v1.h
wayland-scanner client-header protocols/wlr-data-control-unstable-v1.xml wlr-data-control-unstable-v1.h
cd xxd; CC="gcc" CFLAGS=" -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1" LDFLAGS="-L/usr/local/lib -Wl,--as-needed" \
make -f Makefile
wayland-scanner client-header protocols/wlr-data-control-unstable-v1.xml wlr-data-control-unstable-v1.h
wayland-scanner client-header protocols/primary-selection-unstable-v1.xml primary-selection-unstable-v1.h
wayland-scanner client-header protocols/xdg-shell.xml xdg-shell.h
make[2]: Entering directory '/opt/bld/vim/src/xxd'
gcc -g -O2 -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -L/usr/local/lib -Wl,--as-needed -DUNIX -o xxd xxd.c
wayland-scanner client-header protocols/xdg-shell.xml xdg-shell.h
wayland-scanner client-header protocols/xdg-shell.xml xdg-shell.h
wayland-scanner client-header protocols/xdg-shell.xml xdg-shell.h
make[2]: Leaving directory '/opt/bld/vim/src/auto/wayland'
make[2]: Leaving directory '/opt/bld/vim/src/auto/wayland'
make[2]: Leaving directory '/opt/bld/vim/src/auto/wayland'
make[2]: Leaving directory '/opt/bld/vim/src/auto/wayland'
Is there a way this can be made to go away (without silencing all the usual make output?
I didn't expect a verbose accounting of all the cd
ing that is done having to do with wayland.
9.1.1845
Linux Mint 21
Terminal:kitty
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
I don't think this is new. Wayland dependencies have been there for a while now. I am afraid that won't got away.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
They've been there for a while, but the spam is new.
Also, in the effort to make it go away, I passed --without-wayland
to configure
, and the build failed in the make
phase:
Starting make in the src directory.
If there are problems, cd to the src directory and run make there
cd src && make first
make[1]: Entering directory '/opt/bld/vim/src'
/bin/sh install-sh -c -d objects
CC="gcc -Iproto -DHAVE_CONFIG_H -I/usr/include/x86_64-linux-gnu " srcdir=. sh ./osdef.sh
make[1]: *** No rule to make target 'auto/wayland/wlr-data-control-unstable-v1.c', needed by 'auto/wayland/wlr-data-control-unstable-v1.h'. Stop.
make[1]: *** Waiting for unfinished jobs....
touch objects/.dirstamp
make[1]: Leaving directory '/opt/bld/vim/src'
make: *** [Makefile:29: first] Error 2
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Closed #18536 as completed via 1201afb.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Thanks, --without-wayland
works now. I'm glad to have this flag!
Question: I found that, in order to make ldd $path_to_my_vim
show no compiled dependency on wayland, I also had to pass --disable-wayland-focus-steal
. It's a bit surprising that --without-wayland
didn't accomplish this all by itself. Is it supposed to work like this?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
I believe that spam from wayland-scanner is only when make
is run with parallel jobs (-j
).
Question: I found that, in order to make ldd $path_to_my_vim show no compiled dependency on wayland, I also had to pass --disable-wayland-focus-steal. It's a bit surprising that --without-wayland didn't accomplish this all by itself. Is it supposed to work like this?
Can't reproduce, maybe its some quirk with the configure script?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.