From: Wes Morgan <wesm@slacknet.org>
To: zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: Compiling zsh-4.0.2 on Mac OS X
Date: Sun, 23 Sep 2001 17:43:54 -0400 [thread overview]
Message-ID: <3BAE579A.3010205@slacknet.org> (raw)
In-Reply-To: <3B8FCFC4.869C0D51@yahoo.co.uk>
This patch causes the "checking for executable suffix..." test in the
configure script to fail with "compiler cannot create executables." The
man page for ld on Mac OS X says that -x overlaps with a compiler option
and that to invoke it from cc, it needs to be specified as "-Wl,-x". I
changed this in the configure script and configure worked again. Then
"make" succeeded, but "make check" had some problems. I don't know if
they are specific to OS X or something I did/didn't do. Here's the errors:
Test ./C02cond.ztst failed: bad status 1, expected 0 from:
[[ -k modish && ! -k zerolength ]]
Was testing: -k cond
Test ./Y01completion.ztst failed: non-zero status from preparation code:
comptestinit -z $ZTST_testdir/../Src/zsh
Test ./Y01completion.ztst failed: bad status 1, expected 0 from:
comptest $': \t\t\t\t\t\t\t'
Error output:
comptest:2: command not found: zpty
comptest:3: command not found: zpty
Was testing: directories and files
Test ./Y02compmatch.ztst failed: non-zero status from preparation code:
comptestinit -z $ZTST_testdir/../Src/zsh
Test ./Y02compmatch.ztst failed: bad status 1, expected 0 from:
test_code z: list1
comptest $'tst \t'
Error output:
comptesteval:4: command not found: zpty
comptesteval:5: command not found: zpty
comptest:2: command not found: zpty
comptest:3: command not found: zpty
Was testing: Match Error for "z:"
Test ./Y03arguments.ztst failed: bad status 1, expected 0 from:
tst_arguments ':desc1:(arg1)'
comptest $'tst \t\C-wa\t\C-war\t\C-warg\t\C-warg1\t\C-wr\t\C-wx\t \ty \t'
Error output:
comptesteval:4: command not found: zpty
comptesteval:5: command not found: zpty
comptest:2: command not found: zpty
comptest:3: command not found: zpty
Was testing: one non-option argument
Thanks,
Wes Morgan
Oliver Kiddle wrote:
>Brian Boonstra wrote:
>
>> I solved this by running
>> autoconf
>>in the top-level source directory. That gave me a configure script with
>>more options, including one for the ldflags, which I then set to be nothing.
>>
>
>I take it there no problems with the clear ldflags then?
>
>> I suppose this is ultimately a problem with autoconf.
>>
>
>What version of autoconf do you have? I'd be suprised if 2.5x doesn't
>handle MacOS X.
>
>Judging by one section of zshconfig.ac, it is probably a zsh problem.
>Can you try with this patch. You will need to rerun autoconf (or
>Util/preconfig) or manually apply this to configure itself.
>
>Does anyone know if ${enable_zsh_debug} is definitely empty for a no
>value as I've assumed here? The -x option may not be right in which case
>we could use nothing.
>
>Oliver
>
>Index: zshconfig.ac
>===================================================================
>RCS file: /cvsroot/zsh/zsh/zshconfig.ac,v
>retrieving revision 1.17
>diff -u -r1.17 zshconfig.ac
>--- zshconfig.ac 2001/07/03 17:34:33 1.17
>+++ zshconfig.ac 2001/08/31 17:47:17
>@@ -307,6 +307,7 @@
> if test -n "$auto_ldflags"; then
> case "${enable_zsh_debug}$host_os" in
> yesaix*|yeshpux*|yesnetbsd*|yesopenbsd*) ;; # "ld -g" is not valid
>on these systems
>+ darwin*) LDFLAGS=-x ;;
> yes*) LDFLAGS=-g ;;
> *) LDFLAGS=-s ;;
> esac
>
>_____________________________________________________________________
>This message has been checked for all known viruses by the
>MessageLabs Virus Scanning Service. For further information visit
>http://www.messagelabs.com/stats.asp
>
next prev parent reply other threads:[~2001-09-23 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 23:58 Wes Morgan
2001-07-25 5:31 ` Borsenkow Andrej
2001-07-30 15:27 ` Clint Adams
2001-08-31 17:12 ` Brian Boonstra
2001-08-31 17:56 ` Oliver Kiddle
2001-09-23 21:43 ` Wes Morgan [this message]
2001-09-24 5:51 ` Borsenkow Andrej
2001-09-27 14:19 ` Oliver Kiddle
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=3BAE579A.3010205@slacknet.org \
--to=wesm@slacknet.org \
--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).