On Tue, 2003-07-08 at 14:55, Florian St=F6hr wrote:
> If you want to use any pkg version (stlport, for example) of the STL,=20
> you have to compile your program with
>=20
> -I/usr/pkg/include/stlport
>=20
> or whatever. Otherwise the GCC will use it's own STL files.
>=20
> I have done this several times and it works perfectly with all STL=20
> versions, under NetBSD 1.6

I used STLport under 2.95.3 and that worked, but somehow
gcc 3.2.1 didn't like the include switch you mention.
However, removing that, and thus letting gcc use it's
own STL files, made the errors vanish.

As for my other question: in an other operating system
that I used some time ago, most system API:s were C++-based,
not C-based, and that caused a big problem when gcc moved
to version 3. This was because some reason I don't quite
understand. As I remember it was something about a
calling convention or ABI change between gcc 2 and 3, which
forced the other OS maker to stay with gcc 2.95 (or break
binary compatiblity, I think).

Is this also true for NetBSD? If not (I guess not), why is NetBSD
shipping with 2.95.3 and not some 3.x version?

--=20
Thorbj=F6rn Jemander =20
thje@enea.se, +46 13 465 58 67,
Enea Epact AB, Teknikringen 8,=20
SE-583 30 Link=F6ping, Sweden=20