Re: compiling glib-1.2.7

[Kevin Handy <kth srv net>]

On some versions of Linux, the header files have bad code for the 
FD_SET series of macros that causes this problem. To fix it, you need
to update your header files with working versions. Sometimes you
can just change a #if so that is uses the non-asm version.

This is mentioned somewhere in the documentation of gcc-2.95, including
the correct fix to the asm code, but I'm currently not sure of where.


Owen Taylor wrote:
> 
> Loban Rahman <loban@enigma.caltech.edu> writes:
> 
> > I get the following error compiling glib-1.2.7 using gcc-2.9.5
> >
> > gcc -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=g_log_domain_glib -DG_ENABLE_DEBUG -I/home/loban/usr/include -I/usr/include -I/usr/ug/include -I/home/loban/usr/include -I/usr/include -I/usr/ug/include -Wall -D_REENTRANT -Wp,-MD,.deps/gerror.pp -c gerror.c  -fPIC -DPIC -o .libs/gerror.lo
> > gerror.c: In function `stack_trace':
> > gerror.c:237: Invalid `asm' statement:
> > gerror.c:237: fixed or forbidden register 2 (cx) was spilled for class CREG.
> 
> This probably means that your compiler is mismatched with your
> binutils, or some such thing. It has nothing to do with glib or
> gerror.c.
> 
> And plenty of people compile GLib with GCC 2.95 (which is, I assume,
> what you mean, not 2.9.5).