Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-24 Thread Mick
On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote:
 On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:

  What do you get when you run:
  
  # eselect python list
 
 Available Python interpreters:
   [1]   python2.6 *
   [2]   python2.7
   [3]   python3.1

OK, the next stage would be to change your python to the latest stable:

eselect python set 2

and then remerge those packages that were linked against the old python:

python-updater -v -p

to get a list of these.

When you finish all this you can run:

emerge --depclean -v -p

It should now ask you to remove the old python, but check carefully the 
remaining packages in case something important is in the list and breaks your 
system.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-23 Thread Alan Mackenzie
Hi, Alan.

On Sat, Apr 23, 2011 at 12:43:45AM +0200, Alan McKinnon wrote:
 Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan Mackenzie 
 did opine thusly:

  Hi, Gentoo.

  In my attempt to 'emerge --update --deep xfce4-meta', one sole
  package is refusing to build, namely pygtk.

  Its log file displays many (perhaps 100) error lines like:

  Could not write method AtkObject.get_attributes: No ArgType for
  AtkAttributeSet*

  .  The command that caused all these errors was:

  libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
  -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
  -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
  -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
  -I/usr/lib64/glib-2.0/include -I./gtk
  -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
  -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
  -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
  -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
  .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
  .libs/pango_la-pangomodule.o

  .  If anybody knows how to fix this, or a more appropriate place to
  ask for help, please tell me.

  Thanks in advance!

 This one might be tricky. Here's a tip: include version numbers of
 packages that are giving trouble, and whether you run stable, testing
 or (god forbid!) a mixture - this can be rather important in guiding
 one to what to do next (a process mostly defined by instinct rather
 than by say reason)

OK.  As a relative newbie, I only run stable.  My system is giving me
enough headaches as it is.

 The error looks like an API break between pygtk and whatever provides 
 AtkObject. That is part of the gtk accessibility toolkit, and the relevant 
 files come out of a package called atk.

 My first guess is that pygtk and atk are now out of sync on your machine. Try 
 this:

 emerge -av1 atk
 emerge -av1 pygtk

 Post back if that doesn't work.

Sadly, it didn't work.

 Another tip: search bugs.gentoo.org first before posting - oftentimes 
 the problem is already known and reported on. In this specific case
 however, I didn't find anything.

OK.  I managed to get the problem fixed, basically by trying everything,
though I don't really understand what I did.  This was my recipe:

emerge --sync
emerge --update --deep --newuse xfce4-meta

, which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
thanks!

 -- 
 alan dot mckinnon at gmail dot com

-- 
Alan Mackenzie (Nuremberg, Germany).



Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-23 Thread Mick
On Saturday 23 April 2011 17:35:44 Alan Mackenzie wrote:
 Hi, Alan.
 
 On Sat, Apr 23, 2011 at 12:43:45AM +0200, Alan McKinnon wrote:
  Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan
  Mackenzie
  
  did opine thusly:
   Hi, Gentoo.
   
   In my attempt to 'emerge --update --deep xfce4-meta', one sole
   package is refusing to build, namely pygtk.
   
   Its log file displays many (perhaps 100) error lines like:
   Could not write method AtkObject.get_attributes: No ArgType for
   
   AtkAttributeSet*
   
   .  The command that caused all these errors was:
   
   libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
   -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
   -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
   -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
   -I/usr/lib64/glib-2.0/include -I./gtk
   -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
   -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
   -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
   -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
   .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
   .libs/pango_la-pangomodule.o
   
   .  If anybody knows how to fix this, or a more appropriate place to
   ask for help, please tell me.
   
   Thanks in advance!
  
  This one might be tricky. Here's a tip: include version numbers of
  packages that are giving trouble, and whether you run stable, testing
  or (god forbid!) a mixture - this can be rather important in guiding
  one to what to do next (a process mostly defined by instinct rather
  than by say reason)
 
 OK.  As a relative newbie, I only run stable.  My system is giving me
 enough headaches as it is.
 
  The error looks like an API break between pygtk and whatever provides
  AtkObject. That is part of the gtk accessibility toolkit, and the
  relevant files come out of a package called atk.
  
  My first guess is that pygtk and atk are now out of sync on your machine.
  Try this:
  
  emerge -av1 atk
  emerge -av1 pygtk
  
  Post back if that doesn't work.
 
 Sadly, it didn't work.
 
  Another tip: search bugs.gentoo.org first before posting - oftentimes
  the problem is already known and reported on. In this specific case
  however, I didn't find anything.
 
 OK.  I managed to get the problem fixed, basically by trying everything,
 though I don't really understand what I did.  This was my recipe:
 
 emerge --sync
 emerge --update --deep --newuse xfce4-meta
 
 , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
 thanks!

What do you get when you run:

# eselect python list
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-23 Thread Alan Mackenzie
Hi, Mick.

On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote:
 On Saturday 23 April 2011 17:35:44 Alan Mackenzie wrote:
  Hi, Alan.

  On Sat, Apr 23, 2011 at 12:43:45AM +0200, Alan McKinnon wrote:
   Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan
   Mackenzie

   did opine thusly:
Hi, Gentoo.

In my attempt to 'emerge --update --deep xfce4-meta', one sole
package is refusing to build, namely pygtk.

Its log file displays many (perhaps 100) error lines like:
Could not write method AtkObject.get_attributes: No ArgType for

AtkAttributeSet*

.  The command that caused all these errors was:

libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
-I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -I./gtk
-I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
-fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
.deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
.libs/pango_la-pangomodule.o

.  If anybody knows how to fix this, or a more appropriate place
to ask for help, please tell me.

Thanks in advance!

   This one might be tricky. Here's a tip: include version numbers of
   packages that are giving trouble, and whether you run stable,
   testing or (god forbid!) a mixture - this can be rather important
   in guiding one to what to do next (a process mostly defined by
   instinct rather than by say reason)

  OK.  As a relative newbie, I only run stable.  My system is giving
  me enough headaches as it is.

   The error looks like an API break between pygtk and whatever
   provides AtkObject. That is part of the gtk accessibility toolkit,
   and the relevant files come out of a package called atk.

   My first guess is that pygtk and atk are now out of sync on your
   machine.  Try this:

   emerge -av1 atk
   emerge -av1 pygtk

   Post back if that doesn't work.

  Sadly, it didn't work.

   Another tip: search bugs.gentoo.org first before posting -
   oftentimes the problem is already known and reported on. In this
   specific case however, I didn't find anything.

  OK.  I managed to get the problem fixed, basically by trying
  everything, though I don't really understand what I did.  This was my
  recipe:

  emerge --sync
  emerge --update --deep --newuse xfce4-meta

  , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
  thanks!

 What do you get when you run:

 # eselect python list

Available Python interpreters:
  [1]   python2.6 *
  [2]   python2.7
  [3]   python3.1

 -- 
 Regards,
 Mick

-- 
Alan Mackenzie (Nuremberg, Germany).



Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-23 Thread Alan McKinnon
Apparently, though unproven, at 18:35 on Saturday 23 April 2011, Alan 
Mackenzie did opine thusly:

 OK.  I managed to get the problem fixed, basically by trying everything,
 though I don't really understand what I did.  This was my recipe:
 
 emerge --sync
 emerge --update --deep --newuse xfce4-meta
 
 , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
 thanks!

In that case, you either had an incomplete portage tree and syncing gave you 
all the bits you needed. Or the pygtk ebuild was faulty and the dev fixed it 
without bumping the version number.


-- 
alan dot mckinnon at gmail dot com



Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-23 Thread Volker Armin Hemmann
On Saturday 23 April 2011 22:21:28 Alan McKinnon wrote:
 Apparently, though unproven, at 18:35 on Saturday 23 April 2011, Alan
 
 Mackenzie did opine thusly:
  OK.  I managed to get the problem fixed, basically by trying everything,
  
  though I don't really understand what I did.  This was my recipe:
  emerge --sync
  emerge --update --deep --newuse xfce4-meta
  
  , which updated libglade-2.6.4 and pygtk-2.22.0-r1 successfully.  So
  thanks!
 
 In that case, you either had an incomplete portage tree and syncing gave you
 all the bits you needed. Or the pygtk ebuild was faulty and the dev fixed
 it without bumping the version number.

which happens everytime a version is so bugged it does not install.



Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-22 Thread Dale

Alan Mackenzie wrote:

Hi, Gentoo.

In my attempt to 'emerge --update --deep xfce4-meta', one sole package
is refusing to build, namely pygtk.

Its log file displays many (perhaps 100) error lines like:

 Could not write method AtkObject.get_attributes: No ArgType for 
AtkAttributeSet*

.  The command that caused all these errors was:

libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. 
-I/usr/include/python2.6 -I/usr/include/python2.6 -pthread 
-I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I./gtk 
-I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread 
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-O2 -pipe -march=athlon64 -Wall -fno-strict-aliasing -std=c9x -MT 
pango_la-pangomodule.lo -MD -MP -MF .deps/pango_la-pangomodule.Tpo -c 
pangomodule.c  -fPIC -DPIC -o .libs/pango_la-pangomodule.o

.  If anybody knows how to fix this, or a more appropriate place to ask
for help, please tell me.

Thanks in advance!

   


I did a bit of googling and found some things to try.  Running 
etc-update was one and python-updater was another.  I also saw a mention 
of running fixlibtool but I'm not sure that helped any.


Maybe one of those will help.  Maybe worth trying at least.

Dale

:-)  :-)



Re: [gentoo-user] Building pygtk-2.22.0-r1 fails. Help, please!

2011-04-22 Thread Alan McKinnon
Apparently, though unproven, at 20:05 on Friday 22 April 2011, Alan Mackenzie 
did opine thusly:

 Hi, Gentoo.
 
 In my attempt to 'emerge --update --deep xfce4-meta', one sole package
 is refusing to build, namely pygtk.
 
 Its log file displays many (perhaps 100) error lines like:
 
 Could not write method AtkObject.get_attributes: No ArgType for
 AtkAttributeSet*
 
 .  The command that caused all these errors was:
 
 libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
 -I/usr/include/python2.6 -I/usr/include/python2.6 -pthread
 -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0
 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0
 -I/usr/lib64/glib-2.0/include -I./gtk
 -I/usr/lib64/python2.6/site-packages/numpy/core/include -pthread
 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
 -I/usr/lib64/glib-2.0/include -O2 -pipe -march=athlon64 -Wall
 -fno-strict-aliasing -std=c9x -MT pango_la-pangomodule.lo -MD -MP -MF
 .deps/pango_la-pangomodule.Tpo -c pangomodule.c  -fPIC -DPIC -o
 .libs/pango_la-pangomodule.o
 
 .  If anybody knows how to fix this, or a more appropriate place to ask
 for help, please tell me.
 
 Thanks in advance!

This one might be tricky. Here's a tip: include version numbers of packages 
that are giving trouble, and whether you run stable, testing or (god forbid!) 
a mixture - this can be rather important in guiding one to what to do next (a 
process mostly defined by instinct rather than by say reason)

The error looks like an API break between pygtk and whatever provides 
AtkObject. That is part of the gtk accessibility toolkit, and the relevant 
files come out of a package called atk.

My first guess is that pygtk and atk are now out of sync on your machine. Try 
this:

emerge -av1 atk
emerge -av1 pygtk

Post back if that doesn't work.

Another tip: search bugs.gentoo.org first before posting - oftentimes 
theproblem is already known and reported on. In this specific case however, I 
didn't find anything.


-- 
alan dot mckinnon at gmail dot com