[bug-notifications] [libiconv 0004726]: build is not thread-safe - errno issues
Mantis Bug Tracker
noreply at opencsw.org
Wed Mar 16 19:54:23 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-16 19:54 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
======================================================================
----------------------------------------------------------------------
(0008918) dam (administrator) - 2011-03-16 19:54
https://www.opencsw.org/mantis/view.php?id=4726#c8918
----------------------------------------------------------------------
Thanks for the report! I have made experimental packages with _REENTRANT
set and split according to the current standard available at
http://buildfarm.opencsw.org/experimental.html#libiconv
Please give them a try and let me know if encounter any issues.
Best regards -- Dago
More information about the bug-notifications
mailing list