Re: final gtk+maverick battles
On 02/17/2014 05:05 AM, Bric wrote: FWIF: with this drive to keep upgrading, I just lost a critical hour of sleep (I start new class material today and needed to be rested) because I messed up the one and only thing you should NEVER mess up in your system: network (wifi) connection (if you are out and about and have no way of plugging into ethernet): With my eye on the 14.04 prize, I checked unsupported and pre-release packages in Update Manager, so it went ahead and installed newer linux-firmware, which screwed up my wifi connection. Luckily, I was still near an ethernet port, and downgraded. Again, just a caveat/caution for anyone who might try to draw from this experience. Years ago I was trying to install software that required a newer libc than I had, so I naively tried to uninstall glibc. (Redhat 5.1 I think.) Needless to say that didn't work too well and I had reinstall. Also I had a friend running Gentoo who decided she didn't want python, so she tried to uninstall it. Needless to say, she too reinstalled. ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On 02/16/2014 10:24 PM, Michael Torrie wrote: On 02/16/2014 04:30 AM, Bric wrote: Nonetheless, I run ./configure in gtk+ git, and I am still getting unmet dependencies: configure: error: Package requirements (glib-2.0 = 2.39.5atk = 2.7.5pango = 1.32.4cairo = 1.12.0 cairo-gobject = 1.12.0 gdk-pixbuf-2.0 = 2.27.1) were not met: Requested 'glib-2.0 = 2.39.5' but version of GLib is 2.32.4 Requested 'atk = 2.7.5' but version of Atk is 2.4.0 Requested 'pango = 1.32.4' but version of Pango is 1.30.0 Requested 'gdk-pixbuf-2.0 = 2.27.1' but version of GdkPixbuf is 2.26.1 So, this is no longer an ancient system. What do I do? (Aside from trashing this new one with local builds, as I did the old one?) Never upgrade system versions of glib and gtk+ in place unless you really know what you're doing. Instead if you need newer versions, compile them to their own prefix. You can set the PKG_CONFIG_PATH variable to point to that prefix and ./configure will see them. Also you can use jhbuild (google for it) to build the latest versions of gtk+ to its own prefix (say /opt/gtk3). Thank you. If you dislike Unity, you can install the mate-desktop, which is a continuation of the old gnome2 desktop that you are used to. I do dislike Unity. But I somehow managed to pull gnome back into my new install, so currently, i am using gnome (you are prompted to choose among several options, on boot) To D. Marceau: I'm going to take a chance and not back up everything. I don't have space to back up all my stuff right now. One would think that, after years of developing system installs, Ubuntu won't do me in (outside of my clicking erase everything... during the install because I'm going on two hours of sleep or something) (Word of caution to others: the installer wipes out stuff in /usr and /etc, so, for example, I lost a painstakingly developed xkb configuration file ... painful to no end...) I think I have to switch a couple of settings in update-manager, no? Like, broaden the upgrade option to all systems, rather just to long-term versions. Will be rebooting and re-probing shortly. I made the mistake the first time around of NOT selecting download packages... during the install. (I had to upgrade from the CD). I am assuming that would have made the installer better match whatever I already had, with remote repositories, rather than simply getting rid of packages it couldn't match with the CD installer. (It's a pain having to reconstruct everything it wiped out!) To A. Cottrell: You are probably right; I should have tried gtk+ 3.0.12 or some such. I wonder if that would have worked with the old system. And, of course, you are right about not messing with glib - i had a vague memory of installing gtk+ on a fedora, years ago, and the memory didn't involve system trashing, or any risk thereof. So... that's what you get when you rely on old, vague memories - the world of linux libraries has been moving on rapidly :-)) ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On 02/17/2014 04:30 AM, Bric wrote: On 02/16/2014 10:24 PM, Michael Torrie wrote: On 02/16/2014 04:30 AM, Bric wrote: Nonetheless, I run ./configure in gtk+ git, and I am still getting unmet dependencies: configure: error: Package requirements (glib-2.0 = 2.39.5atk = 2.7.5pango = 1.32.4cairo = 1.12.0 cairo-gobject = 1.12.0 gdk-pixbuf-2.0 = 2.27.1) were not met: Requested 'glib-2.0 = 2.39.5' but version of GLib is 2.32.4 Requested 'atk = 2.7.5' but version of Atk is 2.4.0 Requested 'pango = 1.32.4' but version of Pango is 1.30.0 Requested 'gdk-pixbuf-2.0 = 2.27.1' but version of GdkPixbuf is 2.26.1 So, this is no longer an ancient system. What do I do? (Aside from trashing this new one with local builds, as I did the old one?) Never upgrade system versions of glib and gtk+ in place unless you really know what you're doing. Instead if you need newer versions, compile them to their own prefix. You can set the PKG_CONFIG_PATH variable to point to that prefix and ./configure will see them. Also you can use jhbuild (google for it) to build the latest versions of gtk+ to its own prefix (say /opt/gtk3). Thank you. If you dislike Unity, you can install the mate-desktop, which is a continuation of the old gnome2 desktop that you are used to. I do dislike Unity. But I somehow managed to pull gnome back into my new install, so currently, i am using gnome (you are prompted to choose among several options, on boot) To D. Marceau: I'm going to take a chance and not back up everything. I don't have space to back up all my stuff right now. One would think that, after years of developing system installs, Ubuntu won't do me in (outside of my clicking erase everything... during the install because I'm going on two hours of sleep or something) (Word of caution to others: the installer wipes out stuff in /usr and /etc, so, for example, I lost a painstakingly developed xkb configuration file ... painful to no end...) I think I have to switch a couple of settings in update-manager, no? Like, broaden the upgrade option to all systems, rather just to long-term versions. Will be rebooting and re-probing shortly. I made the mistake the first time around of NOT selecting download packages... during the install. (I had to upgrade from the CD). I am assuming that would have made the installer better match whatever I already had, with remote repositories, rather than simply getting rid of packages it couldn't match with the CD installer. (It's a pain having to reconstruct everything it wiped out!) To A. Cottrell: You are probably right; I should have tried gtk+ 3.0.12 or some such. I wonder if that would have worked with the old system. And, of course, you are right about not messing with glib - i had a vague memory of installing gtk+ on a fedora, years ago, and the memory didn't involve system trashing, or any risk thereof. So... that's what you get when you rely on old, vague memories - the world of linux libraries has been moving on rapidly :-)) FWIF: with this drive to keep upgrading, I just lost a critical hour of sleep (I start new class material today and needed to be rested) because I messed up the one and only thing you should NEVER mess up in your system: network (wifi) connection (if you are out and about and have no way of plugging into ethernet): With my eye on the 14.04 prize, I checked unsupported and pre-release packages in Update Manager, so it went ahead and installed newer linux-firmware, which screwed up my wifi connection. Luckily, I was still near an ethernet port, and downgraded. Again, just a caveat/caution for anyone who might try to draw from this experience. ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On Mon, Feb 17, 2014 at 11:05 PM, Bric b...@flight.us wrote: FWIF: with this drive to keep upgrading, I just lost a critical hour of sleep (I start new class material today and needed to be rested) because I messed up the one and only thing you should NEVER mess up in your system: network (wifi) connection (if you are out and about and have no way of plugging into ethernet): With my eye on the 14.04 prize, I checked unsupported and pre-release packages in Update Manager, so it went ahead and installed newer linux-firmware, which screwed up my wifi connection. Luckily, I was still near an ethernet port, and downgraded. Again, just a caveat/caution for anyone who might try to draw from this experience. Hey, it's a lot easier than back when I first started playing with networking, in the 1990s. Granted, it was normal then to install off a CD, but on the flip side, it was normal to need to get specific drivers for your actual card. We got to know a few reliable cards (Realtek network cards, ET6000 video cards, and such) that would always work with our beloved OS/2, and if anything went wrong, I'd go to my stash and grab one. Otherwise, it was a matter of transfer by floppy disk, or pulling out the LinkWiz cable and moving data through the computers' parallel ports. (Or their serial ports, if we didn't feel like unplugging the ol' noisy. So much slower that way, even though LinkWiz would (ab)use quite a few of the pins for extra data.) These days, the face-palm DOH! moment usually comes from ssh'ing to a box and then ifconfigging the network interface down. Yeah, that one gets annoying. ChrisA ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On Sun, Feb 16, 2014 at 10:30 PM, Bric b...@flight.us wrote: (Unity completely and majorly sucks, by the way. And the upgrade has wiped out major settings, like /etc/bash.bashrc (!??), gnome panels, and lots more!) Unrelated to your main issues, but I'll put in a plug for Xfce. When Ubuntu went to Unity, I jumped to Debian, which was using GNOME 2. When Debian upgraded to GNOME 3, I switched to Xfce, and that's where I'm now happy (Debian Wheezy or Jessie with Xfce). You can probably just 'sudo apt-get install xfce' or similar, or you can download Xubuntu which uses it by default. ChrisA ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On 02/16/2014 06:30 AM, Bric wrote: My old system was, indeed, trashed. An accidental re-boot proved that it wasn't going into GUI mode anymore. Thus, I upgraded, and am now on Ubuntu 12. Now upgrade a few more times to get to trusty(14.04) to get the latest bells and whistles. Then there are recipes to get trusty with the latest GNOME available through some extra ppa's repositories. Then you can install proprietary graphics display drivers as final step. HINT: BE PATIENT. Never reboot or control-C during the install/upgrade. Just let it do its thing. One of the slowest parts of the install/upgrade is always the graphics chipset hardware identification and resolution capability testing. That's why it takes so long and especially on older hardware. It will flicker a lot. Just wait until it settles on a certain resolution or it comes back on its own to the text-mode console. Go for a coffee or something. HINT: BE PATIENT. There are possibly disk error checks done when upgrading which also cause for slower bootup sequences. Don't reboot or control-C. Just let it do its thing. Installing proprietary drivers for nvidia/ati are always the culprits for the gui display manager failing. Remove the proprietary display drivers for now. From the command-line, upgrade to 13.04, 13.10, and finally to 14.04. Expect a 6-8 hours for each upgrade to complete so it will probably take you a good 3 days to finish if you take a day for each of these version jumps. When you're done all the upgrading, then you may install the proprietary drivers for nvidia/ati to your heart's content. That will take another hour to download and install. Once all this is done, you'll be up-to-date and your current issues will be resolved. Cheers, David Marceau ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On Sun, 16 Feb 2014, Bric wrote: On 02/14/2014 02:54 PM, Chris Angelico wrote: On Sat, Feb 15, 2014 at 4:52 AM, Bric b...@flight.us wrote: GTK on MacOSX requires a few dependencies to build and those script download them all and build them with clang default compiler without too many issues. https://wiki.gnome.org/action/show//Projects/GTK+/OSX/Building My old system was, indeed, trashed. An accidental re-boot proved that it wasn't going into GUI mode anymore. Thus, I upgraded, and am now on Ubuntu 12. Nonetheless, I run ./configure in gtk+ git, and I am still getting unmet dependencies [...] That should not be surprising. Why do you need the current (unstable) development version of gtk+ rather than just the latest stable release (at present, 3.10.7)? In the unstable development versions (with odd minor version numbers, such as 3.11) you have no guarantee of API or ABI stability, and you'll likely find that unstable gtk+ depends on unstable glib, pango, atk and so on. Taking this path is quite likely to bork your system again, in the sense that the GUI supplied with *buntu will stop working since it's built against a potentially incompatible gtk stack. Allin Cottrell ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On 02/16/2014 03:05 PM, Bric wrote: On 02/16/2014 10:33 AM, David Marceau wrote: On 02/16/2014 06:30 AM, Bric wrote: My old system was, indeed, trashed. An accidental re-boot proved that it wasn't going into GUI mode anymore. Thus, I upgraded, and am now on Ubuntu 12. Now upgrade a few more times to get to trusty(14.04) to get the latest bells and whistles. Then there are recipes to get trusty with the latest GNOME available through some extra ppa's repositories. Then you can install proprietary graphics display drivers as final step. Are you sure i can't fast-forward to 14.04, with just one more install ? For peace of mind, backup your personal data no matter what upgrade path you choose. It seems possible to do a one-step upgrade: http://www.liberiangeek.net/2014/01/daily-ubuntu-tips-upgrade-to-ubuntu-14-04-trusty-tahr-from-13-10/ You'll need to do a tweak along the way: http://askubuntu.com/questions/379430/upgrading-to-alpha-fails-due-extras-repositories The trick is don't be disappointed about how slow the first couple of reboots are during the upgrade and after the upgrade. These are deceptive bad first-impressions, but once the operating system settles itself out in both ubuntu and in debian, they are very snappy to boot up and shut down. Be patient especially for the first two to three reboots. Don't be overly eager to click the mouse again on the same button. The OS heard your first click, but it's very busy doing a lot of stuff in the background without you being aware of it. Just let it do its thing. Don't stop anything. Don't cancel anything. The first couple of reboots are always seemingly slow, but keep in mind it's setting up configurations for the first time, possibly preparing disk nodes for future writes, caching your most recently used applications for faster loading the next time, etc... Cheers :) David Marceau ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On 02/16/2014 04:30 AM, Bric wrote: Nonetheless, I run ./configure in gtk+ git, and I am still getting unmet dependencies: configure: error: Package requirements (glib-2.0 = 2.39.5atk = 2.7.5pango = 1.32.4cairo = 1.12.0 cairo-gobject = 1.12.0 gdk-pixbuf-2.0 = 2.27.1) were not met: Requested 'glib-2.0 = 2.39.5' but version of GLib is 2.32.4 Requested 'atk = 2.7.5' but version of Atk is 2.4.0 Requested 'pango = 1.32.4' but version of Pango is 1.30.0 Requested 'gdk-pixbuf-2.0 = 2.27.1' but version of GdkPixbuf is 2.26.1 So, this is no longer an ancient system. What do I do? (Aside from trashing this new one with local builds, as I did the old one?) Never upgrade system versions of glib and gtk+ in place unless you really know what you're doing. Instead if you need newer versions, compile them to their own prefix. You can set the PKG_CONFIG_PATH variable to point to that prefix and ./configure will see them. Also you can use jhbuild (google for it) to build the latest versions of gtk+ to its own prefix (say /opt/gtk3). If you dislike Unity, you can install the mate-desktop, which is a continuation of the old gnome2 desktop that you are used to. ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
barely compiled gcc 4.8.2 (make install first failed, then, after ldconfig, it succeeded) The upgraded gcc doesn't seem to have an effect on my gtk+ woes. (!) :-(( (unless make is still using the old gcc, but I don't see an indication of that) Same /bin/sh: --: invalid option error with the git source, but with a cleanly unpacked tarball I get a different error : http://www.flight.us//misc/gtk_compile_error2.txt Have you tried with the John Rails scripts? GTK on MacOSX requires a few dependencies to build and those script download them all and build them with clang default compiler without too many issues. https://wiki.gnome.org/action/show//Projects/GTK+/OSX/Building -- Bye, Gabry ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On 02/14/2014 10:38 AM, Gabriele Greco wrote: barely compiled gcc 4.8.2 (make install first failed, then, after ldconfig, it succeeded) The upgraded gcc doesn't seem to have an effect on my gtk+ woes. (!) :-(( (unless make is still using the old gcc, but I don't see an indication of that) Same /bin/sh: --: invalid option error with the git source, but with a cleanly unpacked tarball I get a different error : http://www.flight.us//misc/gtk_compile_error2.txt Have you tried with the John Rails scripts? GTK on MacOSX requires a few dependencies to build and those script download them all and build them with clang default compiler without too many issues. https://wiki.gnome.org/action/show//Projects/GTK+/OSX/Building Sorry, you lost me... I am on Ubuntu, not OSX. An _old_ ubuntu, at that, with lots of old packages. I have a double challenge: build something new, with new-version dependency, and avoid breaking (trashing) my old system. I can't seem to find anything concrete on John Rails scripts -- Bye, Gabry ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On Fri, 14 Feb 2014, Bric wrote: On 02/14/2014 10:38 AM, Gabriele Greco wrote: barely compiled gcc 4.8.2 (make install first failed, then, after ldconfig, it succeeded) The upgraded gcc doesn't seem to have an effect on my gtk+ woes. (!) :-(( (unless make is still using the old gcc, but I don't see an indication of that) Same /bin/sh: --: invalid option error with the git source, but with a cleanly unpacked tarball I get a different error : http://www.flight.us//misc/gtk_compile_error2.txt Have you tried with the John Rails scripts? GTK on MacOSX requires a few dependencies to build and those script download them all and build them with clang default compiler without too many issues. https://wiki.gnome.org/action/show//Projects/GTK+/OSX/Building Sorry, you lost me... I am on Ubuntu, not OSX. An _old_ ubuntu, at that, with lots of old packages. Not wanting to be snotty, but I get the impression you're out of your depth here. Why not just install a Linux distro (Ubuntu or otherwise) that has an up-to-date GTK stack? I'm afraid you're going to wear out your welcome here with How can I unbreak my system that has a horrid mess-up of old and new GLib/GTK? This is not really a gtk-app-devel question. Allin Cottrell ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On Sat, Feb 15, 2014 at 4:52 AM, Bric b...@flight.us wrote: GTK on MacOSX requires a few dependencies to build and those script download them all and build them with clang default compiler without too many issues. https://wiki.gnome.org/action/show//Projects/GTK+/OSX/Building Sorry, you lost me... I am on Ubuntu, not OSX. An _old_ ubuntu, at that, with lots of old packages. Just to explain where the confusion came from: Ubuntu 10.10 (released back in 2010 and supported until 2012) is called Maverick Meerkat or just Maverick. (Incidentally, I still have one computer running Ubuntu Maverick... and one running Karmic. Neither of them even reboots more than about once a year, tops, and that because of UPS failure; so I have no particular desire to do a full OS upgrade with consequent downtime. Even though these are only used internally, I still hate the idea of downtime.) Mac OS X 10.9 (released late 2013, and currently supported) is called Mavericks. Compilation issues on the latest OSX are not an unusual thing (Python had a few issues with GUI handling, needed a bugfix release before 10.9 could officially be called supported), so it's going to be what most people think of when you talk about GTK+Maverick issues. ChrisA ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On 02/14/2014 01:27 PM, Allin Cottrell wrote: On Fri, 14 Feb 2014, Bric wrote: On 02/14/2014 10:38 AM, Gabriele Greco wrote: barely compiled gcc 4.8.2 (make install first failed, then, after ldconfig, it succeeded) The upgraded gcc doesn't seem to have an effect on my gtk+ woes. (!) :-(( (unless make is still using the old gcc, but I don't see an indication of that) Same /bin/sh: --: invalid option error with the git source, but with a cleanly unpacked tarball I get a different error : http://www.flight.us//misc/gtk_compile_error2.txt Have you tried with the John Rails scripts? GTK on MacOSX requires a few dependencies to build and those script download them all and build them with clang default compiler without too many issues. https://wiki.gnome.org/action/show//Projects/GTK+/OSX/Building Sorry, you lost me... I am on Ubuntu, not OSX. An _old_ ubuntu, at that, with lots of old packages. Not wanting to be snotty, but I get the impression you're out of your depth here. Why not just install a Linux distro (Ubuntu or otherwise) that has an up-to-date GTK stack? I'm afraid you're going to wear out your welcome here with How can I unbreak my system that has a horrid mess-up of old and new GLib/GTK? This is not really a gtk-app-devel question. fair enough, with respect to unbreaking. But I wasn't asking Gabriele Greco to help me do that. He sounded like he had no idea about what's been happening here, so I elaborated a bit, highlighting what's critical (I couldn't possibly see how a single utility — the John Rails script he mentioned — could be useful for both OSX and an old Ubuntu! Fortunately, someone explained why he thought I was on OSX). I don't expect to pass on the extra burden/challenge to this list. Someone here gave me the courtesy of just cluing me in, that I was trashing my system by upgrading my glib and related packages. It's all new to me... the notion that I might already be working on a non-bootable machine... and I have been depending on it for YEARS... Apologies if I took a few line to express my alarm here... But are we certain at this point that my latest compile failure is caused by an old package(s)? It's conceivable that it's something in between? A bug that can emerge only in such an old environment ? As in, SOME code is MEANT to be backwards-compatible (to some degree), but a bug therein might not be readily seen, until someone with an old environment comes a long ? (me) In a case like that my feedback could be legit and untainted by my rip-van-winkle situation. And, after all... my ./configure is happy! It should, theoretically, spot and complain about incompatibilities ? Specifically, I think my breakage happens in the ./gtk/Makefile subdirectory of the source root. It's rather bewildering that the make interpreter can't print out more specifics about the breakage... there are line numbers mentioned at the end of the error message but I don't think that's where the /bin/sh: --: invalid option error occurs. Even though this is out of my depth, I would guess that somewhere an option is being passed with an intended string variable that is empty in my case (but isn't empty in newer environments), and thus a solitary double dash ? (-- instead of some --cflags blah blah blha) The ./gtk/Makefile has 6518 ! I wish the error led me to the offending line... thanks again for the help so far... ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
On Sat, Feb 15, 2014 at 7:45 AM, Bric b...@flight.us wrote: But are we certain at this point that my latest compile failure is caused by an old package(s)? Easiest way to find out is probably to spin yourself up a newer OS (Ubuntu 12.04 LTS Precise or 13.10 Saucy, or maybe Debian Wheezy, which is what I use), either on a spare bit of hardware or in a virtual machine. Then try building inside that. Use nothing but the OS-provided packages, see how it goes. Compare. ChrisA ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Re: final gtk+maverick battles
Incidentally: On Sat, Feb 15, 2014 at 7:45 AM, Bric b...@flight.us wrote: It's rather bewildering that the make interpreter can't print out more specifics about the breakage... Makefiles are notorious for being hard to debug, partly because they're often generated by a script. It's almost never worth the effort of delving into my makefile isn't working. :( ChrisA ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
final gtk+maverick battles
thought I'd move out to a new thread, since we are past the Pango issue in reckless abandonment (sliding irrevocably down the slope of system trashing) I manually moved *glib* files and directories from under /usr/local/lib, to a hiding place, then quickly re-installed (make install) glib from git. my git gtk+ continued to give me the nasty 2.39.4 vs. 2.39.5 discrepancy error. Then I ./autogen.sh'ed it again... and, lo and behold, the ./autogen.sh cleared its misunderstanding of what my glib version was (this, in conjunction with the above deletions, in /usr/local/lib, I presume) So, my gtk+ git finally ./configure'd. But then, of course, it had to snag with this: http://www.flight.us//misc/gtk_compile_error1.txt thanks again!! ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
