unofficial mirror of guix-devel@gnu.org 
 help / color / Atom feed
* Helping with powerpc64-linux
@ 2020-06-14  2:41 Chris Marusich
  2020-06-16  2:05 ` lle-bout
  0 siblings, 1 reply; 2+ messages in thread
From: Chris Marusich @ 2020-06-14  2:41 UTC (permalink / raw)
  To: Léo Le Bouter; +Cc: guix-devel

[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]

Hi Léo,

As you know, I'm still investigating why the powerpc64-linux bootstrap
binaries (really just GCC) are not reproducible [1].  Eventually, if we
can't figure it out, we might want to just bite the bullet and use the
non-reproducible bootstrap binaries to get started, but I'm hopeful we
can figure it out and have at least two different people build the same
binaries before doing that.

The investigation is slow, partially because building things without
substitutes is very slow (iteration time is in hours or days).  In the
meantime, I understand you've been continuing to work on building more
powerpc64-linux packages on top of your own bootstrap binaries [2].  I
also understand you've had some trouble setting up Cuirass on your
POWER9 PC.  I'd like to help (and invite others to help, if they want),
but I'm not sure what the current status is.

Is Cuirass still not working?  I checked your POWER9 Gentoo VM, and I
saw that Cuirass is not currently running.

Which branches in your Git repository are still relevant?  My
understanding is that only the following branches in your repo might
currently contain changes we would want to upstream into Guix:

  - master: the first attempts you made.
  - wip-lle-bout-be1: your more recent attempts.

Do you think we should we try adding powerpc64le-linux?  Since the
powerpc64-linux bootstrap binaries are not reproducible, I see no reason
to expect that the powerpc64le-linux binaries would be reproducible,
either, but you never know.  Maybe it's worth a try.

Is there something else I can help you with?  I will have time while
waiting for long builds to finish, but please forgive me if my progress
is slow.  Life is busy.  Slowly but surely, we can make progress, and
hopefully we can keep collaborating to make it happen!

Footnotes: 
[1]  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41669

[2]  https://gitlab.com/lle-bout/guix

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Helping with powerpc64-linux
  2020-06-14  2:41 Helping with powerpc64-linux Chris Marusich
@ 2020-06-16  2:05 ` lle-bout
  0 siblings, 0 replies; 2+ messages in thread
From: lle-bout @ 2020-06-16  2:05 UTC (permalink / raw)
  To: Chris Marusich; +Cc: guix-devel, efraim


[-- Attachment #1.1: Type: text/plain, Size: 4321 bytes --]

On 6/14/20 4:41 AM, Chris Marusich wrote:
> Hi Léo,
> 
> As you know, I'm still investigating why the powerpc64-linux bootstrap
> binaries (really just GCC) are not reproducible [1].  Eventually, if we
> can't figure it out, we might want to just bite the bullet and use the
> non-reproducible bootstrap binaries to get started, but I'm hopeful we
> can figure it out and have at least two different people build the same
> binaries before doing that.
> 
> The investigation is slow, partially because building things without
> substitutes is very slow (iteration time is in hours or days).  In the
> meantime, I understand you've been continuing to work on building more
> powerpc64-linux packages on top of your own bootstrap binaries [2].  I
> also understand you've had some trouble setting up Cuirass on your
> POWER9 PC.  I'd like to help (and invite others to help, if they want),
> but I'm not sure what the current status is.
> 
> Is Cuirass still not working?  I checked your POWER9 Gentoo VM, and I
> saw that Cuirass is not currently running.
> 
> Which branches in your Git repository are still relevant?  My
> understanding is that only the following branches in your repo might
> currently contain changes we would want to upstream into Guix:
> 
>   - master: the first attempts you made.
>   - wip-lle-bout-be1: your more recent attempts.
> 
> Do you think we should we try adding powerpc64le-linux?  Since the
> powerpc64-linux bootstrap binaries are not reproducible, I see no reason
> to expect that the powerpc64le-linux binaries would be reproducible,
> either, but you never know.  Maybe it's worth a try.
> 
> Is there something else I can help you with?  I will have time while
> waiting for long builds to finish, but please forgive me if my progress
> is slow.  Life is busy.  Slowly but surely, we can make progress, and
> hopefully we can keep collaborating to make it happen!
> 
> Footnotes: 
> [1]  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41669
> 
> [2]  https://gitlab.com/lle-bout/guix
> 

Hello!

I'm busy as well with many things that werent planned at all! (Not a
job, but matters I need to contribute to **now** because it will be
impossible later)

The most recent changes are uncommitted and inside the VM in /root/guix
- but if they werent committed it means things are in flux.

Things to fix would be Go bootstrapping, using gccgo instead of go@1.4
as specified in the comment, because go@1.4 doesnt support ppc64[le],
lots of tools are in go. And you could investigate creating bootable ISO
inspiring yourself from how Debian does it for ppc64el.

Cuirass still isnt working, I havent had time to continue since my last
messages.

To get the state I was at, you need to (as root):

# cd /root/cuirass-data
# cuirass -D cuirass.sqlite -S specfile.scm --web --cache-directory=cache &
# cuirass -D cuirass.sqlite -S specfile.scm --cache-directory=cache

The reason is that you can't get both the web interface and the
background service that runs builds at the same time, so you need to run
it twice.

After that, you can access through http://localhost:8080 (from the
machine itself, so make an SSH tunnel).

I ran it on the machine inside a screen session.

For powerpc64le, I installed an Ubuntu ppc64el VM using nested KVM in
/root/ubuntu-ppc64le.qcow2

You can run it with (as root):

# cd /root
# qemu-system-ppc64 -drive format=qcow2,file=ubuntu-ppc64le.qcow2
-device virtio-net,netdev=vmnic -netdev user,id=vmnic -enable-kvm -m 8G
-smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial
stdio -machine cap-ccf-assist=off

This will give you a little endian VM from within the big endian VM with
minimal performance overhead.

I gave gentoo-ppc64 access to efraim as well, so they worked a little on
it as well. I initially investigated the nested KVM for them, but it's
done now.

We can also try little endian, but bootstrap-tarballs don't even build
right now, let alone reproducibility. I'll try to help as soon as I can
for investigating lack of reproducibility of these GCC binaries. I have
a beefier x86 server than you for this AFAICT, but I'm not sure I could
give access.

I hope to resume work again on GNU Guix soon!

Thanks a lot,
Leo



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-14  2:41 Helping with powerpc64-linux Chris Marusich
2020-06-16  2:05 ` lle-bout

unofficial mirror of guix-devel@gnu.org 

Archives are clonable:
	git clone --mirror https://yhetil.org/guix-devel/0 guix-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-devel guix-devel/ https://yhetil.org/guix-devel \
		guix-devel@gnu.org
	public-inbox-index guix-devel

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.devel
	nntp://news.gmane.io/gmane.comp.gnu.guix.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git