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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 4 Jan 2002 15:19:48 -0500 From: Jason Tishler To: Norman Vine Cc: "'Cygwin'" , "'Roth, Kevin P.'" Subject: Re: rebase for setup (curl) Message-ID: <20020104201948.GC2172@dothill.com> Mail-Followup-To: Norman Vine , 'Cygwin' , "'Roth, Kevin P.'" References: <20020104185355 DOT GA2172 AT dothill DOT com> <008e01c19552$4b6bd6e0$a300a8c0 AT nhv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <008e01c19552$4b6bd6e0$a300a8c0@nhv> User-Agent: Mutt/1.3.24i On Fri, Jan 04, 2002 at 02:02:01PM -0500, Norman Vine wrote: > Jason Tishler writes: > >Does anyone have any bright ideas? > > What happens if you link with --enable-auto-image-base ?? I was unable to get dllwrap to use --enable-auto-image-base, but I was able to build pq.dll using the normal "gcc -shared" way. I ran the full PostgreSQL regression test using this pq.dll without any errors. But, the above is not the point. The point is it will be difficult to get the upstream maintainers to change their build procedures just for Cygwin. So, how should Cygwin's rebase solution handle these odd-balls? Skip them, rebase around them (if possible), what? BTW, guess what value dllwrap used for --image-base? The same one used by --enable-auto-image-base! Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/