I already mentioned what to do. Maybe I was unclear. Just do jhbuild build evince --start-at=gtk+
On Tue 04 Feb 2014 06:09:02 PM EST, Piyush Goel wrote: > Hey, > I gave up on the module spi2 using option 3 and got the following at > the end > > *** module evince not built due to non buildable gtk+ *** [23/23] > *** module evince not built due to non buildable gnome-icon-theme *** > [23/23] > *** the following modules were not built *** [23/23] > at-spi2-atk gtk+ gnome-icon-theme evince > > What should I do? > > > > On Tue, Feb 4, 2014 at 11:18 PM, Germán Póo-Caamaño <[email protected] > <mailto:[email protected]>> wrote: > > On Tue, 2014-02-04 at 10:37 -0500, Hashem Nasarat wrote: > > I was having trouble building this module recently too. Perhaps > > something is broken in at-spi2-core. > > Until that gets fixed, you can skip (option 3) building the module, > > note what module is being built immediately after, then Ctrl-C > out of > > jhbuild then do something like: > > jhbuild build evince --start-at=module-after-at-spi2-core > > A better solution could be fallback to a stable version of > at-spi2-core. > > For example, in your .jhbuildrc: > > branches['at-spi2-core'] = (None, 'gnome-3-8') > > See > https://developer.gnome.org/jhbuild/stable/config-reference.html for > further reference. > > In addition, it would be nice to let the at-spi2 developers know about > the issue. > > -- > Germán Poo-Caamaño > http://calcifer.org/ > > > > > -- > Regards, > > Piyush Goel > Information Technology 2011-2015|NSIT,Delhi > Ph: +91 9891006457 _______________________________________________ evince-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/evince-list
