public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: co <cuicle@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [gentoo-user] Fwd: gnome-applets-python 装不上
Date: Fri, 21 Oct 2011 16:03:46 +0800	[thread overview]
Message-ID: <CAChzKCrY8QP6xH0mOk-2pTrE3-2Ep=GH4ks3-jOBwS_9heMJ8Q@mail.gmail.com> (raw)
In-Reply-To: <4EA12207.9000804@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3838 bytes --]

Thankyou, I found this
note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead
note: I will now try to invoke pygobject-codegen-2.0 in the same directory
Could not write function factory_main: No ArgType for
PanelAppletFactoryCallback
Could not write function panel_applet_shlib_factory: No ArgType for gpointer
Could not write function panel_applet_shlib_factory_closure: No ArgType for
gpointer
Could not write function main: No ArgType for char*-argv
Warning: Constructor for PanelApplet needs to be updated to new API
         See http://live.gnome.org/PyGTK_2fWhatsNew28#update-constructors
***INFO*** The coverage of global functions is 33.33% (2/6)
***INFO*** The coverage of methods is 100.00% (13/13)
***INFO*** There are no declared virtual proxies.
***INFO*** There are no declared virtual accessors.
***INFO*** There are no declared interface proxies.

2011/10/21 Dale <rdalek1967@gmail.com>

> co wrote:
>
>>
>> can't emerge  gnome-applets-python
>> what's the problem?
>>
>>  * ERROR: dev-python/gnome-applets-**python-2.32.0 failed (compile
>> phase):
>>  *   Building failed with CPython 2.7 in python_default_function()
>> function
>>  *
>>  * Call stack:
>>  *     ebuild.sh, line   56:  Called src_compile
>>  *   environment, line 6045:  Called gnome-python-common_src_**compile
>>  *   environment, line 3099:  Called python_src_compile
>>  *   environment, line 5899:  Called python_execute_function '-d' '-s'
>> '--'
>>  *   environment, line 4352:  Called die
>>  * The specific snippet of code:
>>  *                       die "${failure_message}";
>>  *
>>  * If you need support, post the output of 'emerge --info
>> =dev-python/gnome-applets-**python-2.32.0',
>>  * the complete build log and the output of 'emerge -pqv
>> =dev-python/gnome-applets-**python-2.32.0'.
>>  * The complete build log is located at '/var/tmp/portage/dev-python/**
>> gnome-applets-python-2.32.0/**temp/build.log'.
>>  * The ebuild environment file is located at '/var/tmp/portage/dev-python/
>> **gnome-applets-python-2.32.0/**temp/environment'.
>>  * S: '/var/tmp/portage/dev-python/**gnome-applets-python-2.32.0/**
>> work/gnome-python-desktop-2.**32.0'
>>
>> >>> Failed to emerge dev-python/gnome-applets-**python-2.32.0, Log file:
>>
>> >>>  '/var/tmp/portage/dev-python/**gnome-applets-python-2.32.0/**
>> temp/build.log'
>>
>>  * Messages for package dev-python/gnome-applets-**python-2.32.0:
>>
>>  * ERROR: dev-python/gnome-applets-**python-2.32.0 failed (compile
>> phase):
>>  *   Building failed with CPython 2.7 in python_default_function()
>> function
>>  *
>>  * Call stack:
>>  *     ebuild.sh, line   56:  Called src_compile
>>  *   environment, line 6045:  Called gnome-python-common_src_**compile
>>  *   environment, line 3099:  Called python_src_compile
>>  *   environment, line 5899:  Called python_execute_function '-d' '-s'
>> '--'
>>  *   environment, line 4352:  Called die
>>  * The specific snippet of code:
>>  *                       die "${failure_message}";
>>  *
>>  * If you need support, post the output of 'emerge --info
>> =dev-python/gnome-applets-**python-2.32.0',
>>  * the complete build log and the output of 'emerge -pqv
>> =dev-python/gnome-applets-**python-2.32.0'.
>>  * The complete build log is located at '/var/tmp/portage/dev-python/**
>> gnome-applets-python-2.32.0/**temp/build.log'.
>>  * The ebuild environment file is located at '/var/tmp/portage/dev-python/
>> **gnome-applets-python-2.32.0/**temp/environment'.
>>  * S: '/var/tmp/portage/dev-python/**gnome-applets-python-2.32.0/**
>> work/gnome-python-desktop-2.**32.0'
>>
>>
> You need to post farther back than this.  Sometimes it fails farther back
> than expected.  See if you can find "Error 1" and then go back at least a
> couple dozen lines.  That *usually* is far enough.
>
> Dale
>
> :-)  :-)
>
>

[-- Attachment #2: Type: text/html, Size: 4876 bytes --]

  reply	other threads:[~2011-10-21  8:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAChzKCq_7xGWz_Pq5cOTGVzquHY0rw5-9tpWDchOjtxRVXLwUQ@mail.gmail.com>
2011-10-21  6:57 ` [gentoo-user] Fwd: gnome-applets-python 装不上 co
2011-10-21  7:40   ` Dale
2011-10-21  8:03     ` co [this message]
2011-10-21  9:07       ` [gentoo-user] Re: [gentoo-user] " Jonas de Buhr
2011-10-21  9:15         ` [gentoo-user] " co
2011-10-21  9:38           ` [gentoo-user] " Jonas de Buhr
2011-10-21  9:48             ` [gentoo-user] " co
2011-10-21  9:40           ` Dale
2011-10-21  9:49             ` [gentoo-user] " co

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAChzKCrY8QP6xH0mOk-2pTrE3-2Ep=GH4ks3-jOBwS_9heMJ8Q@mail.gmail.com' \
    --to=cuicle@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox