Re: gcc 2.5.4 MIPS/ULTRIX v4.3

Article View: gnu.gcc.help

Article #49980

#49980

From: Michael Hohmuth
Date: Thu, 02 Dec 1993 18:34

24 lines
1712 bytes

In article <LIBOVE.93Nov28063621@foobil.ilo.dec.com>, libove@foobil.ilo.dec.com (Jay Vassos-Libove) writes:

> /usr/local/lib/gcc-lib/mips-dec-ultrix4.3/2.5.4/include/sys/types.h:106: syntax error before `char'

> typedef	volatile char		v_char;		/* line 106 */

> Any ideas on why this is happenning? Did I use the wrong
> compiler switches?  Did I miss something in the FAQ/README/
> INSTALL documentation?

This happens all the time when using -traditional with `gcc', because
`gcc' doesn't know "volatile" in traditional mode.

The `fixincludes' pass during the installation should probably #ifdef
out all those "volatile"s for -traditional.

A quick fix for you would be to compile `xv' without -traditional.
I have done so (with gcc 2.4.5) and experienced no problems (even though
the INSTALL documentation suggests using -traditional with `gcc').

Michael
--
Internet: hohmuth@freia.inf.tu-dresden.de

Technical Details

Message-ID: <2dlcfm$d77@irz402.inf.tu-dresden.de>

Path: arc1-ca.pugleaf.net!gmd.de!xlink.net!math.fu-berlin.de!news.tu-chemnitz.de!irz401!mh1

References: <LIBOVE.93Nov28063621@foobil.ilo.dec.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,902d7bf162509ff5
X-Google-Attributes: gid11318c,public
X-Google-ArrivalTime: 1993-12-02 11:35:18 PST
Path: arc1-ca.pugleaf.net!gmd.de!xlink.net!math.fu-berlin.de!news.tu-chemnitz.de!irz401!mh1
From: mh1@irz.inf.tu-dresden.de (Michael Hohmuth)
Newsgroups: gnu.gcc.help
Subject: Re: gcc 2.5.4 MIPS/ULTRIX v4.3
Date: 2 Dec 1993 19:34:30 +0100
Organization: Dept. of Computer Science, TU Dresden, Germany
Lines: 24
Distribution: world
Message-ID: <2dlcfm$d77@irz402.inf.tu-dresden.de>
References: <LIBOVE.93Nov28063621@foobil.ilo.dec.com>
Reply-To: hohmuth@freia.inf.tu-dresden.de
NNTP-Posting-Host: irz402.inf.tu-dresden.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Reply to Parent Message