Re: final gtk+maverick battles

[Bric <bric flight us>]

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...