From: turbo <turbo@weasel.com>
To: cygwin@cygwin.com
Subject: Re: make 3.80 bug - running a program inside make
Date: Thu, 21 Jul 2005 13:35:00 -0000 [thread overview]
Message-ID: <6.2.3.4.0.20050721062446.020d7258@wheresmymailserver.com> (raw)
>Careful on the version numbers here.
>bash-3.0-7 works, but has prompt display bugs because it inks
against libreadline6-5.0-2.
>bash-3.0-8 works, is the current version, and includes a static
readline library.
>bash-3.0-9 does not exist yet, but will soon be present to link against
>the experimental libreadline6-5.0-3.
>coreutils-5.3.0-7 works, but has bugs with .exe magic on virtual directories.
>coreutils-5.3.0-8 was dead on arrival, and was pulled from the mirrors
>immediately after that was discovered.
>coreutils-5.3.0-9 is the current version.
>>
>>
>>>Not Found: sh
>ANY installation that doesn't have /bin/sh probably had problems running
>the bash postinstall script, so the easiest solution is to use setup.exe
>to reinstall the latest version of bash.
As Eric Blake pointed out, there was a problem with /bin/sh.
I had run setup.exe about 4 or 5 days ago to update my installation.
Although it didn't produce any errors that I noticed, it did somehow
leave my system in
an inconsistent state. I re-ran setup.exe just now, and it installed
the latest coreutils,
and all my make code now works fine.
I don't know how my system got in an inconsistent state, but running cygcheck
before and after revealed the following diffs:
U:\j\jeff-lib>diff cygcheck.out cygcheck.out-new
3c3
< Current System Time: Thu Jul 21 06:13:31 2005
---
> Current System Time: Thu Jul 21 06:21:35 2005
112c112
< Not Found: sh
---
> Found: c:\cygwin\bin\sh.exe
263,264c263,264
< 1242k 2005/01/08 c:\cygwin\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
< "cygxml2-2.dll" v0.0 ts=2005/1/8 5:22
---
> 1383k 2005/07/14 c:\cygwin\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
> "cygxml2-2.dll" v0.0 ts=2005/7/13 16:43
299c299
< _update-info-dir 00276-1
---
> _update-info-dir 00280-1
306c306
< bash 3.0-7
---
> bash 3.0-8
312c312
< coreutils 5.3.0-7
---
> coreutils 5.3.0-9
390c390
< libxml2 2.6.16-2
---
> libxml2 2.6.20-2
U:\j\jeff-lib>
Thanks for all the help,
Jeff
--
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/
next reply other threads:[~2005-07-21 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 13:35 turbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-21 3:45 turbo
2005-07-21 4:03 ` Christopher Faylor
2005-07-21 11:48 ` Dave Korn
2005-07-21 12:47 ` Eric Blake
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=6.2.3.4.0.20050721062446.020d7258@wheresmymailserver.com \
--to=turbo@weasel.com \
--cc=cygwin@cygwin.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).