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

Colin Patrick McCabe edited comment on HADOOP-11426 at 12/18/14 11:55 PM:
--------------------------------------------------------------------------

I really would prefer not to do this.  What's the problem with just installing 
the bzip2 development files?

edit:  I guess I should go into more detail about the reasons why I wouldn't 
like to do this:
* Consistency.  For all the other stuff we {{dlopen}}, we search for both the 
libraries and the headers.  Why should bzip2 behave differently than everything 
else?
* "Least surprise" to developers.  By searching for the library, we ensure that 
developers who successfully create a hadoop build with bzip2 can almost 
certainly run it on that same machine.
* Lack of a use-case.  Linux distributions usually supply two kinds of 
packages: development packges with both the header and the libraries, or 
production packages with just the library.  As far as I know, nobody supplies 
packages with just header files.

let me know if I missed anything or if there's a use-case I forgot!


was (Author: cmccabe):
I really would prefer not to do this.  What's the problem with just installing 
the bzip2 development files?

> Fix native bzip2 codec build dependency
> ---------------------------------------
>
>                 Key: HADOOP-11426
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11426
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>         Attachments: HADOOP-11426.patch
>
>
> In hadoop-common-project/hadoop-common/src/CMakeLists.txt, find_package() is 
> used to check whether bzip2 libraries and header are present.  However, the 
> library is loaded by libhadoop using dlopen(), not linked during build, so 
> the real build-time dependency is only on the header file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to