From: Chris Gehlker <gehlker@fastq.com>
To: Zefram <zefram@fysh.org>
Cc: <zsh-workers@sunsite.dk>
Subject: Re: zsh 4.0.2 (powerpc-apple-darwin1.4)
Date: Sun, 07 Oct 2001 17:28:17 -0700 [thread overview]
Message-ID: <B7E64131.1E52C%gehlker@fastq.com> (raw)
In-Reply-To: <20011008001533.A7577@fysh.org>
On 10/7/01 4:15 PM, "Zefram" <zefram@fysh.org> wrote:
>>> configure goes to some effort to avoid using the -s flag where that
>>> wouldn't work.
>
> But it only makes that effort when it's likely to need it, which is when
> it's doing dynamic module loading. The configure output you provided
> showed that it didn't find any dynamic linking facilities that it
> could use.
>
> Why did you have to remove the -s flags? With -s left in, did it fail
> to build, or did you get an executable that didn't work? What error
> messages were produced?
The compiler barfed on the -s. It produced pages of output without so much
as a warning. Then, as you can see below, it hit the -s and stopped with an
error message. I'm pasting the last few lines of make's output below. The
rest looks uninteresting but I'll send it if you want.
cc -c -I. -DHAVE_CONFIG_H -Wall -Wno-implicit -Wmissing-prototypes -O2 -o
main.o ./main.c
( echo '#!'; cat builtin.syms compat.syms cond.syms exec.syms glob.syms
hashtable.syms hist.syms init.syms input.syms jobs.syms lex.syms
linklist.syms loop.syms math.syms mem.syms module.syms options.syms
params.syms parse.syms pattern.syms prompt.syms signals.syms signames.syms
string.syms subst.syms text.syms utils.syms watch.syms | sed -n
'/^X/{s/^X//;p;}' | sort -u ) > zsh.export
rm -f zsh
cc -s -o zsh main.o `cat stamp-modobjs` -lm -lc
/usr/bin/ld: warning unused multiple definitions of symbol _glob
glob.o definition of _glob in section (__TEXT,__text)
/usr/lib/libm.dylib(glob.o) unused definition of _glob
/usr/bin/ld: can't use -s with input files containg indirect symbols (output
file must contain at least global symbols, for maximum stripping use -x)
make[1]: *** [zsh] Error 1
make: *** [all] Error 1
The compiler docs say it's GNU 2.7.2 with certain extensions to support
Objective C and AltiVec instructions.
As always, feel free to ask if I can provide more help.
-Chris
--
Adults are obsolete children.
-Dr. Seuss, humorist, illustrator, and author (1904-1991)
next prev parent reply other threads:[~2001-10-08 0:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-07 8:26 Chris Gehlker
2001-10-07 11:50 ` Zefram
2001-10-07 16:06 ` Chris Gehlker
2001-10-07 23:15 ` Zefram
2001-10-08 0:28 ` Chris Gehlker [this message]
2001-10-08 6:42 ` Borsenkow Andrej
2001-10-08 8:07 ` Peter Stephenson
2001-10-08 9:43 ` Borsenkow Andrej
2001-10-08 10:02 ` Bart Schaefer
2001-10-08 6:30 ` Borsenkow Andrej
2001-10-08 6:36 ` Geoff Wing
2001-10-08 6:40 ` Geoff Wing
2001-10-08 9:41 ` Oliver Kiddle
2001-10-08 9:53 ` Bart Schaefer
[not found] ` <3BC1737C.9F680641@yahoo.co.uk>
2001-10-08 13:26 ` Geoff Wing
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=B7E64131.1E52C%gehlker@fastq.com \
--to=gehlker@fastq.com \
--cc=zefram@fysh.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).