Re: Porting GNU Mes to the PowerPC

[Ekaitz Zarraga]

We can help a little if you like.

Ping me if you need something.

On 2024-07-03 19:46, Tobias Alexandra Platen wrote:

I am currently reading the documentation of GNU Mes, and have
been thinking of doing a port to PowerPC / POWER ISA.
https://www.gnu.org/software/mes/manual/mes.html#Porting-GNU-Mes

No mutter on master

[Andreas Enge]

Hello,

currently I cannot reconfigure my laptop with the Xfce desktop environment
due to mutter not building:
Ok: 166
Expected Fail:  5
Fail:   1
Unexpected Pass:0
Skipped:0
Timeout:0
(this was on a local build).

Given the amount of output, I find it difficult to see which test failed.

I am on commit 972c06dc79641864b05590b2cd905cc8b810062b from yesterday.
As far as I can see, the corresponding derivation has not been built by QA
(following is my breadcrump trail of links followed from the data service):
   https://data.guix.gnu.org/revision/972c06dc79641864b05590b2cd905cc8b810062b
   
https://data.guix.gnu.org/revision/972c06dc79641864b05590b2cd905cc8b810062b/packages
   
https://data.guix.gnu.org/revision/972c06dc79641864b05590b2cd905cc8b810062b/packages?locale=en_US.UTF-8_query=mutter=version=synopsis_name=_results=100
   
https://data.guix.gnu.org/revision/972c06dc79641864b05590b2cd905cc8b810062b/package/mutter/44.9?locale=en_US.UTF-8
   
https://data.guix.gnu.org/gnu/store/gn3qgnzix2lnq4cg95samsy07zp0a8qr-mutter-44.9.drv

Going back in time, the last successful build I could find was for commit
ab41f5ec1cf559708165e1cd28e15538e6a197d6 of June 30. The next entry in the
dataservice has status "unknown".

After that, I do not see a commit that strikes me as suspicious as far as
mutter is concerned.

But there are quite a few patches applied to master recently of which I am
not sure whether they have gone through QA and the process described here:
   
https://guix.gnu.org/en/manual/devel/en/html_node/Managing-Patches-and-Branches.html
Going through QA should normally make sure that dependent packages still
build and that substitutes are directly available (while for some recently
updated packages there are no substitutes); I would like to invite all
committers to follow this procedure.

Andreas

Porting GNU Mes to the PowerPC

[Tobias Alexandra Platen]

I am currently reading the documentation of GNU Mes, and have 
been thinking of doing a port to PowerPC / POWER ISA.
https://www.gnu.org/software/mes/manual/mes.html#Porting-GNU-Mes

Trying to update my Guix on Android

[Tobias Alexandra Platen]

I folled this old blog post from April 24, 2018:
https://guix.gnu.org/en/blog/2018/guix-on-android/

I installed Guix some long time ago, new I tried a guix pull because my
instance is too old. I remember that I once got emacs working.

guix package: warning: Your Guix installation is 87 days old.
guix package: warning: Consider running 'guix pull' followed by
'guix package -u' to get up-to-date packages and security updates.

zcat /var/log/guix/drvs/nz/ad...4h-hello-2.12.1.tar.gz.drv.gz 

Starting download of /gnu/store/3d..a3-hello-2.12.1.tar.gz

>From https://ftpmirror.gnu.org/gnu/hello/hello-2.12.1.tar.gz...
In procedure getaddrinfo: Temporary failure in name resolution

I pushed the files from my laptop:
adb push /etc/protocols /system/etc/
adb push /etc/services /system/etc/
adb push /etc/resolv.conf /system/etc/
and tried nameserver 8.8.8.8 once.

/system/bin/curl is working, anything that uses glibc is broken.

Re: Bootstrapping path discovered for RISC-V 64bit

[Efraim Flashner]

On Wed, Jul 03, 2024 at 05:16:55PM +0200, Ekaitz Zarraga wrote:
> Hi,
> 
> Thanks to NlNet we have found a bootstrapping path for RISC-V 64 and we
> created an alternative `commencement.scm` draft that builds from source up
> to a GCC-9.
> 
> At the moment, that GCC-9 does not provide C++ support in my Guix packages.
> I tried to add it but I had issues. We made it work for live-bootstrap
> (Andrius did), and now it's time to move that to Guix but it's getting a
> little bit difficult with GCC's build-system.
> 
> I'm opening this issue to make the handover to Guix. I have already worked
> with Efraim and he agreed to continue with this work until it's upstreamed.
> Also Janneke is working on a version of this commencement module that adds
> support for x86, so we could use that for everything instead of relying in
> two different bootstrapping paths.

It may be possible that we end up diverging slightly in parts of the
bootstrap; glibc didn't get support for riscv64 until relatively
recently, although we will have to see about combining your work on
backporting (successfully!) riscv64 support to gcc-4.6.4 with the
existing version of 4.6.4 in commencement.scm. In reality I foresee it
with more comments in commencement.scm and some conditionals to try to
keep the different architectures working within the same packages.

> This will take some time to integrate. There are a couple of packages that I
> didn't bootstrap yet (but it's possible to bootstrap them): `flex` and
> `bison`. Mostly because we wanted to fix
> , too.

Piece by piece, we'll get there :) Plus we have live-bootstrap to look
at for inspiration.

> The Gash package is replaced with a non-bootstrapped Bash because there's an
> issue in Gash that hangs the bootstrapping process. We have reported it
> upstream. We should use Gash once the issue is fixed.
> 
> Also, we only made the path until a modern GCC, not all the rest of it, that
> we should be able to reuse from the current `commencement.scm` module.
> 
> This is the link to the repo:
> 
> https://github.com/ekaitz-zarraga/commencement.scm
> 
> I'm more than open to help Guix include the RISC-V bootstrapping process
> upstream, so if you have any question, suggestion or anything else, feel
> free to directly contact me.
> 
> As a note, in this series of blogposts I shared the 2 year process until
> today, and almost everything is documented:
> 
> https://ekaitz.elenq.tech/tag/bootstrapping-gcc-in-risc-v.html
> 
> Also, I'd like to publicly thank everyone who took part in this process.
> Especially Andrius, for all those sleepless nights we spent fixing weird
> compiler errors.
> 
> Let's make this finally happen!
> 
> Ekaitz

So close!

I have a couple of changes I've worked on at
https://github.com/Millak/commencement.scm but I'm also still working on
getting that modern GCC to build.

-- 
Efraim Flashner  רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature

Bootstrapping path discovered for RISC-V 64bit

[Ekaitz Zarraga]

Hi,

Thanks to NlNet we have found a bootstrapping path for RISC-V 64 and we 
created an alternative `commencement.scm` draft that builds from source 
up to a GCC-9.


At the moment, that GCC-9 does not provide C++ support in my Guix 
packages. I tried to add it but I had issues. We made it work for 
live-bootstrap (Andrius did), and now it's time to move that to Guix but 
it's getting a little bit difficult with GCC's build-system.


I'm opening this issue to make the handover to Guix. I have already 
worked with Efraim and he agreed to continue with this work until it's 
upstreamed. Also Janneke is working on a version of this commencement 
module that adds support for x86, so we could use that for everything 
instead of relying in two different bootstrapping paths.


This will take some time to integrate. There are a couple of packages 
that I didn't bootstrap yet (but it's possible to bootstrap them): 
`flex` and `bison`. Mostly because we wanted to fix 
, too.


The Gash package is replaced with a non-bootstrapped Bash because 
there's an issue in Gash that hangs the bootstrapping process. We have 
reported it upstream. We should use Gash once the issue is fixed.


Also, we only made the path until a modern GCC, not all the rest of it, 
that we should be able to reuse from the current `commencement.scm` module.


This is the link to the repo:

https://github.com/ekaitz-zarraga/commencement.scm

I'm more than open to help Guix include the RISC-V bootstrapping process 
upstream, so if you have any question, suggestion or anything else, feel 
free to directly contact me.


As a note, in this series of blogposts I shared the 2 year process until 
today, and almost everything is documented:


https://ekaitz.elenq.tech/tag/bootstrapping-gcc-in-risc-v.html

Also, I'd like to publicly thank everyone who took part in this process. 
Especially Andrius, for all those sleepless nights we spent fixing weird 
compiler errors.


Let's make this finally happen!

Ekaitz