[comp.windows.x] Bug in img 1.2 - exhibit.c and maint_back.c

mike@sam.ists.ca (Mike Clarkson) (03/11/90)

In  X.V11R4/contrib/clients/new/img/imgprogs/exhibit

there are defines like

#ifndef	hpux
#define	volatile	""
#endif

and then the use of vaolatile as a data type.  Gcc 1.35 doesn't like this.

(X11R4 PL 5, SunOS 3.5, gcc 1.35)

Mike.

*** exhibit.c.dst	Wed Mar  7 18:52:51 1990
--- exhibit.c	Sat Mar 10 19:53:03 1990
***************
*** 123,129 ****
  
  
  #ifndef	hpux
! #define	volatile	""
  #endif
  
  extern		rnd_init ();	/*  Initialize random number generator	*/
--- 123,129 ----
  
  
  #ifndef	hpux
! #define	volatile
  #endif
  
  extern		rnd_init ();	/*  Initialize random number generator	*/



*** maint_back.c.dst	Wed Mar  7 18:52:51 1990
--- maint_back.c	Sat Mar 10 19:53:35 1990
***************
*** 98,104 ****
  
  
  #ifndef	hpux
! #define	volatile	""
  #endif
  
  
--- 98,104 ----
  
  
  #ifndef	hpux
! #define	volatile
  #endif
  
  
Mike.

-- 
Mike Clarkson					mike@ists.ists.ca
Institute for Space and Terrestrial Science	uunet!attcan!ists!mike
York University, North York, Ontario,		FORTRAN - just say no. 
CANADA M3J 1P3					+1 (416) 736-5611

raveling@isi.edu (Paul Raveling) (03/14/90)

In article <108@sam.ists.ca>, mike@sam.ists.ca (Mike Clarkson) writes:
|> 
|> In  X.V11R4/contrib/clients/new/img/imgprogs/exhibit
|> 
|> there are defines like
|> 
|> #ifndef	hpux
|> #define	volatile	""
|> #endif
|> 
|> and then the use of vaolatile as a data type.  Gcc 1.35 doesn't like this.

	I'll fix this blunder in V1.3 to make that a null operand
	instead of a null string.  Until then folks with Suns & such
	will need to make that change manually.

	Something about BSDish systems needing to change this seems
	some sort of justice.  Or to put it another way, how many
	getcwd() calls have you BSD-based people had to change?
	We HP-UXers have to recode a fair number of getwd()'s.


----------------
Paul Raveling
Raveling@isi.edu