[MLton-devel] Re: [Twelf-developer] Twelf and MLton

[Henry Cejtin]

Here  is something I saw on some Linux newsgroups about the Red Hat 8.1 glibc
problems.  There isn't any indication of what the errno problem is, but  more
importantly  it  isn't  clear  if it is going to get `fixed' by Red Hat or we
will have to work around it.

>From: "Duke" <thisis@bogus.com>
>Newsgroups: linux.redhat,linux.redhat.misc,linux.redhat.rpm,redhat.general,redhat.rpm.general
>Subject: RH glibc-2.3.1-6+ RPMs broken (errno)
>Date: Fri, 7 Feb 2003 12:03:52 -0500
>Organization: Posted via Supernews, http://www.supernews.com
>Message-ID: <v47q6uem0ghmd3@news.supernews.com>
>X-Complaints-To: abuse@supernews.com
>Xref: news.acns.nwu.edu redhat.general:20989 redhat.rpm.general:1128
>
>I am surprised how little (none?) conversation/info there is on this
>subject.  The current RedHat Rawhide RPMs of glibc 2.3.1 are broken.  This
>includes any release newer than glibc-2.3.1-5.  Running them even tell you
>they are broken (from 2.3.1-41):
>
>[duke@erbium duke]$ /lib/libc.so.6
>Incorrectly built binary which accesses errno, h_errno or _res directly.
>Needs to be fixed.
>GNU C Library stable release version 2.3.1, by Roland McGrath et al.
>Copyright (C) 2003 Free Software Foundation, Inc.
>This is free software; see the source for copying conditions.
>There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
>PARTICULAR PURPOSE.
>Compiled by GNU CC version 3.2.1 20030202 (Red Hat Linux 8.0 3.2.1-7).
>Compiled on a Linux 2.4.20 system on 2003-02-05.
>Available extensions:
>        GNU libio by Per Bothner
>        crypt add-on version 2.1 by Michael Glad and others
>        linuxthreads-0.10 by Xavier Leroy
>        BIND-8.2.3-T5B
>        libthread_db work sponsored by Alpha Processor Inc
>        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
>Thread-local storage support included.
>Report bugs using the `glibcbug' script to <bugs@gnu.org>.
>
>The problem is with errno.  This breaks some packages and does not allow you
>to compile others w/o patching first.  This includes software like PHP,
>Postfix & Cyrus (when using mysql support).
>
>I wrote a patch for PHP/MySQL 4.0.9, I don't want to patch all software in
>order to get it running.  To build PHP 4.3.0 and Postfix/Cyrus w/ MySQL
>support in order to have them work with the current Rawhide glibc-2.3.1-41,
>I have to do no less than:
>
>Patch mysql 4.x, then build manually
>Build PHP, linking against above
>Patch mysql 3.x (pam_mysql only seems to run w/ 3.x because of a missing
>symbol in 4.x's libmysqlclient), then build manually
>Build Postfix & Cyrus, linking against above
>
>..and if I want to run anything else that is coded with
>extern int errno;
>I must manually patch it.  The chain only gets longer when you are building
>something that depends on some other thing that uses this - you must rebuild
>the dependent libs before you can link against them.
>
>My question is.. WHY?  I have noticed Debian also experienced this (current
>status unknown to me) - is the GNU libc changing in this respect or what?
>If it is, why the "Incorrectly built binary .. Needs to be fixed" message?
>If not, why fsck with us like this?  And what is RedHat doing to address
>this issue?


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel