pcp
[Top] [All Lists]

Re: pcp updates

To: Nathan Scott <nscott@xxxxxxxxxx>
Subject: Re: pcp updates
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 14 Aug 2008 08:04:16 +1000
Cc: Max Matveev <makc@xxxxxxx>, pcp@xxxxxxxxxxx
In-reply-to: <1218661381.4645.68.camel@xxxxxxxxxxxxxxxxxx>
References: <1218609809.4645.46.camel@xxxxxxxxxxxxxxxxxx> <1218610990.2914.14.camel@bozo> <1218613488.4645.59.camel@xxxxxxxxxxxxxxxxxx> <1218623125.2914.21.camel@bozo> <18594.47855.656239.937662@xxxxxxxxxxxxxxxxxxxxxx> <1218661381.4645.68.camel@xxxxxxxxxxxxxxxxxx>
Reply-to: kenj@xxxxxxxxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
OK, that makes more sense ... and explains the problem I'm seeing.

If a build area has been used before Nathan's change you still have a
libpcp_pmcd.so even on Linux, make clean does not remove it, and make
creates libpcp_pmcd.a.  Then pmcd is linked (incorrectly) with
libpcp_pmcd.so.

The attached patch fixes this corner case.

My new *.deb's install OK and pmcd starts just fine now on Ubuntu.

On Thu, 2008-08-14 at 07:03 +1000, Nathan Scott wrote:
> Apologies all round - a typo in my earlier mail made this thread
> even more confusing than it needed to be.
> 
> libpcp_pmda.so and the pmcd DSO agent are as they always were,
> no plans to change that.  What we do have now is this libpcp_pmcd
> library... this turned out to be required on Windows.  It contains
> the pmcd internal symbols (code+data) that need to be visible to
> both the pmcd binary and the pmcd DSO PMDA - on Windows you cannot
> link a DSO to symbols from a binary, as we do on all the other
> platforms.
> 
> Initially I made this new lib a shared library on all platforms,
> but I later reverted that - its now a static library (everywhere
> except on Windows) which pmcd links with, and the symbols are
> resolved as they always were, directly from pmcd's address space,
> by the pmcd DSO PMDA.
> 
> Sorry for the confusion!

Attachment: patch
Description: Text Data

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