On Tue, Dec 11, 2018, 9:26 AM Bruce Dubbs via blfs-dev <
blfs-dev@lists.linuxfromscratch.org wrote:
> On 12/11/2018 03:33 AM, Wayne Blaszczyk wrote:
> > On Mon, 2018-12-10 at 15:08 -0600, Bruce Dubbs via blfs-dev wrote:
> >> I'm trying to update to gtk+-3.24.1, but can't complete the build.
> >>
> >> I am using:
> >>
> >> ./configure --prefix=/usr \
> >> --sysconfdir=/etc \
> >> --enable-broadway-backend \
> >> --enable-x11-backend \
> >> --disable-wayland-backend &&
> >> #--enable-wayland-backend \
> >>
> >> make -j4 &&
> >> sudo make install
> >>
> >> Configure and make complete OK, but the install give me (slightly
> >> formatted for clarity):
> >>
> >> /bin/sh /tmp/gtk3/gtk+-3.24.1/build-aux/install-sh \
> >> -d /usr/lib/gtk-3.0/3.0.0
> >>
> >> ../../gtk/gtk-query-immodules-3.0 >
> >> /usr/lib/gtk-3.0/3.0.0/immodules.cache
> >>
> >> Cannot load module /usr/lib/gtk-3.0/3.0.0/immodules/im-ibus.so:
> >> /usr/lib/gtk-3.0/3.0.0/immodules/im-ibus.so:
> >> undefined symbol: gdk_wayland_display_get_type
> >>
> >> /usr/lib/gtk-3.0/3.0.0/immodules/im-ibus.so does not export GTK+ IM
> >> module API: /usr/lib/gtk-3.0/3.0.0/immodules/im-ibus.so:
> >> undefined symbol: gdk_wayland_display_get_type
> >>
> >> Cannot load module /usr/lib/gtk-3.0/3.0.0/immodules/im-wayland.so:
> >> /usr/lib/gtk-3.0/3.0.0/immodules/im-wayland.so:
> >> undefined symbol: gdk_wayland_seat_get_wl_seat
> >>
> >> /usr/lib/gtk-3.0/3.0.0/immodules/im-wayland.so does not export GTK+ IM
> >> module API: /usr/lib/gtk-3.0/3.0.0/immodules/im-wayland.so:
> >> undefined symbol: gdk_wayland_seat_get_wl_seat
> >>
> >> I did go back and redo the package with --enable-wayland-backend and it
> >> completed OK. We probably will want to change the Command Explanation
> >> for --enable-wayland-backend and promote the two wayland dependencies to
> >> required.
> >
> > I assume you had wayland installed already when you got the above errors
> as
> > you did not mention anything about installing wayland afterwards.
>
> Correct.
>
> I would
> > say that the above errors is caused by a previous gtk+ and possibly ibus
> > being installed that were somehow built with wayland.
>
> Possibly. I definitely had wayland{,-protocols} installed when I built
> gtk+.
>
> > I build everything with wayland, but I can reproduce the error above.
> > By blowing away /usr/lib/gtk-3.0 fixes the above build (without wayland).
>
> Thanks for your help. I suppose a note about --disable-wayland-backend
> not working if gtk3 is built when wayland is present would be
> appropriate. The only reason I tried building without is because my
> current script had it and I don't use wayland. I do build wayland for
> mesa which says wayland is needed for plasma and is recommended.
>
> I've added the note in my sandbox and it will be in my next commit.
>
> -- Bruce
> --
> http://lists.linuxfromscratch.org/listinfo/blfs-dev
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
Why don't we make Wayland support recommended? It would remove a difference
between books, and it's only a matter of time before GTK applications that
are NOT using Wayland are ported to do so.
Note that when updating GNOME, I do test on sysv - but I do build with
wayland support. I couldn't tell you whether or not they actually need it.
>
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
