all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 28000@debbugs.gnu.org
Subject: [bug#28000] [PATCH] gnu: octave: Build with texinfo.
Date: Fri, 29 Sep 2017 20:25:06 +0530	[thread overview]
Message-ID: <0cd8914f.ADkAADSRXK4AAAAAAAAAAAPwTpIAAAACwQwAAAAAAAW9WABZzl7V@mailjet.com> (raw)
In-Reply-To: <877ewjalo5.fsf@fastmail.com>


Oops! I just realized that my patch doesn't work. Let me explain.

Octave uses makeinfo to render the built-in function documentation. So,
it complains when it is not able to find makeinfo. This is shown below:

octave:1> help sin
sh: makeinfo: command not found
warning: help: Texinfo formatting filter exited abnormally; raw Texinfo source of help text follows...
'sin' is a built-in function from the file libinterp/corefcn/mappers.cc

Moving texinfo to inputs does not fix this. I wrongly thought it did
because when I tested octave within the following environment, the
built-in documentation worked.

$ guix environment guix
$ ./pre-inst-env guix environment --ad-hoc octave

However, this was only because texinfo, having been pulled in by the
guix environment, was in the profile.

Now, I'll try to patch the octave source code so that it references the
makeinfo executable in the store. I will send a new patch when I'm done.

  reply	other threads:[~2017-09-29 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ddec1ecd.AEEARAgPOywAAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZylTD@mailjet.com>
2017-09-27 21:14 ` [bug#28000] [PATCH] gnu: octave: Build with texinfo Marius Bakke
2017-09-29 14:55   ` Arun Isaac [this message]
2017-08-07 10:43 Arun Isaac
2017-08-07 22:13 ` Marius Bakke
2017-09-26 13:23   ` Arun Isaac

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

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

  git send-email \
    --in-reply-to=0cd8914f.ADkAADSRXK4AAAAAAAAAAAPwTpIAAAACwQwAAAAAAAW9WABZzl7V@mailjet.com \
    --to=arunisaac@systemreboot.net \
    --cc=28000@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.