From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: "guix environment --pure" different to guix-daemon's environment Date: Sat, 31 Mar 2018 22:33:04 +0200 Message-ID: <87605chtof.fsf@gnu.org> References: <20180331005317.073c34e4@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48646) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f2NC3-0005kr-C0 for guix-devel@gnu.org; Sat, 31 Mar 2018 16:33:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f2NBx-00025I-Ka for guix-devel@gnu.org; Sat, 31 Mar 2018 16:33:40 -0400 Received: from hera.aquilenet.fr ([185.233.100.1]:41148) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f2NBx-00024c-E7 for guix-devel@gnu.org; Sat, 31 Mar 2018 16:33:37 -0400 In-Reply-To: <20180331005317.073c34e4@scratchpost.org> (Danny Milosavljevic's message of "Sat, 31 Mar 2018 00:53:17 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Danny Milosavljevic Cc: guix-devel@gnu.org Hello! Danny Milosavljevic skribis: > so I'm trying to get mrustc to work (see attachment) but I've hit a snag. > > When I use "guix build", gcc will eventually fail with SIGABRT. > When I then try to reproduce the problem via "guix environment" gcc works= just > fine (using the failed tempdir and the failed command line). > > What could be up in this case? Did you try =E2=80=98guix environment -C=E2=80=99? There=E2=80=99d still b= e a few differences compared to what guix-daemon does, but not that much (info "(guix) Debugging Build Failures"). > Can I get guix-daemon to make gcc dump core on SIGABRT? (setrlimit in a b= uild phase? :->) Yes, you can! :-) Add a phase that does this: ;; Allow us to dump core during the test suite so GDB ;; can report backtraces. (let ((MiB (* 1024 1024))) (setrlimit 'core (* 300 MiB) (* 500 MiB))) (From .) HTH, Ludo=E2=80=99.