From owner-freebsd-stable Wed Feb 21 4:14:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 5BB3437B503 for ; Wed, 21 Feb 2001 04:14:54 -0800 (PST) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14VYAX-000Hb4-00 for stable@freebsd.org; Wed, 21 Feb 2001 12:14:53 +0000 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f1LCErW07512 for stable@freebsd.org; Wed, 21 Feb 2001 12:14:53 GMT (envelope-from rasputin) Date: Wed, 21 Feb 2001 12:14:52 +0000 From: Rasputin To: stable@freebsd.org Subject: compiler problems Message-ID: <20010221121452.A7487@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Past couple of days I've had trouble with gcc. Typical errors are: "Shared object has no run-time symbol table" "junk pointer: too high to make sense" and the odd sig11. This happens during big compiles (e.g. make world, installing wine, etc)- only in the last week or so. I made world successfully last week sometime (can't tell you exactly when as the box has spontaneously rebooted and has become a brainless windoze PC). My understanding is that I'm out of VM, or my CPU/RAM is on the way out. The only slight oddity is that I've only seen these errors when shelled in remotely over ssh; a build of WINE under X last night worked perfectly. If it *is* a memory shortage, surely running X should stress things more than just running networking? Just seeing if anyone else has had problems (chances are it is the box, CPU and RAM are both > 3 years old) Thanks. -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message