From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28954 invoked by alias); 20 Dec 2012 19:21:03 -0000 Received: (qmail 28929 invoked by uid 22791); 20 Dec 2012 19:21:01 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from youngberry.canonical.com (HELO youngberry.canonical.com) (91.189.89.112) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 20 Dec 2012 19:20:57 +0000 Received: from dslb-088-073-099-101.pools.arcor-ip.net ([88.73.99.101] helo=[192.168.42.216]) by youngberry.canonical.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1Tllfs-0006DD-AY; Thu, 20 Dec 2012 19:20:56 +0000 Message-ID: <50D36513.8020105@ubuntu.com> Date: Thu, 20 Dec 2012 19:21:00 -0000 From: Matthias Klose User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Ian Lance Taylor CC: GCC Patches , "libstdc++@gcc.gnu.org" , gfortran , GCJ-patches Subject: Re: [patch] fix install dependencies for target libraries References: <50D35782.7020202@ubuntu.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact java-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-patches-owner@gcc.gnu.org X-SW-Source: 2012-q4/txt/msg00060.txt.bz2 Am 20.12.2012 20:11, schrieb Ian Lance Taylor: > On Thu, Dec 20, 2012 at 10:22 AM, Matthias Klose wrote: >> This was seen with the libgo installation [1], but from my point of view can >> happen when the install target is called with -j >1, libtool seems to fall back >> to the system libraries if the library in the install location is not available >> (which is always the case if you install into an empty dir set with DESTDIR). >> Currently it just works for a non-parallel install because the dependencies in >> Makefile.def are created in the right order. >> >> Ok for the trunk? > > This is OK with a ChangeLog entry. committed, with the ChangeLog entry from the original mail. Matthias