Path: utzoo!telly!ddsw1!lll-winken!killer!mit-eddie!bloom-beacon!tut.cis.ohio-state.edu!rutgers!labrea!polya!weening@Gang-of-Four.Stanford.EDU
From: weening@Gang-of-Four.Stanford.EDU (Joe Weening)
Newsgroups: gnu.gcc
Subject: Re: GCC/stdio interaction (ultrix, maybe others)
Message-ID: <5440@polya.Stanford.EDU>
Date: 3 Dec 88 01:29:19 GMT
References: <7747@boring.cwi.nl>
Sender: news@polya.Stanford.EDU
Reply-To: weening@Gang-of-Four.Stanford.EDU (Joe Weening)
Organization: Stanford University
Lines: 13
In-reply-to: jack@cwi.nl (Jack Jansen)

In article <7747@boring.cwi.nl>, jack@cwi (Jack Jansen) writes:
>
>The following is probably not a bug in GCC, but in Ultrix (and maybe
>other) stdio. However, gcc triggers the bug because it stores
>strings in read-only space.
> ...

I encountered this when compiling the window manager "twm" for X11R3,
and it may happen on other X11 programs as well.  This was under Sun
OS 4.0, by the way.  Adding "-fwritable-strings" to the GCC options
avoids the problems, however.
--
Joe Weening                                Computer Science Dept.
weening@Gang-of-Four.Stanford.EDU          Stanford University