From: jbranso@dismail.de
To: "Vagrant Cascadian" <vagrant@debian.org>,
"zimoun" <zimon.toutoune@gmail.com>,
"Tobias Geerinckx-Rice" <me@tobias.gr>,
guix-devel@gnu.org
Subject: Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic
Date: Tue, 19 Jul 2022 21:44:39 +0000 [thread overview]
Message-ID: <7ca3b2f3a2b0dcf1700c12d5670195c4@dismail.de> (raw)
In-Reply-To: <874jzjogbo.fsf@contorta>
July 14, 2022 11:38 AM, "Vagrant Cascadian" <vagrant@debian.org> wrote:
> On 2022-07-14, zimoun wrote:
>
>> Well, dreaming about science fiction, it appears me more approachable to
>> have Guix running on something as Debian/kfreeBSD – it could be an
>> interesting project with the help of Debian folks. Other said, “just”
>> replace the Linux kernel by a variant of the FreeBSD one running with
>> GNU GLibc.
>
> Well, guile-3.0 does not build on Debian GNU/kFreeBSD, so that would be
> a bit of a blocker for a GNU Guix port:
>
> https://buildd.debian.org/guile-3.0
>
> But guile-2.2 built fine:
>
> https://buildd.debian.org/guile-2.2
>
> It is a rough port, I have toyed with it now and again ... requires lots
> of patches to code that assume userland based on running kernel; patches
> that upstreams are hesitant to take, etc. It is great as a grueling test
> of coding assumptions, though!
Does guile 3.0+ compile on the GNU/Hurd?
>
> My guess is you would have the same sort of problems with porting GNU
> Guix to any of the *BSD.
>
> Definitely the sort of project that would take someone highly motivated
> over many years...
>
> live well,
> vagrant
next prev parent reply other threads:[~2022-07-19 21:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 22:44 Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic Joshua Branson
2022-07-12 0:16 ` indieterminacy
2022-07-12 2:18 ` Joshua Branson
2022-07-12 3:56 ` Akib Azmain Turja
2022-07-12 13:39 ` Joshua Branson
2022-07-12 8:25 ` Josselin Poiret
2022-07-12 13:36 ` Joshua Branson
2022-07-12 20:12 ` Csepp
2022-07-14 10:23 ` zimoun
2022-07-14 10:40 ` Tobias Geerinckx-Rice
2022-07-14 13:06 ` zimoun
2022-07-14 15:38 ` Vagrant Cascadian
2022-07-15 11:09 ` Csepp
2022-07-19 21:46 ` jbranso
2022-07-19 21:44 ` jbranso [this message]
2022-07-19 21:43 ` jbranso
2022-07-19 21:41 ` jbranso
-- strict thread matches above, loose matches on Subject: below --
2022-07-20 16:03 Raghav Gururajan
2022-07-20 16:49 ` Maxime Devos
2022-07-21 16:27 ` zimoun
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=7ca3b2f3a2b0dcf1700c12d5670195c4@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
--cc=vagrant@debian.org \
--cc=zimon.toutoune@gmail.com \
/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).