From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 179091382C5 for ; Sun, 21 Jun 2020 22:35:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 84121E086F; Sun, 21 Jun 2020 22:35:22 +0000 (UTC) Received: from mail.apteryx.fr (apteryx.fr [91.121.49.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2E195E084A for ; Sun, 21 Jun 2020 22:35:21 +0000 (UTC) Received: from [192.168.0.19] (lfbn-idf2-1-437-14.w86-246.abo.wanadoo.fr [86.246.145.14]) by mail.apteryx.fr (Postfix) with ESMTPSA id 528D82461346 for ; Mon, 22 Jun 2020 00:35:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=apteryx.fr; s=apteryx.fr; t=1592778918; bh=tZhTY0nPvxzeLWykynGsbq3ZZBJxK26o80VMlDJQrIg=; h=Subject:To:References:From:Date:In-Reply-To; b=Biay+j5kbF6aW3f2pXv8/vre9TZUGZW8Xuniydl4aXJKJ3n5KfAmNqDjGRyy9JoTT IiptyImpu0KtkUmK7Xv51LoA9w78KgfaNtF1GNiIi78AYMPZtRTEjjYVxJVi7F31cg OmtdIHqB82N/EouS4JH/4Q5cn+lpMcRxwxRrDL8c= Subject: Re: [gentoo-user] Gentoo chroot with old glibc To: gentoo-user@lists.gentoo.org References: <2061dce3-a6b3-31a7-aed0-c08487fa15ce@apteryx.fr> From: =?UTF-8?Q?Herv=c3=a9_Guillemet?= Message-ID: <734ffd71-a3c1-621e-f975-189f40941041@apteryx.fr> Date: Mon, 22 Jun 2020 00:34:48 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Archives-Salt: a69e39fe-a215-42ae-94b9-ff67449884d5 X-Archives-Hash: 182d1014810f1944fc5cf1c5c2c67a63 Le 21/06/2020 à 23:08, Rich Freeman a écrit : > On Fri, Jun 19, 2020 at 5:19 PM Hervé Guillemet wrote: >> >> Or do you have any suggestion for alternatives to this gentoo chroot ? >> (I'd prefer avoid installing some CentOS or Ubuntu as virtual guests). > > You're of course free to do it any way you wish, but if I wanted to > create packages for various distros, I'd probably just follow their > instructions for doing so. > > If you're making Ubuntu 16.04 packages I suspect it would be just a > lot less fuss all around to do it from an Ubuntu 16.04 container, and > so on. > > And if you're just building binaries and creating tarballs with them, > well, why? If people want to manually deal with stuff the source is > already fine. If they want the benefits of a package manager they're > going to want packages. And if you're hoping to encourage distros to > do the packaging for you, they're probably only going to do that from > source anyway. In my case the application is a Java software embedding some native components. I don't want to limit the target system to some specific distros and specific versions, I just want the software to run on a large variety of linux boxes. All I have to do is to avoid linking with too recent libc and libstdc++. Version 2.29+ of libc is particularly annoying because they introduce new version of pow(), log() and exp()... so any simple mathematical library compiled with 2.29+ won't run on linux distro using 2.28-. As for the packaging, I'm using a jlink image in a tarball, and will probably use jpackage soon. > > I imagine most distros have a fairly straightforward packaging system, > and I suspect a lot of CI systems have plugins to churn out packages > for them automatically. So why maintain some Gentoo chroot and > carefully curate every single library on them to match some entirely > different distro? You're going to run into stuff where Gentoo doesn't > have the version you need in the repo, and you'll be fighting auto > updates, and so on. > > But, sure, you can get Gentoo to install whatever you want as long as > you don't mind manually picking packages, or maintaining your own repo > where you carefully curate this stuff. > Thanks for the suggestion. I believe my local build system with the chroot is enough for my current needs but I'll probably have to use a CI system if it becomes untractable or decide to use target distro packaging system. -- Hervé