hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-8037) Binary tarball does not preserve platform info for native builds
Date Wed, 08 Feb 2012 08:31:59 GMT
Binary tarball does not preserve platform info for native builds

                 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

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