🚀 go-pugleaf

In article <4e4l36$1dp@mr-skullhead.cs.utexas.edu>, duckskip@cs.utexas.edu
(Alva Lease Duckwall IV) wrote:

> I recently sucessfully compiled/installed gcc 2.7.2 and then decided to 
> try to install glibc1.09
> 
> 
> 
> well i tried to configure/compile but I keep getting the same
> error message.
> 
> I checked out the Makeconfig file and all the defaults seemed to apply,
> so I just touch'd configparms.
> 
> I did:
> 
> mkdir sun4
> cd sun4
> ../configure
> touch configparms
> 
> (after it whirred and churned)
> make lib
> 
> and it died on version.c with "stdio/stdio.h:167 parse error before 
> 'void' "
> 
> i looked in the .h file and there didn't seem to be any problem.
> 
> any help would be appreciated, or if somebody could point me to 
> precompiled binaries, i'd be very grateful..
> 
> thanks!
> 
> skip duckwall
> duckskip@cs.utexas.edu


Chuck,

What a coincidence! I stumbled the same day over the same line of code. As
far as I have figured out the problem is predefined word "NORETURN" that
precedes the key word "void" (Your compiler complained very accurately ;) )
It depends on your settings (version of gcc >= 2.7) but in my case "NORETURN"
stands for "__attribute__ (( __volatile__ ))". This is defined in
./misc/sys/cdefs.h. (I came across the same problem with "CONSTVALUE")
After some grepping around I found in "info.gcc-9" a description of the
attribute modifier. In the examples that go with it, this modifier is always
placed after the function, like:

               void some_function(some_args) __attribute__ ((__volatile__))

In this spirit I changed the offending line in stdio.h:167 from
               extern __NORETURN void __libc_fatal __P(( args )); 
to:
               extern void __libc_fatal __P(( args )) __NORETURN;
and, lo and behold, this did the trick.

Though, it is not a nice solution: I'm now in the process of constantly
changing my code in this way (also for "CONSTVALUE"), which is quite
time consuming. Besides this kind of changes or difficult to make correctly
in cases of expanding predifined code. At this time don't know how to change
the code in __math.h.

Maybe somebody knows an easier way of coming accros this problem.

It bothers me, because I have a gcc-2.7.0 compiler and I hoped not to
have such kinds of trouble. Oh, well..

If you find a solution, I'd like to hear from you.

Good luck, 
Jan Vos (vos@nesta.biol.ruu.nl)