Received: from osprey.astro.umass.edu (root@osprey.astro.umass.edu [128.119.51.182]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA37074; Sun, 24 Oct 1999 09:16:19 -0400 (EDT) (envelope-from weinberg@osprey.astro.umass.edu) Received: from osprey.astro.umass.edu (weinberg@localhost [127.0.0.1]) by osprey.astro.umass.edu (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA26493; Sun, 24 Oct 1999 09:16:12 -0400 Message-Id: <199910241316.JAA26493@osprey.astro.umass.edu> To: Bruce Momjian cc: oleg@pine.krs.ru, vadim@krs.ru, pgsql-interfaces@postgreSQL.org, pgsql-general@postgreSQL.org, weinberg@osprey.astro.umass.edu Subject: Re: [GENERAL] Re: Errors in Postgres In-reply-to: Your message of "Sun, 24 Oct 1999 08:42:53 EDT." <199910241242.IAA14822@candle.pha.pa.us> Date: Sun, 24 Oct 1999 09:16:12 -0300 From: Martin Weinberg Bruce Momjian wrote on Sun, 24 Oct 1999 08:42:53 EDT >This is a standard C++ problem. Some platforms need string.h, and some >just string. We have not figured out a way to make this work on all >platforms. > >Any ideas? We kept switching them back and forth until we realized >this. Sun's seem to have the problem. > >At this point, and OS-specific test would probably be OK. > Yes, this has been trouble everywhere. I believe is ANSI. In the latest gnulibs, the old libg++ is replaced by stdc++ which should have "string" defined. For what it's worth, this works on one of our sparc solaris boxes with gcc 2.8.1. Although it may well be something else, you might check to make sure that you have the latest version of the gnu g++ libraries. FYI, in the gnu implemenation, the "string" header is just an include of the original "string.h" but at least it's conforming. --Martin