Note, libhdfs now requires autoconf-2.61 and the binary is placed in c+ +/<os_osarch_jvmdatamodel>/lib

Nige

Begin forwarded message:

From: <[email protected]>
Date: December 16, 2008 12:21:30 AM PST
To: <[email protected]>
Subject: svn commit: r726983 [1/8] - in /hadoop/core/trunk: ./ src/c+ +/libhdfs/ src/c++/libhdfs/m4/ src/c++/libhdfs/tests/ src/c++/pipes/
Reply-To: [email protected]

Author: nigel
Date: Tue Dec 16 00:21:29 2008
New Revision: 726983

URL: http://svn.apache.org/viewvc?rev=726983&view=rev
Log:
HADOOP-3344. Fix libhdfs build to use autoconf and build the same architecture (32 vs 64 bit) of the JVM running Ant. The libraries for pipes, utils, and libhdfs are now all in c++/ <os_osarch_jvmdatamodel>/lib. Contributed by Giridharan Kesavan.

Added:
   hadoop/core/trunk/src/c++/libhdfs/Makefile.am   (with props)
   hadoop/core/trunk/src/c++/libhdfs/Makefile.in   (with props)
   hadoop/core/trunk/src/c++/libhdfs/aclocal.m4
   hadoop/core/trunk/src/c++/libhdfs/config.guess
   hadoop/core/trunk/src/c++/libhdfs/config.sub
   hadoop/core/trunk/src/c++/libhdfs/configure
   hadoop/core/trunk/src/c++/libhdfs/configure.ac
   hadoop/core/trunk/src/c++/libhdfs/depcomp
   hadoop/core/trunk/src/c++/libhdfs/install-sh
   hadoop/core/trunk/src/c++/libhdfs/ltmain.sh   (with props)
   hadoop/core/trunk/src/c++/libhdfs/m4/
   hadoop/core/trunk/src/c++/libhdfs/m4/apfunctions.m4
   hadoop/core/trunk/src/c++/libhdfs/m4/apjava.m4
   hadoop/core/trunk/src/c++/libhdfs/m4/apsupport.m4
   hadoop/core/trunk/src/c++/libhdfs/m4/libtool.m4
   hadoop/core/trunk/src/c++/libhdfs/m4/ltoptions.m4
   hadoop/core/trunk/src/c++/libhdfs/m4/ltsugar.m4
   hadoop/core/trunk/src/c++/libhdfs/m4/ltversion.m4
   hadoop/core/trunk/src/c++/libhdfs/m4/lt~obsolete.m4
   hadoop/core/trunk/src/c++/libhdfs/missing
Removed:
   hadoop/core/trunk/src/c++/libhdfs/Makefile
Modified:
   hadoop/core/trunk/CHANGES.txt
   hadoop/core/trunk/build.xml
   hadoop/core/trunk/src/c++/libhdfs/tests/test-libhdfs.sh
   hadoop/core/trunk/src/c++/pipes/configure
[snip]

Reply via email to