From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24073 invoked by alias); 7 Apr 2014 22:49:57 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 24062 invoked by uid 89); 7 Apr 2014 22:49:57 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: Yes, score=6.8 required=5.0 tests=AWL,BAYES_50,SPAM_BODY,SPF_HELO_PASS,SPF_PASS,TVD_RCVD_IP autolearn=no version=3.3.2 X-HELO: ripple.fruitbat.org Received: from 173-228-5-241.dsl.static.sonic.net (HELO ripple.fruitbat.org) (173.228.5.241) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 07 Apr 2014 22:49:55 +0000 Received: from ming.fruitbat.org (ming.fruitbat.org [192.168.55.2]) by ripple.fruitbat.org (8.14.4/8.14.4/fruitwall-1.7) with ESMTP id s37MfZ4O015902 for ; Mon, 7 Apr 2014 15:41:35 -0700 Received: from ming.fruitbat.org (ming.fruitbat.org [192.168.55.2]) by ming.fruitbat.org (8.14.4/8.14.4/fruithub-1.11) with ESMTP id s37MfRAa032561 for ; Mon, 7 Apr 2014 15:41:27 -0700 Date: Mon, 07 Apr 2014 22:49:00 -0000 From: "Peter A. Castro" To: cygwin@cygwin.com Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU In-Reply-To: <534322E8.8070701@cygwin.com> Message-ID: References: <20140404083359.GD2508@calimero.vinschen.de> <20140404113738.GF2508@calimero.vinschen.de> <20140407112313.GA17922@calimero.vinschen.de> <5342D299.1040101@cygwin.com> <534322E8.8070701@cygwin.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IsSubscribed: yes X-SW-Source: 2014-04/txt/msg00141.txt.bz2 On Mon, 7 Apr 2014, Larry Hall (Cygwin) wrote: > 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. Geetings, Larry, Some comments about this (sorry if this is off-tipic): 1) There used to be a directory to pull the snapshots, but that's been removed or otherwise made inaccessable a while ago, so archving the snapshots has been impossible for me. 2) Packaging changes of setup.exe have made extracting the version string impossible, save for actually running setup, which isn't something I'm going to do on a daily basis. If there is a method of extracting this info from it, please do tell me how. 3) The format of setup.ini hasn't changed in any significant way that prevents newer versions of setup from working with older versions of the achive, and vise-versa, so it hasn't been worth doing regular achives of setup. Mostly I tell people to grab the lastest setup and try it first. The exceptions are for the Legacy release (hard coded for -legacy) as well as the preview (-2) release, but that, again, was most about the name of the setup file and the initial release path names. So, there really hasn't been much incentive to archive setup. That being said, I do have a Legacy and a -2 setup versions available for those that need them, as well as some other older releases of setup, just in case. If someone can tell me how to extract the version id from setup.exe, I'll start archiving specific versions of it again. >> /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. -- --=> Peter A. Castro Email: doctor at fruitbat dot org / Peter dot Castro at oracle dot com "Cats are just autistic Dogs" -- Dr. Tony Attwood -- 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