Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.23.1
-
None
-
None
-
None
Description
In branch-1, found and fixed following issues:
- binary tarball target was incorrectly persisted from the rpm-generating dir structure, but should have been regular tarball dir structure minus docs and sources
- rpm-generating dir structure may be persisted as bin-tarball with platform-specific tag (like rpms)
- native libs built for 64-bit platform should go in "lib64" rather than "lib" directory
- platform-specific tags for rpms and debs (and bin-tarballs as above) should be "i86_64", not "amd64"
- consider whether "i86_64" should be used in certain directory paths, too.
Need to check trunk / v0.23 for related issues, although they'll be different due to different build env.
Attachments
Issue Links
- is related to
-
HADOOP-8037 Binary tarball does not preserve platform info for native builds, and RPMs fail to provide needed symlinks for libhadoop.so
- Closed
-
HADOOP-8132 64bit secure datanodes do not start as the jsvc path is wrong
- Closed
-
HADOOP-8090 rename hadoop 64 bit rpm/deb package name
- Closed