public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: "Anthony Feick" <afeick@hotmail.com>
Cc: rup@kanat.pair.com, rschiele@uni-mannheim.de, gcc@gcc.gnu.org,
	jakub@gcc.gnu.org
Subject: Re: gcc 3.2 on Solaris 8 (libgcc_s.so problem)
Date: Tue, 20 Aug 2002 16:51:00 -0000	[thread overview]
Message-ID: <15714.54791.665985.621199@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <F251TKf4BDibt9d4TRO0001f55a@hotmail.com>

Anthony Feick writes:

> I tried the Sun linker and assembler in "/usr/ccs/bin".  With them I can at 
> least run a simple program, but now there are problems linking source files 
> that use "std::basic_string<wchar_t>".

Do you have a simple testcase that fails for you?  Then please file a bug
(via gccbug) so this can be investigated.

> I'm sure I'll get it going eventually.  I just found out I need another 
> configure flag "--enable-cxx-flags="-fshort-wchar".  Thank you for your 
> help.

This seems terribly wrong: the gcc/g++ defaults for wchar_t match what
Solaris 8 has in <iso/wchar_iso.h>, while the -fshort-wchar flag changes
wchar_t to short, creating an incompatibility with system functions.

Why do you think you need this?

	Rainer

  reply	other threads:[~2002-08-20 16:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 16:37 Anthony Feick
2002-08-20 16:51 ` Rainer Orth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-22 11:01 Anthony Feick
2002-08-21  8:50 Anthony Feick
2002-08-21 13:12 ` Bernd Jendrissek
2002-08-20 17:35 Anthony Feick
2002-08-20 18:51 ` Rainer Orth
2002-08-20  8:35 Anthony Feick
2002-08-20  8:39 ` Rainer Orth
2002-08-21  3:16 ` Bernd Jendrissek
2002-08-20  1:17 Anthony Feick
2002-08-20  6:11 ` Robert Schiele
2002-08-20  6:29   ` Rupert Wood
2002-08-20  7:39     ` Rainer Orth

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=15714.54791.665985.621199@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=afeick@hotmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@gcc.gnu.org \
    --cc=rschiele@uni-mannheim.de \
    --cc=rup@kanat.pair.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).