I built sigar from head last week to look into those problems. The internal
version is 1.6.6. And i have those functions:
objdump -x bindings/java/build/obj/amd64-linux/lib/libsigar-amd64-linux.so
| grep sigar_version
0000000000000000 l df *ABS* 0000000000000000
sigar_version.c
0000000000231840 l O .data 0000000000000048
sigar_version
00000000000180b0 g F .text 0000000000000008
sigar_version_get
[chris@wintermute sigar.git (sigar-1.6)]$ nm -a -C
bindings/java/build/obj/amd64-linux/lib/libsigar-amd64-linux.so | c++filt |
grep sigar_version
0000000000231840 d sigar_version
0000000000000000 a sigar_version.c
00000000000180b0 T sigar_version_get
I downloaded the fedora 1.6.5 and it seems a lot of symbols are missing:
objdump -x libsigar.so.debug | wc (from fedora)
620 3475 40200
objdump -x bindings/java/build/obj/amd64-linux/lib/libsigar-amd64-linux.so
| wc
793 4465 63587
2012/11/2 Denis Arnaud <[email protected]>
> Hi Doug,
>
>
> On Monday, 22 October 2012 17:38:50 UTC+2, Doug Judd wrote:
>>
>> The SIGAR library isn't available in a yum repository (last we checked).
>> We usually download it and install it "by hand". Take a look at our CentOS
>> 5<https://github.com/hypertable/hypertable/blob/master/bin/src-utils/build-setup-centos5.sh>build
>> setup instructions for how to install SIGAR. We're happy to host a
>> yum repository for SIGAR, if that's necessary for Fedora.
>>
>
> In fact, SIGAR is already packaged for Fedora (see
> https://admin.fedoraproject.org/pkgdb/acls/name/sigar). For instance, you
> can check on the RedHat mirror for Fedora
> 17<http://dl.fedoraproject.org/pub/fedora/linux/releases/17/Everything/x86_64/os/Packages/s/>:
>
> http://dl.fedoraproject.org/pub/fedora/linux/releases/17/Everything/x86_64/os/Packages/s/sigar-1.6.5-0.6.git58097d9.fc17.x86_64.rpmand
> http://dl.fedoraproject.org/pub/fedora/linux/releases/17/Everything/x86_64/debug/s/sigar-debuginfo-1.6.5-0.6.git58097d9.fc17.x86_64.rpm(for
> the object symbols).
> You will note that Fedora packagers have shipped a pre-release (1.6.5).
> However, the incriminated symbol, namely sigar_version_get, cannot be
> found in that version!
> $ nm -a -C /usr/lib/debug/usr/lib/libsigar.so.debug | c++filt | grep
> sigar_version
> [empty]
>
> And the library is not empty:
> $ nm -a -C /usr/lib/debug/usr/lib/libsigar.so.debug | c++filt | grep
> sigar_swap_get
> 00008d90 T sigar_swap_get
> $ nm -a -C /usr/lib/debug/usr/lib/libsigar.so.debug | wc -l
> 633
>
> So, apparently, either that symbol/API has been removed in the latest
> version of the SIGAR code, or Fedora packagers have done something wrong...
> I had a quick look at the SIGAR code, but could not find the source of the
> issue in the 10 minutes I dedicated to it. If you have some more insights,
> do not hesitate!
>
>
> One thing we've done to reduce the dependencies with our RPM package is to
>> include all of the dependent libraries in the installation. [...] This
>> makes it easy to install the package without having to worry about
>> dependencies. Is this something that is ok with Fedora? Also, there are a
>> lot of Java .jar files that we include in the package (Hadoop, thrift,
>> etc.). If we're allowed to include .jar files in the RPM, then the only
>> java-related dependencies would be Java itself and Hadoop.
>>
>
> No, bundling external projects (or even components or libraries) is
> forbidden. Everything, including the rationale, is explained on the
> dedicated Fedora Wiki page:
> https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries. That of
> course encompasses Java .jar files.
> That is why we have to package every single dependency, as suggested in
> https://fedoraproject.org/wiki/Hypertable
>
> If some volunteers want to help (co-)maintain some of the packages, please
> do not hesitate; I will of course support them.
>
> Kind regards
>
> Denis
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Hypertable Development" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/hypertable-dev/-/-OCCBIT3QSgJ.
>
> 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.
>
--
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.
