From: Earnie Boyd <earnie_boyd@yahoo.com>
To: John Wiersba <John.Wiersba@medstat.com>
Cc: cygwin users <cygwin@sourceware.cygnus.com>
Subject: Re: updating to snapshot
Date: Mon, 27 Mar 2000 14:43:00 -0000 [thread overview]
Message-ID: <20000327224324.18996.qmail@web121.yahoomail.com> (raw)
--- John Wiersba <John.Wiersba@medstat.com> wrote:
> Earnie,
>
> I'm trying to build vim5.5. The build failed when trying to link with
> libcurses.a because of a lack of _ctype_. This is apparently because I'm
> using a binary version of ncurses I pulled off franken.de which was built
> against a snapshot which didn't need _ctype_. So, I tried to rebuild
> ncurses to fix the _ctype_ problem. But I ran into a problem with the
> install:
> > ../././man/../mkinstalldirs /blah/target/man
> ../././man/../../././man/../mkinstalldirs: Can't open ...
>
> You can see that the program name has been screwed up by bash. Should I
> install a snapshot more recent that 1/15/99 to fix this problem?
>
A newer snapshot will fix the _ctype_ problem if you install the cygwin-inst
tarball. It used to be __ctype and was changed since 1/15/99.
> Here's the real question: If so, which snapshot should I install (i.e.
> which snapshot do you believe is the most stable)?. And, what's the easiest
> way to prepare to back the snapshot out if something goes wrong?
>
I'll suggest the most recent snapshot and I posted within the past 4 to 6 weeks
a howto on using a snapshot. Please refer to the archives for that.
=====
---
Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
__Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
__Minimalist GNU for Windows__
Mingw32 List: < http://www.egroups.com/group/mingw32/ >
Mingw Home: < http://www.mingw.org/ >
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
reply other threads:[~2000-03-27 14:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000327224324.18996.qmail@web121.yahoomail.com \
--to=earnie_boyd@yahoo.com \
--cc=John.Wiersba@medstat.com \
--cc=cygwin@sourceware.cygnus.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).