hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6069) Remove explicit dynamic loading of libz in native code
Date Thu, 09 Jul 2009 00:07:14 GMT

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

Todd Lipcon commented on HADOOP-6069:
-------------------------------------

The advantage is a significant cleanup of both the autotools and source. I don't see any advantage
to dynamically loading libz - zlib is installed on pretty much every Linux system I've ever
seen. HADOOP-4652 also seems to depend on libz. If it needs to be updated so it doesn't conflict,
I'm happy to do that.

> Remove explicit dynamic loading of libz in native code
> ------------------------------------------------------
>
>                 Key: HADOOP-6069
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6069
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-6069-guts.txt, hadoop-6069.txt
>
>
> The native zlib code currently uses dlopen/dlsym to dynamically load libz. This used
to make sense when there was an lzo option (so you could load libhadoop for lzo purposes without
requiring libz as well). Now that libhadoop only has zlib as an option, it makes sense to
just add it as an ld flag and let it be automatically loaded as a shlib dependency. I also
doubt that there are any distros where libz isn't required by the base system.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message