You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Giridharan Kesavan (JIRA)" <ji...@apache.org> on 2009/01/12 13:19:59 UTC
[jira] Updated: (HADOOP-2318) All C++ builds should use the
autoconf tools
[ https://issues.apache.org/jira/browse/HADOOP-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Giridharan Kesavan updated HADOOP-2318:
---------------------------------------
Attachment: hadoop-2318.patch
Except librecordio all other components are now ported to use autotools.
Here with submitting a patch that enables librecordio to use autotools
The compilation part works just fine, though the test compilation fails with error
And now as any other c++ component librecordio.a file is moved to a new location:
build/c++/<Linux>-<amd64>-<64>/lib/librecordio.a
[exec] Run test
[exec] Makefile:236: ../hadoop-core-trunk-librecordio/src/c++/librecordio/.deps/%.Po: No such file or directory
[exec] make[1]: *** No rule to make target `../hadoop-core-trunk-librecordio/src/c++/librecordio/.deps/%.Po'. Stop.
[exec] make: *** [test] Error 2
I need some pointers on solving this issue.
Thanks
Giri
> All C++ builds should use the autoconf tools
> --------------------------------------------
>
> Key: HADOOP-2318
> URL: https://issues.apache.org/jira/browse/HADOOP-2318
> Project: Hadoop Core
> Issue Type: Improvement
> Components: build
> Reporter: Nigel Daley
> Priority: Minor
> Attachments: hadoop-2318.patch
>
>
> Currently we have -Dcompile.native and -Dcompile.c++ build flags. In addition, builds for pipes and libhadoop use autoconf tools, but libhdfs does not, nor does 64bit libhdfs compile work.
> All these builds should use autoconf tools, support 64bit compilation, and should occur when a single flag is present (-Dcompile.c++ seems like the better choice).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.