unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Daniel Kochmański" <dkochmanski@hellsgate.pl>
Cc: 19888-done@debbugs.gnu.org
Subject: bug#19888: [check][fail]
Date: Tue, 24 Feb 2015 00:03:36 +0100	[thread overview]
Message-ID: <87d250z0vr.fsf@gnu.org> (raw)
In-Reply-To: <85k2zgmtdl.fsf@hellsgate.pl> ("Daniel \=\?utf-8\?Q\?Kochma\=C5\=84\?\= \=\?utf-8\?Q\?ski\=22's\?\= message of "Tue, 17 Feb 2015 16:48:22 +0100")

Daniel Kochmański <dkochmanski@hellsgate.pl> skribis:

> I'm encountering an error when building guix from git (linux, archlinux, aur
> package guix-git) - make check returns three failed checks (see
> attachments).

[...]

> ./configure: ./config.status: /tmp/packerbuild-1000/guix-git/guix-git/src/guix/test-tmp/store/s5j6jzyqy26f0: bad interpreter: No such file or directory

I sounds like the shebang is actually longer than Linux’s static limit.

Indeed, the string
“/tmp/packerbuild-1000/guix-git/guix-git/src/guix/test-tmp/store/wzk9i3vyr53xiyxl6ar7ykyifxhfxqpv-bootstrap-binaries-0/bin/bash”
is exactly 126 characters, but BINPRM_BUF_SIZE in Linux, which accounts
for the entire shebang plus trailing zero, is 128.

Commit b69c5c2 works around that by skipping tests that would otherwise
hit this limit.

I will also add configure-time checks to at least warn about the risk of
such problems.

Thanks for the report!

Ludo’.

      reply	other threads:[~2015-02-23 23:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 15:48 bug#19888: [check][fail] Daniel Kochmański
2015-02-23 23:03 ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d250z0vr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=19888-done@debbugs.gnu.org \
    --cc=dkochmanski@hellsgate.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).