From: "Bob Calco" <robert.calco@verizon.net>
To: "Larry Hall \(RFK Partners, Inc\)" <lhall@rfk.com>, <cygwin@cygwin.com>
Subject: RE: Problem obtaining m4 binaries
Date: Sun, 26 May 2002 21:35:00 -0000 [thread overview]
Message-ID: <CHELLOJJMKHPEKPJINCBGEHCDLAA.robert.calco@verizon.net> (raw)
In-Reply-To: <4.3.1.2.20020526131016.02748ee8@pop.ma.ultranet.com>
% May I suggest looking at the email archives when you have
% questions about whether other people have had similar problems
% to you with Cygwin?
yes, thanx.
% This list is where all problems are reported and discussed so
% it's real helpful to the overall volume if folks do a little
% research first and avoid a message like this if possible.
Right. It is annoying when new folks rehash all the same questions, a
problem, for instance, no the python list. Sorry - I usually have better
manners.
% In answer to your question,
Thanx, I'm on track I think... I set my $USER and $HOME variables in
/etc/profile, and made sure the directories /home/rcalco exist (they weren't
created during the install). It still says "I have no name!@CALCOLAP" but it
does start me in /home/rcalco anyway. I'll figure it out, or I'll stop
trying since it doesn't inhibit me functionally in any apparent way.
I successfully compiled what I wanted to compile so I feel I achieved my
main objective. Somebody might want to check out wuzzup with m4 binaries not
downloading properly from setup, but I was able to compile it from the
source anyway so it wasn't a show stopper, just a nuissance. :)
Sorry for the hassle.
- Bob.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
prev parent reply other threads:[~2002-05-26 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 14:29 Bob Calco
2002-05-26 16:24 ` Larry Hall (RFK Partners, Inc)
2002-05-26 21:35 ` Bob Calco [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CHELLOJJMKHPEKPJINCBGEHCDLAA.robert.calco@verizon.net \
--to=robert.calco@verizon.net \
--cc=cygwin@cygwin.com \
--cc=lhall@rfk.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).