From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Porting to mips64el Date: Fri, 11 Jan 2013 14:28:33 +0100 Message-ID: <87a9sfc0hq.fsf@gnu.org> References: <8738yvnslh.fsf@karetnikov.org> <87y5gfa7t9.fsf@gnu.org> <87vcbjldp5.fsf@karetnikov.org> <87zk0v4e29.fsf@gnu.org> <87wqvzclyj.fsf@karetnikov.org> <87ehi71bl6.fsf@gnu.org> <87pq1rma9g.fsf@karetnikov.org> <87wqvyxvhv.fsf@gnu.org> <87lic3vm8s.fsf@karetnikov.org> <871udv6bny.fsf@gnu.org> <87d2xfk9qb.fsf@karetnikov.org> <87k3rnr61e.fsf@gnu.org> <871udvwna6.fsf@karetnikov.org> <876237bdqu.fsf@gnu.org> <87y5g2uzbj.fsf@karetnikov.org> <87y5g2kp8s.fsf@gnu.org> <87d2xc4azh.fsf@karetnikov.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:37432) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttef1-0008W8-CP for bug-guix@gnu.org; Fri, 11 Jan 2013 08:28:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tteey-0008NE-DT for bug-guix@gnu.org; Fri, 11 Jan 2013 08:28:39 -0500 Received: from mail4-relais-sop.national.inria.fr ([192.134.164.105]:37171) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tteey-0008N9-76 for bug-guix@gnu.org; Fri, 11 Jan 2013 08:28:36 -0500 In-Reply-To: <87d2xc4azh.fsf@karetnikov.org> (Nikita Karetnikov's message of "Thu, 10 Jan 2013 23:08:51 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Nikita Karetnikov Cc: bug-guix@gnu.org Hi, Nikita Karetnikov skribis: >> I think Llu=C3=ADs said that something must be added to ~/.nixpkgs/confi= g.nix >> to make sure the right platform setup is used, but again, I have no >> expertise in MIPS64 so I can=E2=80=99t really help. > > Thanks, I forgot about 'config.nix'. Unfortunately, it didn't help. It seems we=E2=80=99re still missing something, because my understanding is= that Llu=C3=ADs has it working on basically the same hardware. Unfortunately, I= =E2=80=99m ignorant about all things MIPS. >> Yes, I think you reported it earlier. This could be either a sign of >> not enough memory, or perhaps that the consequence of trying to run an >> invalid binary (such as a corrupt ELF executable.) > > How can I test the latter? You could run =E2=80=98nix-build -A stdenv -K /path/to/nixpkgs=E2=80=99. U= pon glibc build failure, just get into the failed build tree: $ sudo chown -r $USER /tmp/nix-build-*glibc-2.13* $ cd /tmp/nix-build-*glibc-2.13* $ source env-vars $ cd build $ make And then =E2=80=98strace=E2=80=99 as needed, etc. (This is admittedly very generic advice, but again the best I can say.) > Will it help if I build something without Nixpkgs? (What should I > build?) As noted in =E2=80=98HACKING=E2=80=99, if you want to avoid Nixpkgs, you co= uld try to use the installed distro tools as a replacement for those normally provided by bootstrap.scm. The way to do it would be along the lines of: (define %bootstrap-gcc (package (name "gcc-bootstrap") (source #f) (build-system trivial-build-system) (arguments '(#:builder (begin (use-modules (guix build utils)) (define out (assoc-ref %outputs "out")) (define bin (string-append out "/bin")) (mkdir-p bin) (symlink "/usr/bin/gcc" (string-append bin "/gcc"))))) ;; ... )) And similarly for %bootstrap-glibc, %bootstrap-guile, and all the others. Then you would run =E2=80=98guix-daemon --disable-chroot=E2=80=99, and try: $ ./pre-inst-env guix-build bootstrap-tarballs -K I=E2=80=99ve never done that, so you=E2=80=99re on your own, but in princip= le it should work. HTH, Ludo=E2=80=99.