On 10 October 2014 08:52, Predrag Punosevac <[email protected]> wrote:
> Stuart Henderson <[email protected]> wrote:
>
>> On 2014/10/09 08:44, Predrag Punosevac wrote:
>> > I am trying to build collectd on the snapshot from a 10 of August which
>> > should be very close to November 1st release.
>> >
>> > # uname -a
>> > OpenBSD oko.bagdala2.net 5.6 GENERIC.MP#333 amd64
>> >
>> >
>> >
>> > As some of you know collectd package depends on rrdtool  which in turn
>> > depends on package rrdupdate.
>> >
>> > # ls -l rrdtool
>> > total 28
>> > drwxr-xr-x  2 root  wheel   512 Aug 11 13:41 CVS
>> > -rw-r--r--  1 root  wheel  3296 Aug 10 13:33 Makefile
>>
>> That file ^^ is an old version, there have been several commits to it
>> since August.
>>
>> > -rw-r--r--  1 root  wheel   115 Oct  9 02:07 distinfo
>> > drwxr-xr-x  3 root  wheel   512 Apr  6  2014 files
>> > drwxr-xr-x  3 root  wheel   512 Mar  5  2014 patches
>> > drwxr-xr-x  3 root  wheel   512 Jun 14 13:14 pkg
>> >
>> >
>> >
>> > During the build I get this error
>> >
>> >
>> > Error:
>> > /usr/ports/pobj/rrdtool-1.4.8/fake-amd64/usr/local/ \
>> > lib/ruby/site_ruby/2.0/x86_64-openbsd/RRD.so does not exist
>> >
>> > That is indeed the case. That looks like what this fella was getting
>> >
>> > https://www.mail-archive.com/[email protected]/msg130224.html
>> >
>> > Is there a work around this problem?
>> >
>> > Most Kind Regards,
>> > Predrag
>> >
>>
>> "cvs up -PdA" and try building again.
>>
>
> Are you sure that this is a good idea? I am not trying to follow
> current? If I check out current port tree I will have to rebuild
> everything. I am just trying to build a single port using a port
> snapshot and the sytem from 10 of August which are suppose to be epsilon
> close to 5.6 release. Is rrdtool package broken for 5.6 release?
>
> Most Kind Regards,
> Predrag
>

You really need to be either working with the 5.6-release (cvs
-d$CVSROOT checkout -rOPENBSD_5_6 -Pd) or have base and ports sync'd
to -current.  The mismatch (using varying snapshots) will cause issues
and if there was a build issue that you described above, would have
been discovered as part of the bulk build for 5.6-release.

Jason.

Reply via email to