From: Philippe Troin <phil@fifi.org>
To: ML.Dowling@tu-bs.de
Cc: zsh-workers@sunsite.dk
Subject: Re: Problem with the configure script (2.4.2)
Date: 19 Mar 2005 07:44:01 -0800 [thread overview]
Message-ID: <87y8cj8wu6.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <20050315163810.GA24540@moocow.localhost>
Mike Dowling <ML.Dowling@tu-bs.de> writes:
> Hello,
>
> I cannot get configure to produce a Makefile or a config.h file. I
> suspect that the problem lies with me, but I would be very grateful for
> any hints as to how I can solve the problem.
>
> #./configure
>
> produces lots of output, as usual, and perminates with
>
> checking for sbrk() prototype in <unistd.h>... yes
> checking for ioctl prototype in <sys/ioctl.h>... yes
> checking for mknod prototype in <sys/stat.h>... yes
> checking if named FIFOs work... yes
> checking if echo in /bin/sh interprets escape sequences... yes
> checking if link() works... yes
> checking if kill(pid, 0) returns ESRCH correctly... yes
> checking if POSIX sigsuspend() works... yes
>
> Everything looks fine, until I enter
>
> #make
> make: *** No targets specified and no makefile found. Stop.
>
> But there's no Make file. config.log also looks inoccuous enough
> (attached).
>
> What could possibly be going wrong?
Maybe the sigsuspend() test wrecks the configure process. That could
be related to users/20886.
Can you try running configure with sh -x, like in:
sh -x ./configure <configure-options>
to see where zsh stops?
Please send the gziped output to the list, not the full thing. Or the
tail of the file.
Phil.
next prev parent reply other threads:[~2005-03-19 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 16:38 Mike Dowling
2005-03-19 15:44 ` Philippe Troin [this message]
2005-03-19 15:52 ` Andrey Borzenkov
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=87y8cj8wu6.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=ML.Dowling@tu-bs.de \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).