I actually changed my path so that /usr/include/sys/ occurred before the blahblah.../gcc-lib/sparc-sun-solaris2.5/2.7.2 directory, and successfully made it past the siginfo.h error. However, I am now presented with a problem in gutils.c: [59] gregoryl@sunray7: make make all-recursive Making all in . /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=g_log_domain_glib -g -O2 -Wall -D_REENTRANT -c gutils.c rm -f .libs/gutils.lo gcc -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=g_log_domain_glib -g -O2 -Wall -D_REENTRANT -c -fPIC -DPIC gutils.c -o .libs/gutils.lo gutils.c: In function `g_get_any_init': gutils.c:477: too many arguments to function `getpwuid_r' gutils.c:477: warning: assignment makes integer from pointer without a cast gutils.c:498: warning: int format, uid_t arg (arg 4) *** Error code 1 make: Fatal error: Command failed for target `gutils.lo' Current working directory /home/gregoryl/tools/glib-1.2.6 *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /home/gregoryl/tools/glib-1.2.6 *** Error code 1 make: Fatal error: Command failed for target `all-recursive-am' I tried upgrading gcc to version 2.95.2 as suggested, but it also failed on build with this error: gcc -c -DIN_GCC -DSVR4 -g -O2 -I. -I.. -I. -I./.. -I./../config -I./../../include jcf-write.c jcf-write.c: In function `make_class_file_name': jcf-write.c:3023: too few arguments to function `mkdir' *** Error code 1 make: Fatal error: Command failed for target `jcf-write.o' Current working directory /home/gregoryl/tools/gcc-2.95.2/gcc/java *** Error code 1 make: Fatal error: Command failed for target `jc1' Current working directory /home/gregoryl/tools/gcc-2.95.2/gcc *** Error code 1 make: Fatal error: Command failed for target `all-gcc' So, it seems I'm having no luck. The build processes for both glib and gcc proceeded quite a ways before exiting. I feel I'm close to getting it, but this is where I'm stuck. Sorry about the HTML in my last email. -Greg Lindsay > On Wed, 09 Feb 2000 19:26:41 -0700, Greg Lindsay wrote: > > I'm attempting to install glib 1.2.6 in my homedir under Solaris 2.7.2, but I > > keep getting a parse error (see below). I'm unsure if the error is related to > > the fact that siginfo.h is located in /usr/include/sys, whereas the other > > includes are in > > /usr/dist/local/share/tom/gnu/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2/include. > > If I view siginfo.h, it looks fine. I don't see any parse errors in the > > described structure - perhaps I'm wrong. Has anyone run into this before? Any > > suggestions? > > > > > > [4:39pm] 4 [~/tools/glib-1.2.6]:sunray7% make > > make all-recursive > > Making all in . > > /usr/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. > > -DG_LOG_DOMAIN=g_log_domain_glib -g -O2 -Wall -D_REENTRANT -c gdate.c > > rm -f .libs/gdate.lo > > gcc -DHAVE_CONFIG_H -I. -I. -I. -DG_LOG_DOMAIN=g_log_domain_glib -g -O2 -Wall > > -D_REENTRANT -c -fPIC -DPIC gdate.c -o .libs/gdate.lo > > In file included from > > /usr/dist/local/share/tom/gnu/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2/include/ti > > e.h:90, from gdate.c:37: > > /usr/include/sys/siginfo.h:74: parse error before `pthread_attr_t' > > /usr/include/sys/siginfo.h:74: warning: no semicolon at end of struct or union > > /usr/include/sys/siginfo.h:76: parse error before `}' > > *** Error code 1 > > make: Fatal error: Command failed for target `gdate.lo' > > Current working directory /home/gregoryl/tools/glib-1.2.6 > > *** Error code 1 > > make: Fatal error: Command failed for target `all-recursive' > > Current working directory /home/gregoryl/tools/glib-1.2.6 > > *** Error code 1 > > make: Fatal error: Command failed for target `all-recursive-am' > > Don't use a gcc compiler configured for Solaris 2.5 on Solaris 2.7. The > gcc build process fixes the broken system header files on your system. > Each OS release contains other broken header files, so the system header > files and the fixed ones are no longer in sync. > > Another problem might be the ancient gcc compiler release. While it is > quite safe to use gcc-2.7.2 on Linux (mainly because the kernel can't be > build with newer gcc versions, although that problem is fixed in the 2.3 > kernels), other OSes should really upgrade to gcc-2.95.2. Being a merge > between egcs and gcc, gcc-2.95.2 is considered the best gcc ever. Have a > look at http://gcc.gnu.org/ . > > > Erik > > PS: Please don't use HTML mail. It doubles the size of the message without > adding extra functionality. > > -- > J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department > of Electrical Engineering, Faculty of Information Technology and Systems, > Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands > Phone: +31-15-2785859 Fax: +31-15-2781843 Email [EMAIL PROTECTED] > WWW: http://www-ict.its.tudelft.nl/~erik/ > > > > -- > To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > -- To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
