Re: MIPS64/N64 support

Nikita Karetnikov writes: > OK, I fetched the tarballs. Now I’m getting this error. > > > $ ./pre-inst-env guix build -K hello > > [...] > > make-3.82/main.c > make-3.82/README.OS2 > make-3.82/remote-cstms.c > phase `unpack' succeeded after 4 seconds [...] > pwd: error retrieving current directo

Re: MIPS64/N64 support

Mark H Weaver skribis: > This is the entry that reports the wrong inode number. Note that this > is a bind mount that mirrors /tmp/nix-build-make-boot0-3.82.drv-0 . > > I guess that /tmp/nix-build-make-boot0-3.82.drv-0 should have > the same inode as /tmp/nix-build-make-boot0-3.82.drv-0/. , but

Re: MIPS64/N64 support

Hi Mark, Thanks for the thorough analysis. Mark H Weaver skribis: > My suspicion is that my kernel (linux-libre-2.6.39.1) and Guix's glibc > are not playing nicely together. However, Guix's glibc was configured > to support kernels as early as 2.6.30, and the same 'pwd' executable > that fails

Re: MIPS64/N64 support

I wrote: > Here are the inode numbers as reported by ls -lia: > > mhw:/tmp$ ls -lia nix-build-make-boot0-3.82.drv-0/ > total 16 > 7274550 drwxr-xr-x 3 guix-builder1 guix-builder 4096 Oct 8 17:19 . > 7072375 drwxrwxrwt 9 root root 4096 Oct 8 17:19 .. > 7272956 -rw-r--r-- 1 guix-bu

Re: MIPS64/N64 support

l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> Nikita Karetnikov writes: >> >>> OK, I fetched the tarballs. Now I’m getting this error. >>> >>> >>> $ ./pre-inst-env guix build -K hello >>> >>> [...] >>> >>> make-3.82/main.c >>> make-3.82/README.OS2 >>> make-3.82/remote-cst

Re: MIPS64/N64 support

Mark H Weaver skribis: > Nikita Karetnikov writes: > >> OK, I fetched the tarballs. Now I’m getting this error. >> >> >> $ ./pre-inst-env guix build -K hello >> >> [...] >> >> make-3.82/main.c >> make-3.82/README.OS2 >> make-3.82/remote-cstms.c >> phase `unpack' succeeded after 4 seconds >> she

Re: MIPS64/N64 support

Nikita Karetnikov writes: > OK, I fetched the tarballs. Now I’m getting this error. > > > $ ./pre-inst-env guix build -K hello > > [...] > > make-3.82/main.c > make-3.82/README.OS2 > make-3.82/remote-cstms.c > phase `unpack' succeeded after 4 seconds > shell-init: error retrieving current direct

Re: MIPS64/N64 support

On Tue, Oct 01, 2013 at 02:06:06PM +0400, Nikita Karetnikov wrote: > > I also seem to recall that gNewSense had only o32 support, years > > ago. And not any n32/n64. Can it be? > > I think this is correct. > > > I'd simply try to avoid ext4 or even ext3, without changing the kernel. I > > don't

Re: MIPS64/N64 support

On Tue, Oct 01, 2013 at 11:48:48AM +0400, Nikita Karetnikov wrote: > > Sure the kernel, needs to have n64 support enabled, to run n64 binaries. I > > imagine it would be detected at ELF header though, and not simply getting > > failing syscalls. > > > I'm sorry, but I don't know what problem is th

Re: MIPS64/N64 support

On Tue, Oct 01, 2013 at 01:51:28AM +0400, Nikita Karetnikov wrote: > > Could you try running the statically-linked bash from > > ‘static-binaries.tar.xz’ and see if the same error occurs? Perhaps > > strace it so we can see where that error comes from. > > I don’t see anything similar. > > > Loo

Re: MIPS64/N64 support

On Tue, Oct 01, 2013 at 01:25:39PM +0200, Ludovic Courtès wrote: > Lluís Batlle i Rossell skribis: > > > On Tue, Oct 01, 2013 at 02:06:06PM +0400, Nikita Karetnikov wrote: > >> > I also seem to recall that gNewSense had only o32 support, years > >> > ago. And not any n32/n64. Can it be? > >> > >

Re: MIPS64/N64 support

On Tue, Oct 01, 2013 at 12:55:53PM +0400, Nikita Karetnikov wrote: > > In fact I was reluctant to raise again the ext4 topic ;) But I think 3.5.3 > > has a > > broken readdir() syscall in ext4. I think it's not a problem of kernel > > options > > active. You simply have to avoid using ext4 (or ev

Re: MIPS64/N64 support

Lluís Batlle i Rossell skribis: > On Tue, Oct 01, 2013 at 02:06:06PM +0400, Nikita Karetnikov wrote: >> > I also seem to recall that gNewSense had only o32 support, years >> > ago. And not any n32/n64. Can it be? >> >> I think this is correct. >> >> > I'd simply try to avoid ext4 or even ext3,

Re: MIPS64/N64 support

> I also seem to recall that gNewSense had only o32 support, years > ago. And not any n32/n64. Can it be? I think this is correct. > I'd simply try to avoid ext4 or even ext3, without changing the kernel. I > don't > know of linux-libre, but you need something newer than 3.7 I think, to get the

Re: MIPS64/N64 support

> I was getting multiple warnings, “a variable is defined but is not used” > or something like that. Or “unbound variable”; I can’t remember. pgpBVNEuPIAcj.pgp Description: PGP signature

Re: MIPS64/N64 support

> In fact I was reluctant to raise again the ext4 topic ;) But I think 3.5.3 > has a > broken readdir() syscall in ext4. I think it's not a problem of kernel options > active. You simply have to avoid using ext4 (or even ext3, I can't recall). In the past, I was using EXT3 with CONFIG_EXT4_USE_FO

Re: MIPS64/N64 support

> Sure the kernel, needs to have n64 support enabled, to run n64 binaries. I > imagine it would be detected at ELF header though, and not simply getting > failing syscalls. > I'm sorry, but I don't know what problem is that. Are you running a recent > kernel, first? Linux-libre 3.5.3 from gNewSen

Re: MIPS64/N64 support

> Could you try running the statically-linked bash from > ‘static-binaries.tar.xz’ and see if the same error occurs? Perhaps > strace it so we can see where that error comes from. I don’t see anything similar. > Looking at >

Re: MIPS64/N64 support

(Cc’ing Lluís who may know more.) Nikita Karetnikov skribis: > OK, I fetched the tarballs. Now I’m getting this error. > > > $ ./pre-inst-env guix build -K hello > > [...] > > make-3.82/main.c > make-3.82/README.OS2 > make-3.82/remote-cstms.c > phase `unpack' succeeded after 4 seconds > shell-i

Re: MIPS64/N64 support

Nikita Karetnikov skribis: > So I ran this command: > > $ ./pre-inst-env guix build bootstrap-tarballs > --target=mips64el-linux-gnuabi64 > > but it failed due to the already known problem: > > /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.18.drv-0/build/libc_pic.a: > could not read symb

Re: MIPS64/N64 support

OK, I fetched the tarballs. Now I’m getting this error. $ ./pre-inst-env guix build -K hello [...] make-3.82/main.c make-3.82/README.OS2 make-3.82/remote-cstms.c phase `unpack' succeeded after 4 seconds shell-init: error retrieving current directory: getcwd: cannot access parent directories: I

Re: MIPS64/N64 support

So I ran this command: $ ./pre-inst-env guix build bootstrap-tarballs --target=mips64el-linux-gnuabi64 but it failed due to the already known problem: /tmp/nix-build-glibc-cross-mips64el-linux-gnuabi64-2.18.drv-0/build/libc_pic.a: could not read symbols: Archive has no index; run ranlib to add

Re: MIPS64/N64 support

Nikita Karetnikov skribis: > So I changed ‘bootstrap.scm’ and got the attached error message. Any > ideas? The diff for bootstrap.scm looks good. > @ build-started > /nix/store/pl2prx6qj1cbcf8rxs874s6r5w0zhzhs-make-boot0-3.82.drv - > mips64el-linux > /nix/var/log/nix/drvs/pl//2prx6qj1cbcf8r

Re: MIPS64/N64 support

So I changed ‘bootstrap.scm’ and got the attached error message. Any ideas? diff --git a/gnu/packages/bootstrap.scm b/gnu/packages/bootstrap.scm index a1d4c7f..9151e01 100644 --- a/gnu/packages/bootstrap.scm +++ b/gnu/packages/bootstrap.scm @@ -63,12 +63,13 @@ (fetch store url hash-algo ha

Re: MIPS64/N64 support

Nikita Karetnikov skribis: >> Instead of a URL, you can also change bootstrap.scm to refer directly to >> a local file name, like this: > >> (package >> ... >> (source "/home/nikita/my-guile-that-works.tar.gz") >> ...) > > I’m sorry to say that we probably won’t be able to include t

Re: MIPS64/N64 support

> Instead of a URL, you can also change bootstrap.scm to refer directly to > a local file name, like this: > (package > ... > (source "/home/nikita/my-guile-that-works.tar.gz") > ...) I’m sorry to say that we probably won’t be able to include the MIPS binaries in 0.4 because it take

Re: MIPS64/N64 support

Nikita Karetnikov skribis: >>> I’ve already tried that: >>> >>> $ ./pre-inst-env guix build -K -s mips64el-linux-gnuabi64 hello >>> >>> […] >>> >>> ERROR: bootstrap binary not found "tar" "mips64el-linux-gnuabi64" > >> As I wrote, call it ‘mips64el-linux’, and put the binaries under the >> direct

Re: MIPS64/N64 support

>> I’ve already tried that: >> >> $ ./pre-inst-env guix build -K -s mips64el-linux-gnuabi64 hello >> >> […] >> >> ERROR: bootstrap binary not found "tar" "mips64el-linux-gnuabi64" > As I wrote, call it ‘mips64el-linux’, and put the binaries under the > directory of that name. I did that but forgo

Re: MIPS64/N64 support

Nikita Karetnikov skribis: >>> 3. Created ‘mips64el-linux-gnuabi64’ in ‘gnu/packages/bootstrap/’. > >> Hmm, I think we should just call it ‘mips64el-linux’ since the ABI is >> really something orthogonal. > > I’ve already tried that: > > $ ./pre-inst-env guix build -K -s mips64el-linux-gnuabi64 h

Re: MIPS64/N64 support

>> 3. Created ‘mips64el-linux-gnuabi64’ in ‘gnu/packages/bootstrap/’. > Hmm, I think we should just call it ‘mips64el-linux’ since the ABI is > really something orthogonal. I’ve already tried that: $ ./pre-inst-env guix build -K -s mips64el-linux-gnuabi64 hello […] ERROR: bootstrap binary not

Re: MIPS64/N64 support

Nikita Karetnikov skribis: > When I tested the previous set of binaries (see the mips64el branch), it > was necessary to adjust ‘%url-base’ in ‘build-aux/download.scm’. It > seems that now it’s not needed since they are already available on > hydra.gnu.org. Well, when you’ve confirmed that you’

Re: MIPS64/N64 support

>> Can I download the bootstrap tarballs from the web interface of Hydra? > Why not do ‘guix build bootstrap-tarballs -s x86_64-linux --target=...’? When I tested the previous set of binaries (see the mips64el branch), it was necessary to adjust ‘%url-base’ in ‘build-aux/download.scm’. It seems

Re: MIPS64/N64 support

Nikita Karetnikov skribis: >> Oh indeed, using ‘-s’ was a good idea. Note that ‘guix build >> bootstrap-tarballs’ is even faster to type. > > Thanks. > >>> Which Guile do I need? The stripped one, right? > >> The one that’s in the output of ‘guix build bootstrap-tarballs’ (I >> forgot the name.

Re: MIPS64/N64 support

> Oh indeed, using ‘-s’ was a good idea. Note that ‘guix build > bootstrap-tarballs’ is even faster to type. Thanks. >> Which Guile do I need? The stripped one, right? > The one that’s in the output of ‘guix build bootstrap-tarballs’ (I > forgot the name.) Yep, the stripped one. Can I downlo

Re: MIPS64/N64 support

Nikita Karetnikov skribis: >> If you can cross-compile (really: substitute) them from x86_64, the >> better (you can even log in to hydra.gnu.org and get them from there.) >> Otherwise let me know and we’ll arrange something. > > $ ./pre-inst-env guix build binutils-static-stripped-tarball \ >

Re: MIPS64/N64 support

> If you can cross-compile (really: substitute) them from x86_64, the > better (you can even log in to hydra.gnu.org and get them from there.) > Otherwise let me know and we’ll arrange something. $ ./pre-inst-env guix build binutils-static-stripped-tarball \ bootstrap-b

Re: MIPS64/N64 support

Nikita Karetnikov skribis: >>> • MIPS64/N64 support: the bootstrap tarballs are now all available >>> through cross-compilation from x86_64, so it’s “just” a matter of >>> feeding them in bootstrap.scm and trying out. > >> I’m also interested in this one.

MIPS64/N64 support (was: Goals for 0.4)

>> • MIPS64/N64 support: the bootstrap tarballs are now all available >> through cross-compilation from x86_64, so it’s “just” a matter of >> feeding them in bootstrap.scm and trying out. > I’m also interested in this one. Oh, I forgot that I’ll need five tarballs, no