From: John Kehayias <john.kehayias@protonmail.com>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [WIP Patch] Adding an FHS container to guix shell
Date: Fri, 15 Jul 2022 15:41:43 +0000 [thread overview]
Message-ID: <DfM45blTQpXJFG3njx8MDz9t6QXIfGgtQ4SKTpTLldUeIM11PsS1GAUZx0V6ZAoz6oYn_jesHuTYBoVvtUFNHzh5Us0ukJ_JwJPBxPQ6WQg=@protonmail.com> (raw)
In-Reply-To: <87zghejkv2.fsf@contorta>
Hi Vagrant
------- Original Message -------
On Tuesday, July 12th, 2022 at 1:34 PM, Vagrant Cascadian wrote:
>
>
> On 2022-07-12, John Kehayias wrote:
>
> > Right now I did not handle a multi-arch setup, though that shouldn't
> > be too difficult. This would probably require an option to build
> > either all or specified packages for an additional arch, like 32bit in
> > a 64bit system, and make the libraries available (/lib32 or
> > something). Though may run into a union-build bug [2]?
>
>
> This might be splitting hairs, but that sounds like a bi-arch setup
> e.g. "/lib and /lib32" vs. a multi-arch setup "/lib,
> /lib/aarch64-linux-gnu/ and /lib/i386-linux-gnu"
>
> https://wiki.debian.org/Multiarch
>
> Not sure how many extra hoops you'd need to jump through to make either
> work well.
>
Thanks, was not aware of the different terminology. The use-case I'm thinking of mostly is for when one needs 32bit libraries in a 64bit x86 system, often for older programs (or maybe Wine).
In any event, I think for my first goals I'll leave that out and we can think about extensions for such a setup later. I don't think it would be very difficult, at least to build some libraries for a different system and link in a separate lib directory.
John
next prev parent reply other threads:[~2022-07-15 15:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 15:59 [WIP Patch] Adding an FHS container to guix shell John Kehayias
2022-07-12 17:34 ` Vagrant Cascadian
2022-07-15 15:41 ` John Kehayias [this message]
2022-07-13 2:11 ` Dominic Martinez
2022-07-13 23:27 ` Blake Shaw
2022-07-15 15:44 ` John Kehayias
2022-07-14 10:01 ` zimoun
2022-07-15 15:46 ` John Kehayias
2022-07-14 14:59 ` Liliana Marie Prikler
2022-07-15 16:00 ` John Kehayias
2022-07-15 13:43 ` Maxim Cournoyer
2022-07-15 16:35 ` John Kehayias
2022-07-15 13:45 ` Maxim Cournoyer
2022-07-18 11:40 ` Ludovic Courtès
2022-07-20 21:22 ` John Kehayias
2022-07-20 23:49 ` Maxime Devos
2022-07-21 3:15 ` John Kehayias
2022-07-21 0:20 ` debbugs irritation Was: " Csepp
2022-07-21 4:18 ` John Kehayias
2022-07-21 16:45 ` zimoun
2022-07-21 20:22 ` Csepp
2022-08-18 10:55 ` zimoun
2022-08-19 22:13 ` jbranso
2022-07-21 4:25 ` John Kehayias
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='DfM45blTQpXJFG3njx8MDz9t6QXIfGgtQ4SKTpTLldUeIM11PsS1GAUZx0V6ZAoz6oYn_jesHuTYBoVvtUFNHzh5Us0ukJ_JwJPBxPQ6WQg=@protonmail.com' \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).