From owner-freebsd-ports@FreeBSD.ORG Wed May 21 09:27:02 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E2B472F; Wed, 21 May 2014 09:27:02 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id EE80F2389; Wed, 21 May 2014 09:27:00 +0000 (UTC) Received: from AprilRyan.norad (iz-aix-213a.HS-Karlsruhe.DE [193.196.64.213]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id E313F7E8CB; Wed, 21 May 2014 11:26:57 +0200 (CEST) Message-ID: <537C7161.20205@bsdforen.de> Date: Wed, 21 May 2014 11:26:57 +0200 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Tijl Coosemans , Kevin Oberman Subject: Re: Staging issue with staging of net-im/libpurple (libtool?) References: <20140520085544.GB69382@pcjas.obspm.fr> <20140520140945.1383e5e2@kalimero.tijl.coosemans.org> <20140520121449.GA70272@pcjas.obspm.fr> <20140520145559.4aed52a5@kalimero.tijl.coosemans.org> <20140520143904.GA70855@pcjas.obspm.fr> <20140520221340.17ba4c56@kalimero.tijl.coosemans.org> In-Reply-To: <20140520221340.17ba4c56@kalimero.tijl.coosemans.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 09:27:02 -0000 On 20/05/2014 22:13, Tijl Coosemans wrote: > On Tue, 20 May 2014 08:52:46 -0700 Kevin Oberman wrote: >> Removed the FIND and re-built. After the build I looked in >> stage/usr/local/lib and the .so.0 files are still present! I then installed >> with no errors. I'll admit that I don't understand what is happening or why >> the touch of the files would break things, but it seems to be fixed, now. > > The touch didn't always give all files the same timestamp so sometimes > make thought the configure script was out of date and regenerated it > erasing any patches that had been applied to it. I figure something like: find FOO -exec touch {} + would do the trick. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?