From: "Hervé Guillemet" <hg@apteryx.fr>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Gentoo chroot with old glibc
Date: Fri, 19 Jun 2020 23:19:39 +0200 [thread overview]
Message-ID: <2061dce3-a6b3-31a7-aed0-c08487fa15ce@apteryx.fr> (raw)
Hello,
I need to distribute some linux binaries and the one built with my
up-to-date gentoo sytem won't run on distributions using older glibc.
My idea is too maintain a gentoo chroot dedicated for compiling my
binaries which would (package.)mask recent versions of glibc and gcc
ebuilds.
What's the better way to go ? If I start with some of the stage3
available for download, I won't be able to downgrade the glibc.
Or do you have any suggestion for alternatives to this gentoo chroot ?
(I'd prefer avoid installing some CentOS or Ubuntu as virtual guests).
--
Hervé
next reply other threads:[~2020-06-19 21:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 21:19 Hervé Guillemet [this message]
2020-06-21 17:06 ` [gentoo-user] Gentoo chroot with old glibc Michael
2020-06-21 19:43 ` Hervé Guillemet
2020-06-21 20:03 ` Michael
2020-06-21 22:52 ` Hervé Guillemet
2020-06-30 8:26 ` Andreas K. Huettel
2020-06-30 16:29 ` Laurence Perkins
2020-07-01 1:40 ` [gentoo-user] Grub: for the love of almighty Zardoz the magniicent Alan Grimes
2020-07-01 8:15 ` Neil Bothwick
2020-07-01 8:45 ` Michael
2020-07-02 4:20 ` Alan Grimes
2020-07-01 1:30 ` [gentoo-user] Gentoo chroot with old glibc Thomas Mueller
[not found] ` <20200701013122.CE9C8E08AE@pigeon.gentoo.org>
2020-07-01 14:47 ` Andreas K. Huettel
2021-01-04 11:57 ` Thomas Mueller
[not found] ` <20210104115748.50A5EE0930@pigeon.gentoo.org>
2021-01-08 23:37 ` Andreas K. Hüttel
2020-06-21 21:08 ` Rich Freeman
2020-06-21 22:34 ` Hervé Guillemet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2061dce3-a6b3-31a7-aed0-c08487fa15ce@apteryx.fr \
--to=hg@apteryx.fr \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox