X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B421EF9.5000905@users.sourceforge.net> Date: Mon, 04 Jan 2010 11:01:45 -0600 From: "Yaakov (Cygwin/X)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Path problems with libgmpxx.la, libppl.la, libppl_c.la and libcloog-ppl.la - a work around References: <4B41F60D DOT 5010300 AT gmail DOT com> In-Reply-To: <4B41F60D.5010300@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 On 04/01/2010 08:07, David Billinghurst wrote: > As discussed previously [1], libraries built with libtool that depend on > libstdc++ end up with the full path to the build compiler's libstdc++.la > file in their own *.la file. This becomes a problem when the compiler is > upgraded. /usr/sbin/fix-libtool-scripts-for-latest-gcc-runtimes.sh Yaakov -- 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