* Mes Bootstrapping demonstration
@ 2022-09-18 0:11 Aret San
2022-09-19 5:03 ` Jan Nieuwenhuizen
0 siblings, 1 reply; 3+ messages in thread
From: Aret San @ 2022-09-18 0:11 UTC (permalink / raw)
To: guix-devel
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
Hi,
I heard that from GNU Mes 0.24 it's capable of being bootstrapped with
M2-Planet. But when I was trying to do that it ended up in some errors in
scm files `something related to (export)`. I also tried this in a busybox
docker image where there's no gcc (not even guile), The M2-Planet and
mescc-tools compiles fine but GNU Mes crashed the container in `sh
configure.sh`.
I was wondering if a step-by-step bootstrap instruction can be written for
a barebone system like a busybox container.
Thanks,
John Wang
[-- Attachment #2: Type: text/html, Size: 651 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Mes Bootstrapping demonstration
2022-09-18 0:11 Mes Bootstrapping demonstration Aret San
@ 2022-09-19 5:03 ` Jan Nieuwenhuizen
2022-09-19 9:22 ` [bootstrappable] " Andrius Štikonas
0 siblings, 1 reply; 3+ messages in thread
From: Jan Nieuwenhuizen @ 2022-09-19 5:03 UTC (permalink / raw)
To: Aret San; +Cc: guix-devel, bootstrappable
Aret San writes:
Hello Aret/John,
> I heard that from GNU Mes 0.24 it's capable of being bootstrapped with
> M2-Planet.
Yes, see the core-updates branch.
> But when I was trying to do that it ended up in some errors
> in scm files `something related to (export)`.
Sounds like a Nyacc problem. You're missing GUILE_LOAD_PATH set to
nyacc/modules, or you don't have nyacc-1.00.2.
> I also tried this in a busybox docker image where there's no gcc (not
> even guile), The M2-Planet and mescc-tools compiles fine but GNU Mes
> crashed the container in `sh configure.sh`.
That could be, I haven't tried such tings.
> I was wondering if a step-by-step bootstrap instruction can be written
> for a barebone system like a busybox container.
If you don't want to use Guix, you may have a look at the live bootstrap
project
https://github.com/fosslinux/live-bootstrap
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://lilypond.org
Freelance IT https://JoyOfSource.com | Avatar® https://AvatarAcademy.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [bootstrappable] Re: Mes Bootstrapping demonstration
2022-09-19 5:03 ` Jan Nieuwenhuizen
@ 2022-09-19 9:22 ` Andrius Štikonas
0 siblings, 0 replies; 3+ messages in thread
From: Andrius Štikonas @ 2022-09-19 9:22 UTC (permalink / raw)
To: Aret San, bootstrappable; +Cc: guix-devel, Jan Nieuwenhuizen
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Hi Aret,
> If you don't want to use Guix, you may have a look at the live bootstrap
> project
>
> https://github.com/fosslinux/live-bootstrap
You might want to take a look at the following files:
https://github.com/fosslinux/live-bootstrap/blob/master/sysa/run.kaem
https://github.com/fosslinux/live-bootstrap/blob/master/sysa/mes-0.24/mes-0.24.kaem
The first file sets up some environmental variables that are used by both mes-0.24 and tcc-0.9.26 steps.
I think GUILE_LOAD_PATH and MES_PREFIX are required by mes and rest (NYACC_PKG, MES_VERSION, MES_PKG_DIR)
are for scripting convenience.
The second file sets up MES_ARENA, MES_MAX_ARENA, MES_STACK and the rest of variables are just for scripting convenience.
Kind regards,
Andrius
>
> Greetings,
> Janneke
>
>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-09-19 10:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-09-18 0:11 Mes Bootstrapping demonstration Aret San
2022-09-19 5:03 ` Jan Nieuwenhuizen
2022-09-19 9:22 ` [bootstrappable] " Andrius Štikonas
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).