From owner-freebsd-stable Sun Mar 24 10:31: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.boo.net (mail2.boo.net [216.200.67.27]) by hub.freebsd.org (Postfix) with ESMTP id 2586E37B419 for ; Sun, 24 Mar 2002 10:30:46 -0800 (PST) Received: from pavilion (162.33.63.44) by mail2.boo.net (Worldmail 1.3.167) for freebsd-stable@FreeBSD.ORG; 24 Mar 2002 13:05:08 -0500 Message-Id: <3.0.5.32.20020324133135.01546100@pop.mindspring.com> X-Sender: kleinc@pop.mindspring.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 24 Mar 2002 13:31:35 -0500 To: freebsd-stable@FreeBSD.ORG From: Chris Klein Subject: problems with freebsd 4.4-stable Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a problem, I don't know how to get out of. I had several boxen running 4.3-release, and I updated them using CVS source to 4.4-stable. I tested the system for about 2-3 weeks on a box doing a decent amount of network actifity with loads in the 1-2 range with no known problem. I then rolled out this version to all of my other systems. However, when I try to compile software, whether it be freebsd 4.5 userland or just a simple application, the compile blows up with a linker problem. I have a system running 4.5, but it has totally different hardware then the other systems. Can I tar the system that works, and then untar it on the other boxes? if the enet cards are not supported, I could always recompile the kernel to provide support for it IF I can get the compiler to work again. the box with 4.5 is running 4.5-release. any ideas? Chris klein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message