From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: brobecker@gnat.com
Cc: gdb@sources.redhat.com
Subject: Re: [Fwd: native hppa2.0w-hp-hpux11.11]
Date: Tue, 09 Dec 2003 00:28:00 -0000 [thread overview]
Message-ID: <20031209002837.D91134B412@berman.michael-chastain.com> (raw)
I'm getting a similar error to you, with mbrtowc (not mbsrtowc).
Did you get a response back from bash-maintainers on your patch?
Our solutions are different. Your solution is to add more checks
so that hpux will properly not be multi-byte. My solution is
to add a README.hpux file which tells the user to do this:
CPPFLAGS=-D_XOPEN_SOURCE=500 configure
Come to think of it, both parts are valid. The autoconfiguration stuff
should be set up the way you like, and then, if people want I18N support
on HP, _XOPEN_SOURCE should enable it.
Here's the HP reference on this:
http://www.docs.hp.com/hpux/onlinedocs/5187-3605/00/00/1-con.html
> In my mind, hpux-10.20 was already no longer supported by GDB :-).
Well, that makes it 2-0. But Andrew has seven votes. :)
Michael C
next reply other threads:[~2003-12-09 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 0:28 Michael Elizabeth Chastain [this message]
2003-12-12 22:39 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 23:53 Michael Elizabeth Chastain
2003-12-09 0:03 ` Joel Brobecker
2003-12-08 23:27 Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031209002837.D91134B412@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=brobecker@gnat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox