X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=TacG9FWCu0i0HdGN1DE//hlNHO8ahtHOK89rF3//8LRR3/wRp+hpy WnV6bTUq6nF9bAtfdm2khVwJ2QOe2qHW6qJqVmfqAr25CwewZKSxPgXpRXARKbfh ACJhD3QB6bftNZ0K7Hwd87U+NrYTlGCdvqwJeS1IOGPS97ILYqlSzo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=sv/6rcSyK1ghHuHVWsI+r+XpnP8=; b=A3Rs9CTRkkiQmVbKRQ5z3J8o7awD w79vif+W9JuzgsBVZqzPzWj6pEu5daB+2svlTMBL1NRVd4Z7dgWlJNDdCKp+O2T0 iYIIVMWPVqCC5K+RfzJAUGgBZhsAc+E4O5yhbNjyvZcYQn9gFgue47mrX5aXAGG6 l0H/3AXLIiA3LVY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.0 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPAM_BODY,SPF_HELO_PASS,SPF_PASS,UNPARSEABLE_RELAY autolearn=no version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Colin Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU Date: Mon, 14 Apr 2014 08:37:15 +0000 (UTC) Lines: 71 Message-ID: References: <20140404083359 DOT GD2508 AT calimero DOT vinschen DOT de> <20140404113738 DOT GF2508 AT calimero DOT vinschen DOT de> <20140407112313 DOT GA17922 AT calimero DOT vinschen DOT de> <5342D299 DOT 1040101 AT cygwin DOT com> <534322E8 DOT 8070701 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Larry Hall (Cygwin cygwin.com> writes: > > On 4/7/2014 5:09 PM, Colin wrote: > > > > >> 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. > Examination of the install log files revealed that the post-install scripts all failed to execute correctly, with directory and file not found errors. For the record, I found that if installing to the root directory (normally not recommended) that it all works. And yes, my initial goal of compiling an application that will run on the Vortex86MX+ cpu has finally been achieved. My grateful thanks to all who have offered advice. Colin -- 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