From: Duncan Roe <duncan_roe@acslink.net.au>
To: cygwin@cygwin.com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Date: Mon, 07 Apr 2014 23:26:00 -0000 [thread overview]
Message-ID: <20140407232600.GA21047@dimstar.local.net> (raw)
In-Reply-To: <534322E8.8070701@cygwin.com>
On Mon, Apr 07, 2014 at 06:12:56PM -0400, Larry Hall (Cygwin) wrote:
> On 4/7/2014 5:09 PM, Colin wrote:
>
> <snip>
>
> >>Indeed. And if your path under bash doesn't include /usr/bin, then I'll
> >>wager your postinstall scripts didn't run or at least
> >completely/correctly.
> >>See /etc/postinstall for the scripts. If you aren't able to figure out
> >>what didn't run properly, you can either try rerunning everything
> >manually
> >>and looking for faults (if any) or just rerun setup.exe and hope that it
> >>has better luck with the scripts the second time around.
> >>
> >
> >Spot on, Larry. $PATH is empty.
> >I 'Reinstall'ed Cygwin, but the result is the same. I did take note of
> >setup complaining that there is a more recent version available according
> >to the ini file (2.774 vs 2.674) but I'm picking that isn't the problem.
>
> I do find it interesting that the Cygwin Time Machine wouldn't have the
> setup version and the archive in sync. You'd have to check with that site
> to understand why you're seeing that.
>
> >/etc/postinstall contains the following "done" script files:
> >base-files-mketc.sh.done
> >base-files-profile.sh.done
> >bash.sh.done
> >coreutils.sh.done
> >cygwin-doc.sh.done
> >man.sh.done
> >passwd-grp.sh.done
> >terminfo.sh.done
> >terminfo0.sh.done
> >update-info-dir.sh.done
> >
> >Is there something missing from that list? What's my next step? I haven't
> >yet tried running them manually, that will have to wait until tonight (gmt
> >+ 12).
>
> That list seems a bit limited to me, unless you specifically asked for just
> those packages to install. Allowing setup to install a default installation
> should get you several dozen packages I believe, in 1.5 days. So I'd say
> start there and check that. If that doesn't help, check with the Cygwin
> Time Machine site for help.
>
I have an older install at work, and thought that behaviour was normal (empty
$PATH). I just set the PATH in .bashrc in the initial directory - then
everything "just worked".
Cheers ... Duncan.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-04-07 23:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 19:20 Colin
2014-04-03 21:22 ` René Berber
2014-04-04 8:07 ` Colin
2014-04-04 8:34 ` Corinna Vinschen
2014-04-04 9:44 ` Colin
2014-04-04 11:37 ` Corinna Vinschen
2014-04-07 11:08 ` Colin
2014-04-07 11:23 ` Corinna Vinschen
2014-04-07 16:30 ` Larry Hall (Cygwin)
2014-04-07 21:10 ` Colin
2014-04-07 22:12 ` Larry Hall (Cygwin)
2014-04-07 22:49 ` Peter A. Castro
2014-04-08 1:28 ` Larry Hall (Cygwin)
2014-04-08 1:50 ` Christopher Faylor
2014-04-08 1:59 ` Larry Hall (Cygwin)
2014-04-15 21:52 ` Peter A. Castro
2014-04-16 13:21 ` Achim Gratz
2014-04-16 16:02 ` Peter A. Castro
2014-04-16 16:20 ` Achim Gratz
2014-04-08 2:14 ` Peter A. Castro
2014-04-07 23:26 ` Duncan Roe [this message]
2014-04-14 8:37 ` Colin
2014-04-04 8:40 ` Yaakov (Cygwin/X)
2014-04-04 9:57 ` Colin
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=20140407232600.GA21047@dimstar.local.net \
--to=duncan_roe@acslink.net.au \
--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).