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 Reply-To: From: "Norman Vine" To: "'Jason Tishler'" , "'Cygwin'" Cc: "'Roth, Kevin P.'" Subject: RE: rebase for setup (curl) Date: Fri, 4 Jan 2002 14:02:01 -0500 Message-ID: <008e01c19552$4b6bd6e0$a300a8c0@nhv> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 In-Reply-To: <20020104185355.GA2172@dothill.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Jason Tishler writes: >> >So, the options passed to ld are the same for cygcurl-2.dll and pq.dll >except for the slight variation of --base-file versus --image-base. > >I decided to table the search for the "offending" ld option(s) because >of the following gloomy thought: > > Given that rebase can break certain DLLs and that it is nearly > impossible to control how arbitrary packages create their DLLs, > can setup.exe's proposed rebase solution deal with this problem? > Or, is the rebase solution doomed to failure? > >Does anyone have any bright ideas? What happens if you link with --enable-auto-image-base ?? Cheers Norman -- 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/