From mint-bounce@lists.fishpool.fi Tue Feb 16 05:25:04 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=CrqaguhPBU4OHEIXNM21rR+v9vRQ2GXHpaM3uDzJky8=; b=n7ajIcDTt9WvUc5fJoj8HAPuoWbVLGsAkIESNj1jgIvfLcyrsxPLOlW5+D/bRPM6FU 1fmLs0HyNNlRhPbuEkqOUSyh06o3spSYElWekbh0+h8Cy903iZdesHfTBBu0w+L1S2uG c4rcZDkfbtfc6rzBfW2E0PgHgo4D20Pjy53Tc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Ihs47yAeexPLSnQ1NQphmDn4IQsxJzELEt0UwGRR3v3X4yfYide0RYiBfC1RqxhNYK 8uSFwzrJ6M7F5cksECYjxadNKhpSTIcY89PzrfdmbWX8RvPYJcDQJZ5SyS7cxYo1AFE2 mCj6o1hQs35a1T+5m1Vc5B+EPDA3Xc606co1U= Message-ID: <4B7A7214.1000202@freesbee.fr> Date: Tue, 16 Feb 2010 11:23:16 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] Wrong placement of cross binaries References: <4B79AFDC.4000401@freesbee.fr> <4B7A65E2.7090302@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Miro Kropacek wrote: > Because look at > your example, how ./configure should know when you're preparing > distribution package (i.e. native one) or when just installation for > your cross environment? In both cases there's --host the same, only > --prefix is different. Oh, you are right. configure can't know. Well, there is probably no clean way to build a library package to be used in a cross-compiler environment. In the library packages I have built until now, I have manually built and installed only the files required in a cross-environment. But in any case, this is a packaging hack. This kind of questions should be asked to the autoconf mailing list ;-) When I started to work on the cross-packages, I finally understood that there was rarely a clean way to do the packaging. So I started writing build scripts with dirty methods. Then I can improve the scripts from time to time, when I learn new stuff. But I'm afraid we will never find a clean, systematic procedure to build any package. In any case, if we are able to build clean binary packages even with dirty methods, it is not so bad. -- Vincent Rivière