From: Mark H Weaver <mhw@netris.org>
To: 21610@debbugs.gnu.org
Subject: bug#21610: FreeBSD compilation problem (errno_location)
Date: Sun, 04 Oct 2015 14:02:43 -0400 [thread overview]
Message-ID: <877fn2v7ek.fsf@netris.org> (raw)
In-Reply-To: <87io6ob74s.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 03 Oct 2015 12:04:19 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Janus Troelsen <ysangkok@gmail.com> skribis:
>
>> I know FreeBSD is not officially supported, but I don't see why it shouldn't be? Many GNU tools work on FreeBSD.
>
> Guix depends on the availability of the GNU C Library, with either the
> Linux-libre kernel or the Hurd. So it cannot be used at all on FreeBSD.
I'd like to expand on this. When Guix builds packages, the container in
which software is built does not use any software or libraries from the
host system at all. The only part of the host system that we use,
implicitly, is the kernel.
Guix is bootstrapped in a manner analogous to Cross [GNU/]Linux from
Scratch, starting from statically "bootstrap binaries" that we provide
for each supported architecture/kernel combination. At present, we
provide bootstrap binaries for x86_64, i686, mips64el, and armhf on top
of Linux (the kernel), and soon we will support the Hurd as well.
Unless the FreeBSD kernel is able to emulate Linux (the kernel)
sufficiently well to run our binaries for GNU/Linux unmodified, and to
convince 'configure' scripts and other build systems that the kernel is
Linux, using Guix on top of FreeBSD will involve porting it, as
described in section 7.8 (Porting to a New Platform) in the Guix manual.
As Ludovic pointed out, such a port would still need to use GNU libc,
and would use all of the GNU userland on top, so only the kernel from
FreeBSD would be used.
Regards,
Mark
prev parent reply other threads:[~2015-10-04 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 1:56 bug#21610: FreeBSD compilation problem (errno_location) Janus Troelsen
2015-10-03 10:04 ` Ludovic Courtès
2015-10-04 18:02 ` Mark H Weaver [this message]
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=877fn2v7ek.fsf@netris.org \
--to=mhw@netris.org \
--cc=21610@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.