Re: final gtk+maverick battles

2014-02-17 Thread Bric

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

2014-02-17 Thread Bric

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: Can't link to Pango

2014-02-15 Thread Bric

On 02/14/2014 05:13 PM, David Marceau wrote:

On 02/13/2014 12:37 PM, Bric wrote:

On 02/13/2014 07:03 AM, Kang Hu wrote:

sorry for my previous misinfomation
it seems that the error happens here in your configure log file:
-

configure:24295: gcc -o conftest -march=i686 -mtune=i686 -Wall
-pthread -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -I/usr/local/include/cairo
-I/usr/local/include -I/usr/local/include/freetype2
-I/usr/local/include/libpng12 -I/usr/include/pixman-1  -ldl
conftest.c -L/usr/local/lib -lpangocairo-1.0 -lpango-1.0 -lcairo
-lgobject-2.0 -lglib-2.05
/usr/local/lib/libpangocairo-1.0.so  http://libpangocairo-1.0.so:
undefined reference to `pango_fc_font_create_base_metrics_for_context'
collect2: ld returned 1 exit status
-

Bric,

You shouldn't be getting this
undefined reference to `pango_fc_font_create_base_metrics_for_context'
linker error.

You haven't provided your entire source code project to compile and link
with.  That said there is a pango example c++ project out there that I
found:
1)go get this sample project:
https://git.gnome.org/browse/gtkmm-documentation/plain/examples/book/drawingarea/pango_text/

The following makefile isn't the most elegant, but it gets the job done.
##
# Makefile
##
all: pangotextcpp

pangotextcpp:
g++ -v -std=gnu++11  -c main.cc  `pkg-config gtkmm-3.0 --cflags --libs`
-lboost_system -lboost_filesystem -lboost_serialization
-lboost_iostreams -lboost_date_time
g++ -v -std=gnu++11  -c myarea.cc  `pkg-config gtkmm-3.0 --cflags
--libs` -lboost_system -lboost_filesystem -lboost_serialization
-lboost_iostreams -lboost_date_time
g++ -v -std=gnu++11  main.o myarea.o -o pangotextcpp   `pkg-config
gtkmm-3.0 --cflags --libs` -lboost_system -lboost_filesystem
-lboost_serialization -lboost_iostreams -lboost_date_time
##
# End of Makefile
##

2)then run make rebuild:
make -B

I wanted to send you the extended verbose output for this build, but the
mailing list refused me.  You will have to build to see them.

I do believe this Makefile will put you back on the right track.

There are others who don't agree with using Makefiles.  Please disregard
their comments because I am simplifying it for you.  There are no other
tools for you that are necessary to use.  The one thing you need to do
however is to install the necessary dependencies on your computer and do
heed the advice to upgrade your computer to the latest os.  It is well
worth it simply to save your time with older less-secure versions of not


David,

thank you for trying to help.  You may have forgotten about gtkmm. It 
depends on gtk+, and I don't have it yet, any version whatsoever. 
(Neither gtkmm, nor gtk+, of course)


So, here is what I get when I run  make -B on your example source:

g++ -v -std=gnu++11  -c main.cc  `pkg-config gtkmm-3.0 --cflags 
--libs`-lboost_system -lboost_filesystem -lboost_serialization 
-lboost_iostreams -lboost_date_time

Package gtkmm-3.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtkmm-3.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtkmm-3.0' found
Using built-in specs.
COLLECT_GCC=g++
Target: i686-pc-linux-gnu
Configured with: ./configure
Thread model: posix
gcc version 4.8.2 (GCC)
COLLECT_GCC_OPTIONS='-v' '-std=gnu++11' '-c' '-shared-libgcc' 
'-mtune=generic' '-march=pentiumpro'
 /usr/local/libexec/gcc/i686-pc-linux-gnu/4.8.2/cc1plus -quiet -v 
-D_GNU_SOURCE main.cc -quiet -dumpbase main.cc -mtune=generic 
-march=pentiumpro -auxbase main -std=gnu++11 -version -o /tmp/cc5MiXGw.s

GNU C++ (GCC) version 4.8.2 (i686-pc-linux-gnu)
compiled by GNU C version 4.8.2, GMP version 5.1.3, MPFR version 
3.1.2, MPC version 1.0.2

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
ignoring nonexistent directory 
/usr/local/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../i686-pc-linux-gnu/include

#include ... search starts here:
#include ... search starts here:
 /usr/local/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../include/c++/4.8.2
 
/usr/local/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../include/c++/4.8.2/i686-pc-linux-gnu
 
/usr/local/lib/gcc/i686-pc-linux-gnu/4.8.2/../../../../include/c++/4.8.2/backward
 /usr/local/lib/gcc/i686-pc-linux-gnu/4.8.2/include
 /usr/local/include
 /usr/local/lib/gcc/i686-pc-linux-gnu/4.8.2/include-fixed
 /usr/include
End of search list.
GNU C++ (GCC) version 4.8.2 (i686-pc-linux-gnu)
compiled by GNU C version 4.8.2, GMP version 5.1.3, MPFR version 
3.1.2, MPC version 1.0.2

GGC heuristics: --param

Re: Can't link to Pango

2014-02-15 Thread Bric

On 02/15/2014 09:34 AM, David Marceau wrote:

Bric,

Please install gtkmm-dev.  You should also install boost-all-dev.
That will bring in all the gtkmm/boost libs along with all the necessary
include files for them.  After that you should be good to go.


I already have libgtkmm-2.4-dev and   libboost-all-dev installed. My 
repositories don't have anything newer for gtkmm.





___
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

2014-02-14 Thread Bric

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

2014-02-14 Thread Bric

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: Can't link to Pango

2014-02-13 Thread Bric

On 02/13/2014 04:21 AM, Lucas Levrel wrote:

Le 12 février 2014, Bric a écrit :


I am trying to compile gtk+-3.11.5

during ./configure I am getting:

Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org

I have pango-1.36.2 installed


pkg-config --cflags pango pangocairo :


I think you should look at --libs since the error is about linking.



$ pkg-config --libs pango
-L/usr/local/lib -lpango-1.0 -lgobject-2.0 -lglib-2.0

$ pkg-config --libs pango pangocairo
-L/usr/local/lib -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 
-lglib-2.0


ça ne change pas grand chose (en ce qui concerne ma compréhension)

that doesn't give me a clue



___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Can't link to Pango

2014-02-13 Thread Bric
 of which is 
not yielding easily (!!!) — battling over 48 hours now...



i don't know a better way to do this.  your problem may be caused by  the 
custom-built pango library.



On Thu, Feb 13, 2014 at 6:26 PM, Bric b...@flight.us 
mailto:b...@flight.us wrote:


On 02/13/2014 04:21 AM, Lucas Levrel wrote:

Le 12 février 2014, Bric a écrit :

I am trying to compile gtk+-3.11.5

during ./configure I am getting:

Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org

I have pango-1.36.2 installed


pkg-config --cflags pango pangocairo :


I think you should look at --libs since the error is about
linking.


$ pkg-config --libs pango
-L/usr/local/lib -lpango-1.0 -lgobject-2.0 -lglib-2.0

$ pkg-config --libs pango pangocairo
-L/usr/local/lib -lpangocairo-1.0 -lpango-1.0 -lcairo
-lgobject-2.0 -lglib-2.0

ça ne change pas grand chose (en ce qui concerne ma compréhension)

that doesn't give me a clue




___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org mailto:gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list




___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Can't link to Pango

2014-02-13 Thread Bric

On 02/13/2014 01:45 PM, Emmanuele Bassi wrote:

hi;

On 13 February 2014 18:37, Bric b...@flight.us wrote:


Is this because the git version doesn't definitively dominate all the
version markers when it installs, and leaves behind the previously installed
versions ??  (git gtk+ is picking up the previous glib-2.39.4, somehow,
the one compiled from release tarball.)

you most likely have .la files lying around.


why are you targeting such an old platform?


Well... i guess it all started with the advent of unity, in Ubuntu 11.

[cut]

my question was more: are you planning on developing GTK/GNOME apps
while retaining your system copy, or are you literally trashing your
system by installing newer versions on top of your running system?


[second attempt to post this... earlier post isn't showing up for some 
reason]


Well, you're the first one to definitively characterize this as 
trashing my system... but I've been suspecting that that's what it is.


I'd like to note that i have JUST NOW ( a couple of days ago) embarked 
on this system trashing, because of the ambition to get the newest gtk+. 
I don't even fully understand the extent of the damage, but am starting 
to feel how quickly it comes.


No, I am not ready for serious gtk+ development, although that's an 
enticing idea (my angle [t]here would be Perl).  At the moment I need 
gtk+ as a dependency.  So... yes, you greatly worry me with this ominous 
warning. I haven't even rebooted since the trashing began (!!)... 
perhaps I'll be rebooting into a blinking cursor (at best) or kernel 
panic ... ;-)) :-((


Meanwhile, I really really appreciate all the help here.  I would have 
never guessed to edit my /usr/local/lib/pkgconfig/pangocairo.pc (that 
worked like a charm, apparently).


---

left-over *.la files?   Did I forget an --enable-shared somewhere ??? 
This is the classic case of knowing just enough to be dangerous...  In 
my defense, however, I have abstained from system trashing, as someone 
dated it here, for FOUR YEARS. :-))





if you're just looking at a development environment, then you should
probably be cloning jhbuild from git, and creating a separate
environment, in a separate directory.

otherwise, I'd strongly suggest you just learn to let go. there are
other distributions, even Debian-based, that are shipping with a
decent set of dependencies. learning how to make packages will lead
you to maintain a Ubuntu fork anyway, and I can assure you:
maintaining a distribution by yourself is not in any way, shape, or
form fun.

ciao,
  Emmanuele.



___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Can't link to Pango

2014-02-13 Thread Bric

On 02/13/2014 01:45 PM, Emmanuele Bassi wrote:

hi;

On 13 February 2014 18:37, Bric b...@flight.us wrote:


Is this because the git version doesn't definitively dominate all the
version markers when it installs, and leaves behind the previously installed
versions ??  (git gtk+ is picking up the previous glib-2.39.4, somehow,
the one compiled from release tarball.)

you most likely have .la files lying around.


why are you targeting such an old platform?


Well... i guess it all started with the advent of unity, in Ubuntu 11.

[cut]

my question was more: are you planning on developing GTK/GNOME apps
while retaining your system copy, or are you literally trashing your
system by installing newer versions on top of your running system?


Well, you're the first one to definitely characterize this as trashing 
my system... but I've been suspecting that that's what it is.


I'd like to note that i have JUST NOW ( a couple of days ago) embarked 
on this system trashing, because of the ambition to get the newest gtk+. 
I don't even fully understand the extent of the damage, but am starting 
to feel how quickly it comes.


No, I am not ready for serious gtk+ development, although that's an 
enticing idea (my angle [t]here would be Perl).  At the moment I need 
gtk+ as a dependency.  So... yes, you greatly worry me with this ominous 
warning. I haven't even rebooted since the trashing began (!!)... 
perhaps I'll be rebooting into a blinking cursor (at best) or kernel 
panic ... ;-)) :-((


Meanwhile, I really really appreciate all the help here.  I would have 
never guessed to edit my /usr/local/lib/pkgconfig/pangocairo.pc (that 
worked like a charm, apparently).


---

left-over *.la files?   Did I forget an --enable-shared somewhere ??? 
This is the classic case of knowing just enough to be dangerous...  In 
my defense, however, I have abstained from system trashing, as someone 
dated it here, for FOUR YEARS. :-))





if you're just looking at a development environment, then you should
probably be cloning jhbuild from git, and creating a separate
environment, in a separate directory.

otherwise, I'd strongly suggest you just learn to let go. there are
other distributions, even Debian-based, that are shipping with a
decent set of dependencies. learning how to make packages will lead
you to maintain a Ubuntu fork anyway, and I can assure you:
maintaining a distribution by yourself is not in any way, shape, or
form fun.

ciao,
  Emmanuele.



___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Can't link to Pango

2014-02-13 Thread Bric

On 02/13/2014 12:53 PM, Emmanuele Bassi wrote:

hi;

On 13 February 2014 17:37, Bric b...@flight.us wrote:


I did the above workaround, successfully, and got past my pango snag

Then ./configure complained about not having atk-bridge; i went down that
chain of dependencies, with at-spi2-core, etc., (some of the latest git
failed to make; i used version releases), and made gtk+ ./configure happy.
But gtk+ make is now failing — HANGING (not exiting!) on an error:
(glib-compile-resources:6887): GLib-GObject-CRITICAL **:
/build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to call
g_type_init()

you're building against a far too old version of GLib. check your
LD_LIBRARY_PATH, because it seems the configure script is catching a
version of GLib recent enough to satisfy the dependency check, but the
linker is trying to use the system version of GLib.


Yes, it's a mess. Here is even more of the mess:  When I try to build 
latest gtk+ from git, it complains that it is finding glib 2.39.4, but 
that the minimum it wants is 2.39.5.


glib 2.39.5 is not an official release yet (correct me if I'm wrong), 
so, I make the assumption that, at the moment, glib 2.39.5 means glib 
git. So, I update and build my glib from git successfully (just a few 
minutes ago), and install.  So, you think gtk+ ./configure is now happy 
?  No! It gives me this weirdness:


-- begin quote --
checking for HP-UX... no
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version = 2.39.5...
*** 'pkg-config --modversion glib-2.0' returned 2.39.5, but GLIB (2.39.4)
*** was found! If pkg-config was correct, then it is best
*** to remove the old version of GLib. You may also be able to fix the error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
*** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
*** to point to the correct configuration files
no
configure: error:
*** GLIB 2.39.5 or better is required. The latest version of
*** GLIB is always available from ftp://ftp.gtk.org/pub/gtk/.

-- end quote -

Is this because the git version doesn't definitively dominate all the 
version markers when it installs, and leaves behind the previously 
installed versions ??  (git gtk+ is picking up the previous 
glib-2.39.4, somehow, the one compiled from release tarball.)




This is a never ending battle, this gtk+ on my Ubuntu 10.10, with the
sprawling tree and extensive chains of dependencies, each of which is not
yielding easily (!!!) — battling over 48 hours now...

you're trying to build a very recent version of a complex library on a
4 years old distribution: issues are to be expected, as well as some
pain in rebuilding the entire stack.


roger on that


why are you targeting such an old platform?


Well... i guess it all started with the advent of unity, in Ubuntu 
11.  I was one of those happy Ubuntu/Gnome users who started kicking and 
screaming, bewildered why a good thing, such as Ubuntu as we had known 
it up until Maverick, was suddenly and irrevocably taken away.  I have 
held on to Maverick all these years, beyond its official expiration date 
(miraculously, it has been unofficially supported all this time, and 
continued to be stable enough for a production environment). Maybe I've 
finally reached its limits, as one, well-lubricated, integrated whole.  
If I'm causing library confusion, there's no telling.  Perhaps I need to 
learn how to build proper debian packages, so I can add them to this 
system with all the proper triggers and cross-linking in play.


I /do/ remember building gtk+ many years ago, on fedora ... it feels 
like I'm going back in time right now :-))


___
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

2014-02-13 Thread Bric

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


Can't link to Pango

2014-02-12 Thread Bric

I am trying to compile gtk+-3.11.5

during ./configure I am getting:

 Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org

I have pango-1.36.2 installed


pkg-config --cflags pango pangocairo :

-pthread -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0 
-I/usr/local/lib/glib-2.0/include -I/usr/local/include/cairo 
-I/usr/local/include -I/usr/local/include/freetype2 
-I/usr/local/include/libpng12 -I/usr/local/include/harfbuzz 
-I/usr/include/pixman-1


---

frustrating to no end.  Can someone please help?

___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Can't link to Pango

2014-02-12 Thread Bric

On 02/12/2014 10:30 PM, Kang Hu wrote:

the error message is emitted here in configure.ac http://configure.ac:
---
if $PKG_CONFIG --uninstalled $PANGO_PACKAGES; then
:
else
gtk_save_LIBS=$LIBS
LIBS=$PANGO_LIBS $LIBS
AC_TRY_LINK_FUNC(pango_context_new, :, AC_MSG_ERROR([
*** Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org]))
LIBS=$gtk_save_LIBS
fi
---

apparently the condition pkg-config --uninstalled pango pangocairo 
is not true.


the --uninstalled option passed to pkg-config instructs pkg-config 
to find pango-uninstalled.pc instead of pango.pc.
this option is mostly used for compilation/linking against uninstalled 
packages.  see man pkg-config for more details.
you can set PKG_CONFIG_DISABLE_UNINSTALLED env variable to disable 
this behavior.




I just tried...

export PKG_CONFIG_DISABLE_UNINSTALLED=1

and

export PKG_CONFIG_DISABLE_UNINSTALLED=true

but ./configure still halts with the same can't link to Pango message.

Here is my config.log :

http://www.flight.us/misc/gtk_config.log.txt

thanks.



On Thu, Feb 13, 2014 at 10:13 AM, Bric b...@flight.us 
mailto:b...@flight.us wrote:


I am trying to compile gtk+-3.11.5

during ./configure I am getting:

 Can't link to Pango. Pango is required to build
*** GTK+. For more information see http://www.pango.org

I have pango-1.36.2 installed


pkg-config --cflags pango pangocairo :

-pthread -I/usr/local/include/pango-1.0
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
-I/usr/local/include/cairo -I/usr/local/include
-I/usr/local/include/freetype2 -I/usr/local/include/libpng12
-I/usr/local/include/harfbuzz -I/usr/include/pixman-1

---

frustrating to no end.  Can someone please help?

___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org mailto:gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list




___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list