From owner-freebsd-doc  Thu Dec 14 09:22:40 1995
Return-Path: owner-doc
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA17234
          for doc-outgoing; Thu, 14 Dec 1995 09:22:40 -0800 (PST)
Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA17229
          for <freebsd-doc@freebsd.org>; Thu, 14 Dec 1995 09:22:37 -0800 (PST)
Received: (from bugs@localhost) by freebsd.netcom.com (8.6.12/8.6.12) id LAA00337 for freebsd-doc@freebsd.org; Thu, 14 Dec 1995 11:19:21 -0600
From: Mark Hittinger <bugs@freebsd.netcom.com>
Message-Id: <199512141719.LAA00337@freebsd.netcom.com>
Subject: lets doc frequently fallen into trap #2
To: freebsd-doc@freebsd.org
Date: Thu, 14 Dec 1995 11:19:20 -0600 (CST)
X-Mailer: ELM [version 2.4 PL24 ME8b]
Content-Type: text
Sender: owner-doc@freebsd.org
Precedence: bulk


Frequently fallen into trap #2  

New user of FreeBSD experiments with the Linux emulation package.  The new
user copies the Linux shared libraries 'lib*.so.4' into /usr/lib.

The new user happily plays with Linux binaries.  Then one horrible day comes
when they reboot and try to compile something on FreeBSD natively.

Much evil then transpires.

The telltale sign are link errors involving the crt0 module.

Again, I've walked people out of this trap one too many times :-)

The solution is to get rid of the 'lib*.so.4' files in /usr/lib and make them
reboot (if they can!!).  Then put the linux shared libraries in some other
spot (like /usr/linux/lib).

Regards,

Mark Hittinger
Netcom/Dallas
bugs@freebsd.netcom.com