🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: gnu.g++.lib.bug
3 messages
3 total messages Started by Jaye Mathisen Thu, 21 Jan 1993 23:00
Still stumped with libg++-2.3 under Ultrix 4.3
#446
Author: Jaye Mathisen
Date: Thu, 21 Jan 1993 23:00
35 lines
2507 bytes
OK, I made a virgin install of gcc-2.3.3, both with and w/o the 
install-fixincludes, and in either case, I get the following: (which is
different than what I was getting earlier...)  Decstation 5000/240, Ultrix
4.3.

Any help again appreciated, I have no idea where to go.  I've never
had trouble building the other libg++'s, but this one is giving me fits.

gcc -g -O -nostdinc++ -I.. -I. -I./../iostream -I./../g++-include  -c AllocRing.cc
In file included from ./std.h:26, from AllocRing.cc:22:
./../g++-include/string.h:28: declaration of `long unsigned int  strlen (const char *)'
<built-in>:0: conflicts with built-in declaration `unsigned int  strlen (const char *)'
In file included from ./std.h:28, from AllocRing.cc:22:
./../g++-include/unistd.h:92: conflicting types for `int  geteuid (...)'
/usr/include/unistd.h:219: previous declaration of `short int  geteuid (...)'
./../g++-include/unistd.h:93: conflicting types for `int  getegid (...)'
/usr/include/unistd.h:204: previous declaration of `short int  getegid (...)'
./../g++-include/unistd.h:94: conflicting types for `int  getgid (...)'
/usr/include/unistd.h:205: previous declaration of `short int  getgid (...)'
./../g++-include/unistd.h:102: conflicting types for `int  getuid (...)'
/usr/include/unistd.h:220: previous declaration of `short int  getuid (...)'
./../g++-include/unistd.h:143: conflicting types for `long int  lseek (...)'
/usr/include/unistd.h:208: previous declaration of `int  lseek (...)'
./../g++-include/unistd.h:144: conflicting types for `long int  read (...)'
/usr/include/unistd.h:172: previous declaration of `int  read (...)'
./../g++-include/unistd.h:145: conflicting types for `long int  write (...)'
/usr/include/unistd.h:180: previous declaration of `int  write (...)'
make[2]: *** [AllocRing.o] Error 1
make[1]: *** [in-src] Error 1
make: *** [all-libg++] Error 1

-- 
 Jaye Mathisen, COE Systems Manager                (406) 994-4780
 410 Roberts Hall,Dept. of Computer Science
 Montana State University,Bozeman MT 59717	osyjm@cs.montana.edu
Re: Still stumped with libg++-2.3 under Ultrix 4.3
#449
Author: bothner
Date: Thu, 21 Jan 1993 23:22
7 lines
752 bytes
Most of these look like errors in libg++/_G_config.h.
Delete than file, and re-make it.  It should be consistent
with the system include files; otherwise tehre is a bug
in libg++/utils/gen-params.

	--Per Bothner
Cygnus Support     bothner@cygnus.com
Re: Still stumped with libg++-2.3 under Ultrix 4.3
#451
Author: Jaye Mathisen
Date: Fri, 22 Jan 1993 00:28
12 lines
1093 bytes
In article <1993Jan21.062636.845@coe.montana.edu> osyjm@cs.montana.edu (Jaye Mathisen) writes:

Well, it turns out the problem is either GNU sed-1.12, or GNU tr.  The
libg++/utils/gen-params file generated a bogus _G_config.h file.  I replaced
the definition of SED with /bin/sed, and the use of tr with /usr/bin/tr,
and now it's working just fine.

Thanks to Per for his help.  
-- 
 Jaye Mathisen, COE Systems Manager                (406) 994-4780
 410 Roberts Hall,Dept. of Computer Science
 Montana State University,Bozeman MT 59717	osyjm@cs.montana.edu
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads