From: John Darrington <john@darrington.wattle.id.au>
To: Kete <kete@ninthfloor.org>
Cc: guix-devel@gnu.org
Subject: Re: Package Definition Place
Date: Sat, 4 Jan 2014 23:25:41 +0100 [thread overview]
Message-ID: <20140104222540.GA5270@intra> (raw)
In-Reply-To: <3887983.4DpMF5UtKy@knossos>
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
This is where you have to start doing some detective work and probably some patching!
Based on what you pasted, it looks as if CONFIG_SHELL isn't getting passed to the mkmakemod.sh file.
Probably the zsh devs have done something wierd.
What I do at this stage is to build with the -K flag, then you can manually enter the build directory which
guix places in /tmp/nix-build-* and start putting in diagnostics and running the build manually to find out
what is going on.
Sometimes it can be painful.
J'
On Sat, Jan 04, 2014 at 04:21:35PM -0500, Kete wrote:
On Saturday, January 04, 2014 08:15:40 AM John Darrington wrote:
> The example in bash.scm is over complicated. Look at some of the examples
> in xorg.scm to see how to set configure-flags.
That got me a little further.
Src/../Src/mkmakemod.sh: line 467: /bin/sh: No such file or directory
Makefile:299: recipe for target 'Makemod' failed
These are the lines around 464-470:
if $second_stage ; then
trap "rm -f $the_subdir/${the_makefile}; exit 1" 1 2 15
${CONFIG_SHELL-/bin/sh} ./config.status \
--file=$the_subdir/${the_makefile}:$the_subdir/${the_makefile}.in ||
exit 1
fi
I tried with the --without-tcsetpgrp flag, but I got the same error.
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-04 22:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 3:55 Package Definition Place Kete
2013-12-30 7:16 ` John Darrington
2013-12-31 0:37 ` Kete
2014-01-01 12:52 ` John Darrington
2014-01-01 16:05 ` Kete
[not found] ` <1458111.8sUPPTkUlg@knossos>
[not found] ` <20140101160917.GA13487@intra>
2014-01-01 16:32 ` Kete
2014-01-01 16:50 ` John Darrington
2014-01-01 19:13 ` Kete
2014-01-01 19:55 ` John Darrington
2014-01-01 20:38 ` Kete
2014-01-01 22:30 ` Kete
2014-01-02 2:44 ` Nikita Karetnikov
2014-01-02 2:50 ` Nikita Karetnikov
2014-01-02 10:06 ` Kete
2014-01-02 14:58 ` Nikita Karetnikov
2014-01-02 23:45 ` Kete
2014-01-03 2:28 ` Kete
2014-01-03 5:50 ` John Darrington
2014-01-03 11:37 ` Kete
2014-01-03 15:16 ` Nikita Karetnikov
2014-01-03 15:19 ` Ludovic Courtès
2014-01-04 1:10 ` Kete
2014-01-04 7:15 ` John Darrington
2014-01-04 21:21 ` Kete
2014-01-04 22:25 ` John Darrington [this message]
2014-01-05 18:21 ` Ludovic Courtès
2014-01-04 11:47 ` Ludovic Courtès
2014-01-04 21:31 ` Kete
2014-01-05 17:57 ` Ludovic Courtès
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=20140104222540.GA5270@intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=kete@ninthfloor.org \
/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).