This is a multi-part message in MIME format.
--------------0581E32060BB66599386553A
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Apparently I'm not the only one...

Regards, Thomas
--------------0581E32060BB66599386553A
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

	by gatekeeper.dcs.elf.stuba.sk (8.8.7/8.8.7) with ESMTP id KAA20406
	for <seidmann@dcs.elf.stuba.sk>; Wed, 8 Apr 1998 10:16:28 +0200 (CEST)
	(envelope-from J.D.Coleman@newcastle.ac.uk)
  (8.7.6/ for ncl.ac.uk) with SMTP; Wed, 8 Apr 1998 09:15:00 +0100 (BST)
From: Julian Coleman <J.D.Coleman@newcastle.ac.uk>
Message-Id: <199804080814.JAA17679@aire.ncl.ac.uk>
Subject: Re: GCC problem?
In-Reply-To: <352B17A6.B108E11A@dcs.elf.stuba.sk> from Thomas Seidmann at "Apr 8, 98 08:22:30 am"
To: seidmann@dcs.elf.stuba.sk (Thomas Seidmann)
Date: Wed, 8 Apr 1998 09:14:59 +0100 (BST)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

>                                                     Could someone
> perhaps test my little program on a NetBSD/Sparc 1.3 RELEASE? THNX.

> A compile test run would suffice (i.e. g++ -o a a.cc).

Funnily enough, on a stock 1.3 system, I get :

/var/tmp/cc18488a1.o: Undefined symbol `_hex__FR3ios' referenced from text segment
/var/tmp/cc18488a1.o: Undefined symbol `_hex__FR3ios' referenced from text segment
/var/tmp/cc18488a1.o: Undefined symbol `_setfill__Fi' referenced from text segment
/var/tmp/cc18488a1.o: Undefined symbol `_setw__Fi' referenced from text segment
/var/tmp/cc18488a1.o: Undefined symbol `_dec__FR3ios' referenced from text segment
/var/tmp/cc18488a1.o: Undefined symbol `_dec__FR3ios' referenced from text segment

J

-- 
    1024/55A5BC19        0F 3F 62 56 18 10 8B 84  43 8F F4 94 93 37 76 AA

S.E.P.

--------------0581E32060BB66599386553A--