pcp
[Top] [All Lists]

Re: [pcp] [pcp-announce] pcp-3.5.5 released

To: Max Matveev <makc@xxxxxxxxx>
Subject: Re: [pcp] [pcp-announce] pcp-3.5.5 released
From: jeffpc@xxxxxxxxxxxxxx
Date: Fri, 8 Jul 2011 09:38:07 -0400
Cc: Nathan Scott <nathans@xxxxxxxxxx>, pcp <pcp@xxxxxxxxxxx>
In-reply-to: <19990.22924.321036.24255@xxxxxxxxxxxx>
References: <780625946.134421.1309986808467.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx> <795680652.135149.1310003251207.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx> <20110707144158.GG18916@xxxxxxxxxxxxxx> <19990.22924.321036.24255@xxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Fri, Jul 08, 2011 at 11:12:44AM +1000, Max Matveev wrote:
> On Thu, 7 Jul 2011 10:41:58 -0400, jeffpc  wrote:
> 
>  jeffpc> On Thu, Jul 07, 2011 at 11:47:31AM +1000, Nathan Scott wrote:
>  >> Hi all,
>  >> 
>  >> The pcp-3.5.5 has been tagged and uploaded.  This is mainly a bug
>  >> fix release...
>  >> 
>  >> pcp-3.5.5 (6 July 2011)
>  jeffpc> ...
>  >> - Perl changes for Solaris.
>  >> - Solaris pmda zpool_vdev_name() api change.
> 
>  jeffpc> FWIW, I get a build failure on OpenIndiana:
> Why is it always jeffpc how comes with unusual distros?

Hehe :)

This one is for fun.  I was "forced" to deal with Gentoo.

...
>  jeffpc> "grammar.y", line 61: fatal: invalid escape, or illegal reserved 
> word: expect
>  jeffpc> gmake[4]: *** [grammar.h] Error 1
> 
> %expect is the bison thing, you're using AT&T yacc - install gnu bison
> and the issue will go away.
> 
> Nathan, we should really check for bison and bison only if we're using
> its features.

Agreed.  It actually turns out that I have both the AT&T yacc as well as
bison installed.  I suspect it's a combination of $PATH silliness and the
bison package not making a symlink/hardlink for yacc.

> Jeff, do you know where openidiana guys keep their source?

OI uses Illumos for the core system - http://src.illumos.org/source/

Jeff.

-- 
UNIX is user-friendly ... it's just selective about who its friends are

<Prev in Thread] Current Thread [Next in Thread>