On 09/18/2014 05:18 AM, Kenneth Harrison wrote: > On Wed, Sep 17, 2014 at 7:17 PM, Armin K. <[email protected]> wrote: >> 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. >> >> >> -- >> http://lists.linuxfromscratch.org/listinfo/blfs-dev >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page >> > > I'm at a loss myself Armin. I can't get a readout as I forgot to > generate a log file, but here is the error as I saved it to a text > file in my host system while I complete my build in chroot to an > extent: > > "/bin/bash: no: command not found" > > I checked everything several times, but apparently from the Ubuntu as > listed here: > > http://ubuntuforums.org/showthread.php?t=962233 > > it was a call to something installed by Mono for some type of purpose > by the Makefile I'm guessing from the Ubuntu post. It could be a > something C or XML related as you said, but outside of that, I'm at a > loss. I thought at first it was a missing binary from coreutils or > util-linux but there wasn't a binary named "no" for either, so I did > some research and it pointed me to installing Mono. Wasn't Mono > excluded from the book some time ago and relisted as something > entirely as optional? > > >
Well, if mono provides a "no" program then it may work. However, I suspect that configure looked for some other binary and didn't find it and set its value to "no" which it should not be doing. If you ever get to reproduce the error, I'd like to see a build log. -- 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
