bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sed 4.0.8 build problem on HP-UX 11.11 with gcc 3.3.2


From: Stepan Kasal
Subject: Re: sed 4.0.8 build problem on HP-UX 11.11 with gcc 3.3.2
Date: Sat, 20 Dec 2003 16:21:10 +0100
User-agent: Mutt/1.4.1i

Hello,

On Fri, Dec 19, 2003 at 01:01:01PM -0600, Dano Carroll wrote:
> I've encountered a problem with building sed-4.0.8 on HP-UX 11.11. The
> problem seems to stem from a failure to include /usr/include/sys/_mbstate_t.h
> which /usr/include/wchar.h should do. I don't know enough about how to
> debug includes to figure out what was wrong. However, there is a
> thread on a similar problem with building on awk on HP-UX 11.11 which

I participated in that thread.  I have been convinced conclude that the
support for multibyte in HP-UX is incomplete, and that there is no easy
workaround, which would be general enough.

So I beleive that future versions of GNU awk will quietly build without
multibyte support.  (I may be wrong with this guess, I'm not the
maintainer of gawk.)

There are more ways to achieve this in the configure script, and we seem
to disagree on this particular detail with Michael, as he mentioned in
his answer.

To get to practical solutions: to use ``my approach'' to sed-4.0.8,
you could try the first of the patches attached to this mail.

It could be useful to try the latest beta test of sed,
        ftp://alpha.gnu.org/gnu/sed/sed-4.0b.tar.gz
I expect the same problem as with 4.0.8.  In that case, you should
apply the second of the patches attached to this mail (it's almost
the same as the first one).
But the post
http://mail.gnu.org/archive/html/bug-gnu-utils/2003-12/msg00095.html
indicates that another problem might appear.
In that case, we would be grateful, if you posted another bug report
to address@hidden  (Thanks in advance.)

Yours,
        Stepan Kasal

Attachment: sed-4.0.8-mbrtowc.patch
Description: Text document

Attachment: sed-4.0b-mbrtowc.patch
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]