From: Alchemist Matt <monroem@email.unc.edu>
To: zsh-users@math.gatech.edu
Subject: Zsh-3.1.3 compile
Date: Mon, 4 May 1998 12:07:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.3.95L.980504120217.14399B-100000@sunny.isis.unc.edu> (raw)
Hi,
I'm trying to compile v3.1.3 of Zsh. I've successfully compiled
version 3.1.2 and others in the past by simply typing
configure --prefix=./new/
and then
make
which successfully creates the executable.
With v3.1.3, I run configure and it ends with the message:
creating ./config.status
creating Makefile
Can't open :Makefile.in
creating Doc/Makefile
Can't open :Doc/Makefile.in
creating Etc/Makefile
Can't open :Etc/Makefile.in
creating Src/Makefile
Can't open :Src/Makefile.in
creating config.h
cat: cannot open :config.h.in
config.h is unchanged
zsh configuration
-----------------
zsh version : 3.1.3
host operating system : sparc-sun-solaris2.5.1
source code location : .
compiler : gcc
executable compiler flags : -Wall -Wno-implicit -Wmissing-prototypes -O2
executable linker flags : -s
binary install path : ./new//bin
man page install path : ./new//man
info install path : ./new//info
With the previous versions I did not get these "can't open" errors.
If I type "ls *.in" I see:
-rw------- 1 monroem graduate 3486 Apr 30 16:55 Makefile.in
-rw------- 1 monroem graduate 12903 Apr 28 19:34 config.h.in
-rw------- 1 monroem graduate 31754 Apr 30 18:03 configure.in
-rw------- 1 monroem graduate 1 Apr 30 18:09 stamp-h.in
so it looks like the files were created just fine. Any suggestions?
Thanks,
Matt
-----------------------------------------------------------------------
Matthew Monroe Monroem@UNC.Edu
Analytical Chemistry http://www.unc.edu/~monroem/
UNC - Chapel Hill This tagline is umop apisdn
_____
Q's Baby?. Q hosts a game show.
-----------------------------------------------------------------------
reply other threads:[~1998-05-04 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.GSO.3.95L.980504120217.14399B-100000@sunny.isis.unc.edu \
--to=monroem@email.unc.edu \
--cc=zsh-users@math.gatech.edu \
/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).