pcp
[Top] [All Lists]

Re: [pcp] pcp chroot build broken

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pcp chroot build broken
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Mon, 06 Feb 2012 09:51:26 +1100
Cc: pcp@xxxxxxxxxxx
In-reply-to: <1328261282.9716.6.camel@xxxxxxxxxxxxxxxxxxxxxxx>
References: <4F2B53C0.6090609@xxxxxxxxxx> <1328261282.9716.6.camel@xxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0
On 02/03/2012 08:28 PM, Ken McDonell wrote:
I agree ... (a) is preferable, especially as this means no changes in a
million man pages!  Changes in a lot of places, but they are easy to
find, the change is simple and the risk if getting it wrong is low.

Do you want to try this, or prefer me to have a go?


I'll do it during this week. I'm a bit strapped for time, but
should get to it.

Cheers


There are a few ways to finally fix this :

(a) move src/include/*.h to src/include/pcp/*.h and then change all
      code to e.g. #include<pcp/pmapi.h>, or

(b) change all affected code to e.g. #include "pmapi.h" rather than
      #include<pcp/pmapi.h>, or

(c) in src/include, symlink pcp ->  . (see attached patch).

We need to fix this - at the moment we're exposed to subtle errors
where some code is including /usr/include/pcp/*.h yet other code is
including those headers directly from the source tree.

I prefer (a), at least because our demo code is clean and consistent.

Thoughts?

-- Mark


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