[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strings.h in argz.c?
From: |
Paul Eggert |
Subject: |
Re: strings.h in argz.c? |
Date: |
Sun, 21 Jan 2007 14:02:22 -0800 |
User-agent: |
Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
Ralf Wildenhues <address@hidden> writes:
> We got a bug report about Libtool 1.5.22 and SunOS 4.1.x this year, so
> I'm not doing any C89 cleanup on branch-1-5.
"this year" meaning 2007? Or in the last 12 months?
I searched for such a bug report and found only
<http://lists.gnu.org/archive/html/bug-libtool/2006-06/msg00021.html>
which mentions m68k SunOS 4.1.1 and sparc sunos 4.1.4. However, in
<http://lists.gnu.org/archive/html/bug-libtool/2006-06/msg00025.html>
you asked "Does anybody actually use these systems outside of a
museum?", noting that Sun itself dropped support for these operating
systems long ago, and didn't get a response.
I just checked
<http://www.sun.com/service/eosl/solaris/solaris_vintage_eol_5.2005.xml>,
and Sun stopped fixing bugs in SunOS 4.1.1 on 1997-01-06 and in SunOS
4.1.4 on 2000-09-30, and stopped giving advice about them on
2000-01-76 and 2003-09-30 respectively.
Obviously it's up to you as to whether to do C89 cleanup, but if that
bug report is what we're talking about, I wouldn't worry about it.
On the other hand, is libtool supposed to address the problem of
freestanding C compilers? If so, the only headers it is allowed to
assume are <float.h>, <limits.h>, <stdarg.h>, and <stddef.h>. If
memory serves, gnulib sometimes assumes freestanding, but more often
hosted.