From owner-freebsd-questions Sun Jun 14 14:08:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00141 for freebsd-questions-outgoing; Sun, 14 Jun 1998 14:08:12 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from post.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA00130 for ; Sun, 14 Jun 1998 14:08:05 -0700 (PDT) (envelope-from marko@uk.radan.com) Received: from (uk.radan.com) [158.152.75.22] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0ylK0S-0002Xm-00; Sun, 14 Jun 1998 21:08:04 +0000 Organisation: Radan Computational Ltd., Bath, UK. Phone: +44-1225-320320 Fax: +44-1225-320311 Received: from beavis.uk.radan.com (beavis [193.114.228.122]) by uk.radan.com (8.6.10/8.6.10) with SMTP id WAA01011 for ; Sun, 14 Jun 1998 22:07:23 +0100 Received: from uk.radan.com (rasnt-1) by beavis.uk.radan.com (4.1/SMI-4.1) id AA29214; Sun, 14 Jun 98 22:07:22 BST Message-Id: <358448AE.263C6BF@uk.radan.com> Date: Sun, 14 Jun 1998 22:03:26 +0000 From: Mark Ovens X-Mailer: Mozilla 4.04 [en] (WinNT; I) Mime-Version: 1.0 To: questions@FreeBSD.ORG Subject: Where is libc.so.3.1???? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is probably a stupid 'kin question, but where can I get a copy of libc.so.3.1? I'm trying to port a SunOS4.1.x app and have d/l the package for g++ 2.8.1 which has solved some of my problems, but now it bitches about "libc.so.3.0, minor version is older than expected 1". This doesn't seem to be a problem in itself but it creates hundreds of lines of these warnings which makes it hard to see the warnings/errors that are important. So far I've d/l about 20MB of .tgz's which I thought might contain libc.so.3.1 but with no success. Where is it?, or do I have to make it myself from libc.a??? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message