Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <425C466D.90A60B6B@dessent.net>
Date: Tue, 12 Apr 2005 15:06:37 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: irc
References: <F71C0DC6B4FD3648815AAA7F969E3529BE1909 AT sr002-2kexc DOT ateb DOT com> <95a8830605041214435ae48645 AT mail DOT gmail DOT com> <95a8830605041214513a9252e1 AT mail DOT gmail DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

beau wrote:

> On Apr 12, 2005 2:43 PM, beau <phaedral AT gmail DOT com> wrote:
> > When I tried irssi at the command line I got
> > "command not found."
> Sorry for the noise; irssi.exe was buried deep at
> /home/Me/irssi-0.8.0/src/fe-text/irssi.exe; I'm sure this the expected
> behavior and that the lack is mine.  All I need to do is alias in my
> .bashrc, right?

That is one way, but the usual way is to do "make install" after the
program is built which copies the binaries to $prefix/bin.  If you
didn't specify $prefix when configuring, it's probably /usr/local, which
means it will be installed into /usr/local/bin which is the usual place
for locally compiled/installed binaries.  I don't know if Cygwin's
default profile adds /usr/local/bin to the path, if not you'd want to
add it and then do "make install".  This will also take care of manpages
and so on so that "man irssi" will work as well.  It's a lot cleaner
than running it from the build directory.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/