From: Lord Imbrius the Despondent <jarmstrong@wi.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sys-apps/dbus-0.23.4-r1 fails to compile
Date: Sat, 7 Jan 2006 18:07:11 +0000 [thread overview]
Message-ID: <200601071807.11529.jarmstrong@wi.rr.com> (raw)
In-Reply-To: <81FEA2CD-4226-41B7-9908-1F467E372636@iinet.net.au>
Yup - running python-updater solved the problem. I didn't even notice that
python was upgraded in the last emerge -uD world I did. Thanks for the hint!
On Friday 06 January 2006 23:47, Jeff wrote:
> On 07/01/2006, at 9:53 AM, Richard Fish wrote:
> > On 1/5/06, Lord Imbrius the Despondent <jarmstrong@wi.rr.com> wrote:
> >> Hey guys - I was just doing an emerge -uD world and it comes to a
> >> screeching
> >> halt with "i686-pc-linux-gnu-gcc: dbus_bindings.c: No such file or
> >> directory"
> >> when compiling sys-apps/dbus-0.23.4-r1. Any clues? Thanks.
> >
> > dbus_bindings.c is built from dbus_bindings.pyx using the program
> > pyrex, provided by dev-python/pyrex. Do you have this package
> > installed? Did you updated python recently, but forget to run
> > python-updater?
>
> I had a problem yesterday that sounds similar to this after updating
> world. I forgot to include -a in the emerge and so wasn't aware that
> python was upgraded in the update. I don't remember seeing anything
> about dbus_bindings.c in the merge output although there was a
> mention of pyrex (I can't remember the actual message). Running
> python-updater was the answer.
>
> Jeff
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-01-08 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 9:06 [gentoo-user] sys-apps/dbus-0.23.4-r1 fails to compile Lord Imbrius the Despondent
2006-01-06 0:00 ` Trenton Adams
2006-01-06 14:20 ` Lord Imbrius the Despondent
2006-01-06 22:53 ` Richard Fish
2006-01-06 23:47 ` Jeff
2006-01-07 18:07 ` Lord Imbrius the Despondent [this message]
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=200601071807.11529.jarmstrong@wi.rr.com \
--to=jarmstrong@wi.rr.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