[bug-notifications] [libiconv 0004726]: build is not thread-safe - errno issues

Mantis Bug Tracker noreply at opencsw.org
Thu Mar 17 08:09:48 CET 2011


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4726 
====================================================================== 
Reported By:                huginn
Assigned To:                dam
====================================================================== 
Project:                    libiconv
Issue ID:                   4726
Category:                   regular use
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2011-03-16 17:44 CET
Last Modified:              2011-03-17 08:09 CET
====================================================================== 
Summary:                    build is not thread-safe - errno issues
Description: 
errno in libiconv latest build is a simple global variable

[amok at border](1)~/$ nm /opt/csw/lib/amd64/libiconv.so | grep errno
[954]   |             0|           0|OBJT |GLOB |0    |UNDEF  |errno

Programs build with thread-safe errno fail on errno check
when iconv() returns with non zero value and should set errno.

Package from blastwave.org is build with thread-safe errno BTW.

[amok at border](1)~/$ nm /opt/csw/lib/amd64/libiconv.so | grep errno
[1314]  |             0|           0|FUNC |GLOB |0    |UNDEF  |___errno

====================================================================== 

---------------------------------------------------------------------- 
 (0008921) dam (administrator) - 2011-03-17 08:09
 https://www.opencsw.org/mantis/view.php?id=4726#c8921 
---------------------------------------------------------------------- 
The symlinks on *.so are deliberately missing as they are useful only when
compiling against the library to find the right version. An application
linking to it would pick up the SONAME and link against that at runtime.
The symlinks are therefore in the development package libiconv_dev.

Best regards -- Dago



More information about the bug-notifications mailing list