OK, looks like you built sigar yourself, the binary packages actually
use amd64. Will apply the changes. Thanks.

On Sat, Aug 1, 2009 at 2:22 PM, Linas Vepstas<[email protected]> wrote:
>
> 2009/8/1 Luke <[email protected]>:
>>
>> Interesting, which sigar distribution are you using? 1.60-1.62 all use
>> amd64 instead of x86_64.
>
> I'm using  hyperic-sigar-1.6.2
>
> I haven't dug into it, but I assume that the suffix that is used depends
> on how the OS and/or Java identifies itself.  Even though I'm running
> on amd Athalons, the sigar build went into
>
> ./bindings/java/sigar-bin/lib/libsigar-x86_64-linux.so
> ./bindings/java/build/obj/x86_64-linux
>
> and so on.  I didn't look to see why sigar thinks that this is the right
> name.  FWIW, I run Ubuntu Intrepid.
>
> --linas
>
>> On Sat, Aug 1, 2009 at 11:47 AM, Linas Vepstas<[email protected]> wrote:
>>>
>>> Today's git pull of hypertable fails finding SIGAR. The patch below
>>> fixes this for me.  Please apply!
>>>
>>> Signed-off-by: Linas Vepstas <[email protected]>
>>>
>>> diff --git a/cmake/FindSIGAR.cmake b/cmake/FindSIGAR.cmake
>>> index 7420373..82ae44a 100644
>>> --- a/cmake/FindSIGAR.cmake
>>> +++ b/cmake/FindSIGAR.cmake
>>> @@ -19,7 +19,7 @@ find_path(SIGAR_INCLUDE_DIR sigar.h
>>>
>>>  # SIGAR support a lot more platforms than listed here.
>>>  # cf. sigar.hyperic.com
>>> -set(SIGAR_NAMES sigar-x86-linux sigar-amd64-linux sigar-universal-macosx)
>>> +set(SIGAR_NAMES sigar-x86-linux sigar-x86_64-linux sigar-amd64-linux
>>> sigar-universal-macosx)
>>>  find_library(SIGAR_LIBRARY
>>>   NAMES ${SIGAR_NAMES}
>>>   PATHS /usr/lib /usr/local/lib /opt/local/lib
>>>
>>> >
>>>
>>
>> >
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Hypertable Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/hypertable-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to