On Sunday 18 January 2009 23:57:24 Wojtek Dalętka wrote:
> I would like to write my first post here just to inform you that I also
> had this problem with avahi and pygtk.
> Avahi failed to emerge and I had to remove pygtk from my use flags, than
> it compiled OK.
>
> I was just interested if removing "-pipe" from CFLAGS makes any
> difference, and I tried remove it and emerge avahi with pygtk, but it
> does not compile.
> For me it compiles only without pygtk and changing -pipe doesn't work at
> all. I checked this because I have 512M.
>
> I don't know why I might need avahi with pygtk...disabling pygtk use
> flag for avahi works fine and other packages compile well.
Are you running stable or testing?
avahi does not have a pygtk USE flag. In fact, there isn't one in portage at
all:
~ $ euse -i pygtk
global use flags (searching: pygtk)
************************************************************
no matching entries found
local use flags (searching: pygtk)
************************************************************
no matching entries found
So whether you have it or not should make no difference at all.
The latest avahi ebuild contains this interesting snippet though:
"src_compile() {
...
# We need to unset DISPLAY, else the configure script might have
problems detecting the pygtk module
unset DISPLAY
econf \
"
I'm not really in a position to help you further as I don't have avahi (or any
zeroconf packages) - mostly because the only place I ever use this notebook
is on properly configured networks
--
alan dot mckinnon at gmail dot com
