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
On Mon, Feb 17, 2014 at 11:05 PM, 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) connect
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
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
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.
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 upgr
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 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.g
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
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
On Sun, Feb 16, 2014 at 10:30 PM, Bric 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 Unit
On 02/14/2014 02:54 PM, Chris Angelico wrote:
On Sat, Feb 15, 2014 at 4:52 AM, Bric 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+
Incidentally:
On Sat, Feb 15, 2014 at 7:45 AM, Bric 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
On Sat, Feb 15, 2014 at 7:45 AM, Bric 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
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.
(!) :-(
On Sat, Feb 15, 2014 at 4:52 AM, Bric 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
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 u
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 s
>
>
> "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
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
19 matches
Mail list logo
