Murray, It looks like I was confused by the version labeling. I was able to compile libgda (upstream version) but without libcrypto support. I filed a bug for that. I am trying to compile libgdamm using jhbuild but always receive: configure: error: Package requirements (glibmm-2.54 >= 2.45.31 libgda- 6.0 >= 5.0.2) were not met:
No package 'glibmm-2.54' found I just found that default branch is not master. Thus, I can't get the recent version. I am working on this case and will let you know if I have any problem. Thanks. On Thu, 2017-04-27 at 22:24 +0200, Murray Cumming wrote: > On Thu, 2017-04-27 at 14:08 -0500, Pavlo Solntsev wrote: > > Thanks. > > > > For me it is confused to see one version in the file name and > > another > > inside. > > I'm sorry. I don't understand. What change are you suggesting? Maybe > a > patch would make that clearer. Thanks. > > > Murray Cumming > murr...@murrayc.com > www.murrayc.com > -- - Pavlo Solntsev --------------------------------------------- Sent from Evolution on GNU/Debian <www.debian.org> id="-x-evo- selection-start-marker"> _______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
