Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 6 Jan 2005 08:08:56 -0500 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3) Message-ID: <20050106130856.GA1068@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <20050105210221 DOT GA2428 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Henry, On Wed, Jan 05, 2005 at 11:10:26PM +0000, Henry S. Thompson wrote: > Jason Tishler writes: Sigh. More fodder for the spammers... :,( > > On Wed, Jan 05, 2005 at 05:22:48PM +0000, Henry S. Thompson wrote: > >> Ah, but rebasing cygwin1.dll _did_ fix the problem (once I had > >> tracked down cygserver and cygrunsrv in the Process Manager and > >> nuked them). > > > > Rebasing cygwin1.dll is not recommended which is why rebaseall > > explicitly skips it. > > Oops -- sorry, your instruction page didn't mention that. I'm not sure what you mean by "instruction page," but my README implies one should only use rebaseall unless they really know what they are doing. > What do you recommend given the evidence so far? See below... > [I am now also suffering from the "cygheap base address mismatch" > phenom., presumably as a result, from at least one app (psql), so I > would like a better solution.] > > So, I should reinstall a clean cygwin, then rebaseall? My naive > assumption was that was much _more_ drastic than just rebasing the > dlls involved. . . I recommend the following: 1. Just reinstall cygwin1.dll to make sure it is based at 0x61000000. 2. Following the steps in my README: Use the following procedure to rebase your entire system: 1. shutdown all Cygwin processes 2. start bash (do not use rxvt) 3. execute rebaseall (in the bash window) If you get any errors due to DLLs being in-use or read-only, then take the appropriate action and rerun rebaseall. Otherwise, you run the risk of fork() failing. BTW, you may want to run rebaseall with the -v (i.e., verbose) flag to verify you haven't run out of address space. For example, if some of your DLL are rebased to near 0x61000000 or below, then you are likely to have problems. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/