On 09/18/2014 04:11 AM, Kenneth Harrison wrote: > I recently attempted to build GTK+3.12.2 under the classic BLFS book > with Wayland support, following examples from the BLFS-systemd book > with librest as well as a dependency. > > Nothing wrong happened during the configure stage but during the build > phase for Wayland's backend, a gdk header tried to work off using > "/bin/sh: no" as a command or sequence during compile and errored out. >
A full output when the error occours could be useful. > I did some research and found through a post at Ubuntu forums that I > needed to install mono as a package as for some reason Wayland's > backend code expected it during build time. I also had to install > libgdiplus as a required dependency for mono. > That makes no sense at all. GTK+ has and never will depend on Mono. GTK+ wayland code may only depend on wayland-scanner for generating C code from XML interafaces or something like that. > After installing these packages, reconfiguring the build, and > re-attempting the build it worked and the package installed > successfully without issue. > > Has anyone else had any errors during building GTK+-3.x in the > non-systemd book and attempting to use Wayland as well, and should > libgdiplus and mono be listed as possible dependencies for GTK+-3.x > when attempting to build with Wayland support? > Yes and no. Wayland itself is a library and is not init system specific. And there isn't a single reference to mono in GTK+ codebase as far as I know. > Also will the BLFS classic book be updated to show support for Wayland > and such components for sysvinit as the KDE Desktop possibly can use > them as the systemd BLFS book has shown? > > Thanks, > Jim > -- Note: My last name is not Krejzi.
signature.asc
Description: OpenPGP digital signature
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
