hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8037) Binary tarball does not preserve platform info for native builds, and RPMs fail to provide needed symlinks for libhadoop.so
Date Thu, 09 Feb 2012 02:57:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204209#comment-13204209

Matt Foley commented on HADOOP-8037:

I'm still seeing the above problem (extra copies of certain 64-bit native libs in the bin-tarball),
but Giri doesn't see it in his environment.

This patch resolves the two dangerous problems, and leaves only a minor glitch in the bin-tarball,
which is a new artifact that few people are known to use.  I'm going to accept this patch,
and move the remaining issue into a new bug, to be resolved in the future.

+1, thanks Giri!

> Binary tarball does not preserve platform info for native builds, and RPMs fail to provide
needed symlinks for libhadoop.so
> ---------------------------------------------------------------------------------------------------------------------------
>                 Key: HADOOP-8037
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8037
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.0.1
>            Reporter: Matt Foley
>            Assignee: Giridharan Kesavan
>         Attachments: hadoop-8027-1.patch, hadoop-8037-1.patch, hadoop-8037.patch
> The source tarball uses "package" ant target, which includes both sets of native builds
(32 and 64 bit libraries), under subdirectories that are named for the supported platform,
so you can tell what they are.
> The binary tarball uses the "bin-package" ant target, which projects both sets of native
builds into a single directory, stripping out the platform names from the directory paths.
 Since the native built libraries have identical names, only one of each survives the process.
 Afterward, there is no way to know whether they are intended for 32 or 64 bit environments.
> It seems to be done this way as a step toward building the rpm and deb artifacts.  But
the rpms and debs are self-identifying as to the platform they were built for, and contain
only one set of libs each, while the binary tarball isn't.  The binary tarball should have
the same platform-specific subdirectories that the full tarball does; but this means that
the rpm and deb builds have to be more careful about include/exclude specs for what goes into
those artifacts.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message