public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Date: Mon, 07 Apr 2014 16:30:00 -0000	[thread overview]
Message-ID: <5342D299.1040101@cygwin.com> (raw)
In-Reply-To: <20140407112313.GA17922@calimero.vinschen.de>

On 4/7/2014 7:23 AM, Corinna Vinschen wrote:
> On Apr  7 11:08, Colin wrote:
>> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>>
>>>
>>> On Apr  4 09:44, Colin wrote:
>>>> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>>>>
>>>
>>> Alternatively, even though I hate to point people to older versions
>>> of Cygwin, you could try the old Cygwin 1.5.25.  I'm not quite sure,
>>> but I think it was compiled for i586 or even i386.  It's not as
>>> feature-rich as Cygwin 1.7 but it worked, and maybe the set of
>>> POSIX functions is sufficient for you.  See the Cygwin time machine
>>> at http://www.fruitbat.org/Cygwin/index.html#cygwincirca
>>>
>>> If you want to go even further back in time, then MSYS may be the
>>> right thing for you.  It's a rip-off of Cygwin 1.3.22 with a few
>>> patches to supposedly building native executables a bit better.
>>> Just make sure to grab the old MSYS, not the more recent MSYS2.
>>> See http://www.mingw.org/wiki/MSYS
>>>
>>> HTH,
>>> Corinna
>>>
>>
>> Cygwin 1.5.25 seems like a good option. So I downloaded setup-legacy.exe
>> from fruitbat and ran it on an XP machine which has not previously seen
>> Cygwin. Initially I installed just the base Cygwin files. The process ran
>> as expected, and installed 4,263 files in 472 folders.
>>
>> However the bash shell appears non-functional as far as external commands
>> go. It presents a prompt bash-3.2$, if I type something like ls, it
>> responds command not found. Any ideas?
>
> $PATH?

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.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

  reply	other threads:[~2014-04-07 16:30 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) [this message]
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
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=5342D299.1040101@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).