public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rittle@latour.rsch.comm.mot.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/11170] bug in ctype_inline.h header file (undefined __istype will break compilation)
Date: Thu, 12 Jun 2003 22:18:00 -0000	[thread overview]
Message-ID: <20030612221800.391.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030612095704.11170.ronald@landheer.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11170



------- Additional Comments From rittle@latour.rsch.comm.mot.com  2003-06-12 22:17 -------
Subject: Re:  New: bug in ctype_inline.h header file (undefined __istype will break compilation)

In article <20030612095704.11170.ronald@landheer.com> you write:

> $ ../src/configure [...] --target=i386-unknown-freebsd4.7 --with-newlib [...]
> [...] Make produced a number of errors due to missing header files [...]

This is not a supported configuration at the moment (this is true for
many "UNIX" cross-targets within libstdc++-v3 AFAIK).  I have no
opinion on whether the above should or should not be supported but we
will review any patches posted to the libstdc++ list to improve that
situation.  For one thing, AFAIK, the libstdc++-v3 configuration
method looks at target triple without regard to presence of
--with-newlib to decide which configuration files to select.  Those
selected files clearly use knowledge of the target OS and expect
system headers to be present not newlib headers.

I.e. if there is a bug, then I suggest it is not in:
libstdc++-v3/config/os/bsd/freebsd/ctype_inline.h
rather it is in the selection process in:
libstdc++-v3/configure* (which should be selecting
libstdc++-v3/config/os/newlib/ctype_inline.h et al. in the presence
of --with-newlib).

Ah, BTW, you thought it was an error to use __istype before checking
it to guard the use of another entity called __maskrune.  That is
not-a-bug (you will have to study the *full* history of
/usr/include/ctype.h on freebsd to understand why).

Regards,
Loren (with both libstdc++-v3 and freebsd maintainer hat on)


  parent reply	other threads:[~2003-06-12 22:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12  9:57 [Bug c++/11170] New: " ronald@landheer.com
2003-06-12 10:17 ` [Bug libstdc++/11170] " giovannibajo@libero.it
2003-06-12 22:18 ` rittle@latour.rsch.comm.mot.com [this message]
2003-06-13  8:33 ` ronald@landheer.com
2003-08-06  3:56 ` pinskia at physics dot uc dot edu
2003-08-06  8:19 ` blytkerchan at users dot sourceforge dot net
2003-08-20 22:11 ` pinskia at gcc dot gnu dot org
2003-08-23  0:26 ` dhazeghi at yahoo dot com
2004-05-26  4:15 ` bkoz at gcc dot gnu dot org

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=20030612221800.391.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).