all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Glenn Morris <rgm@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: makeinfo: missing file argument
Date: Thu, 5 Apr 2012 20:14:48 +0200	[thread overview]
Message-ID: <7021A856-25C8-4B65-A0B6-0827F62A7881@Web.DE> (raw)
In-Reply-To: <2my5qa4022.fsf@fencepost.gnu.org>


Am 5.4.2012 um 18:26 schrieb Glenn Morris:

> Kuroishi Mitsuo wrote:
> 
>> (cd doc/emacs; make  info)
>> /usr/bin/makeinfo --force --enable-encoding -I /home/kuroishi/download/emacs/doc/emacs -o /home/kuroishi/download/emacs/doc/emacs/../../info/emacs
>> makeinfo: missing file argument.
> 
> The questions I would ask are:
> 
> What version of make are you using?

Config.log tells: 

	checking whether we are using GNU Make
	result: no


> What is /bin/sh for you (eg bash, dash, etc)?

	SHELL='/bin/bash'  (from config.log too)


The make programme Mitsuo is using looks suspicious. I also wonder why configure uses lines like:

	checking for getifaddrs
	gcc -std=gnu99 -o conftest -g -O2     -Wl,-znocombreloc conftest.c  >&5 -L/usr/local/lib
	$? = 0
	result: yes

Shouldn't ">&5" come last? On a few occasions configure reports:

	gnome-config: not found
	result: no
	(checking for lgetfilecon in -lselinux)



The comparison also showed in *my* config.log file mostly the use of gcc, but there are also lines like:

	checking sys/un.h usability
	gcc -std=gnu99 -I/opt/local/include -L/opt/local/lib -c -g -O2 -I/opt/local/include      conftest.c >&5
	$? = 0
	result: yes
	checking sys/un.h presence
	cc -E -no-cpp-precomp -I/opt/local/include -L/opt/local/lib    conftest.c
	$? = 0
	result: yes
	checking for sys/un.h
	result: yes

At its end config.log has:
	
	ac_cv_prog_CPP='cc -E -no-cpp-precomp -I/opt/local/include -L/opt/local/lib'
	...
	CC='gcc -std=gnu99 -I/opt/local/include -L/opt/local/lib'
	CPP='cc -E -no-cpp-precomp -I/opt/local/include -L/opt/local/lib'

This looks also suspicious.


I must say that I don't know FreeBSD well enough to be more helpful in future. Looking into doc/emacs/Makefile (and comparing it with mine) is certainly a good option. Maybe we can see the cause why no file name is passed to makeinfo. Or are these lines obviously suspicious:

	EMACS_XTRA= \
		${srcdir}/emacs-xtra.texi \
		$(srcdir)/arevert-xtra.texi \
		$(srcdir)/cal-xtra.texi \
		$(srcdir)/dired-xtra.texi \
		$(srcdir)/picture-xtra.texi \
		$(srcdir)/emerge-xtra.texi \
		$(srcdir)/vc-xtra.texi \
		$(srcdir)/vc1-xtra.texi \
		$(srcdir)/fortran-xtra.texi \
		$(srcdir)/msdog-xtra.texi
	
	EMACSSOURCES= \
		${srcdir}/emacs.texi \
		${srcdir}/emacsver.texi \
		...
		${srcdir}/kmacro.texi \
		$(EMACS_XTRA)

Usually the syntax is:

	MACRO <white space> =

--
Greetings

  Pete

We have to expect it, otherwise we would be surprised.




  reply	other threads:[~2012-04-05 18:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  1:53 makeinfo: missing file argument Kuroishi Mitsuo
2012-04-04 16:00 ` Peter Dyballa
2012-04-05  0:18   ` Kuroishi Mitsuo
2012-04-05  9:23     ` Peter Dyballa
2012-04-05 13:22       ` Kuroishi Mitsuo
2012-04-05 13:31         ` Peter Dyballa
2012-04-05 16:26     ` Glenn Morris
2012-04-05 18:14       ` Peter Dyballa [this message]
2012-04-06  0:38       ` Kuroishi Mitsuo
2012-04-06  7:06         ` Glenn Morris
2012-04-06  7:22           ` Kuroishi Mitsuo
2012-04-06  7:32             ` Glenn Morris
2012-04-06  7:37               ` Glenn Morris
2012-04-06  9:16                 ` Peter Dyballa
2012-04-07 19:26                 ` Glenn Morris
2012-04-08  0:13                   ` Peter Dyballa
2012-04-08  6:01                   ` Kuroishi Mitsuo
2012-04-06  8:01               ` Kuroishi Mitsuo
2012-04-06  8:47                 ` Kuroishi Mitsuo
2012-04-06  8:59                 ` Peter Dyballa
2012-04-06  9:15                   ` Kuroishi Mitsuo
2012-04-06  9:52                   ` Eli Zaretskii

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=7021A856-25C8-4B65-A0B6-0827F62A7881@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rgm@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.