From owner-freebsd-questions Thu Dec 21 13:38:39 2000 From owner-freebsd-questions@FreeBSD.ORG Thu Dec 21 13:38:38 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from donkeykong.gpcc.itd.umich.edu (donkeykong.gpcc.itd.umich.edu [141.211.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 8BE1037B400 for ; Thu, 21 Dec 2000 13:38:37 -0800 (PST) Received: from frogger.gpcc.itd.umich.edu (smtp@frogger.gpcc.itd.umich.edu [141.211.2.144]) by donkeykong.gpcc.itd.umich.edu (8.8.8/4.3-mailhub) with ESMTP id QAA12334; Thu, 21 Dec 2000 16:38:36 -0500 (EST) Received: from localhost (timcm@localhost) by frogger.gpcc.itd.umich.edu (8.8.8/5.1-client) with ESMTP id QAA06706; Thu, 21 Dec 2000 16:38:36 -0500 (EST) Date: Thu, 21 Dec 2000 16:38:36 -0500 (EST) From: Tim McMillen X-Sender: timcm@frogger.gpcc.itd.umich.edu To: Christopher Leake Cc: questions@FreeBSD.ORG Subject: Re: FW: non ported applications In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well if it's trivial, you should be able to just untar it assuming it was tarred, read the README or some such that comes with it and follow the instructions like ./configure make or whatever they want. If it's not trivial you may need to adjust the code. Maybe you can go by the error messages you see when you follow thier directions and just tweak the code. If it's worse than that you'll have to port it yourself. See: http://www.freebsd.org/porters-handbook/ Good luck, Tim On Thu, 21 Dec 2000, Christopher Leake wrote: > > > Can anyone point me to some documentation on how to install non-port bound > applications? I can't seem to find much on the topic and seemed to have > lost our bound copy of the FreeBSD handbook. > thanks > chris > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message