Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Oct 2016 14:57:16 -0600
From:      "John Hein" <jh-fbml@snkmail.com>
To:        gnome@freebsd.org
Subject:   Re: net/avahi-app fails to configure due to XML::Parser
Message-ID:  <2177-1476705567-546314@sneakemail.com>
In-Reply-To: <580289B5.1010603@greengear.com>
References:  <58016483.9090101@greengear.com> <CAN6yY1sA=413eocstsZHKA55nHbZSU_-=c9U2TqK1T8OcMd3Sw@mail.gmail.com> <580262BE.6060602@greengear.com> <CAN6yY1vAm7TnW3gx0qfTcj8%2B4sxxjHe44iVvFAPvL=ecWbLK-g@mail.gmail.com> <580289B5.1010603@greengear.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Walter Lapchynski wrote at 12:55 -0700 on Oct 15, 2016:
 > On 10/15/2016 12:23 PM, Kevin Oberman wrote:
 > > On Sat, Oct 15, 2016 at 10:09 AM, Walter Lapchynski <wxl@greengear.com <mailto:wxl@greengear.com>> wrote:
 > >     On 10/14/2016 08:52 PM, Kevin Oberman wrote:
 > >     > On Fri, Oct 14, 2016 at 4:04 PM, Walter Lapchynski <wxl@greengear.com <mailto:wxl@greengear.com> <mailto:wxl@greengear.com <mailto:wxl@greengear.com>>> wrote:
 > >     >>     checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
 > >     >>     You'll notice that p5-XML-Parser is included in the package list, though.
 > >     > just re-install p5-XML-Parser and it will work again. 
 > >     Unfortunately, that didn't work, no matter how I do it, whether simply through make or via portmaster on either package or both. Any other ideas?
 > > Can you post the contents of config.log someplace?  Or mail it privately to me. 
 > 
 > The output I got from the compilation is as above. However, if you look at config.log:
 > 
 > http://pastebin.com/DkPPLhwM
 > 
 > you find:
 > 
 >     conftest.c:128:10: fatal error: 'sys/inotify.h' file not found
 >     #include <sys/inotify.h>
 >              ^
 >     1 error generated.
 > 
 > which certainly suggests a different issue. 
 > 
 > So, I'm guessing I should install libnotify?

The missing inotify.h is okay (not needed - and in fact, explicitly
disabled for this port - it caused build problems for this port and
others in the past, although a recent version of devel/libinotify may
work fine these days).  That's just configure doing its normal thing.

The test in configure for XML::Parser is pretty simple.
What if you do:

 perl -e "require XML::Parser"
 which perl
 perl -V

More than likely it's a problem with your perl or XML::Parser
installation.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2177-1476705567-546314>