From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: Clint Adams <schizo@debian.org>
Cc: zsh-workers@sunsite.dk, Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Subject: Re: Fwd: Re: zsh compilation problem with autoconf git
Date: Wed, 30 Jan 2008 06:42:40 +0200 [thread overview]
Message-ID: <200801300642.40468.ismail@pardus.org.tr> (raw)
In-Reply-To: <20080129223819.GA12715@scowler.net>
[ Removed bug-autoconf from CC because this might be off topic for them ]
Wednesday 30 January 2008 00:38:19 tarihinde Clint Adams şunları yazmıştı:
> On Wed, Jan 30, 2008 at 12:03:33AM +0200, Ismail Dönmez wrote:
> > Hi Ralf,
> >
> > I am forwarding your message to zsh-workers list. To summarise the issue
> > zsh modules are not compiled with upcoming autoconf 2.62 and Ralf
> > successfully identified that zsh/Src/mkmakemod.sh does some unportable
> > stuff :
> >
> > # check 2.13, 2.50, and 2.60 syntaxes
> > if grep '%@D@%D%' config.status >/dev/null ||
> > grep ',@D@,D,' config.status >/dev/null ||
> > grep ',@D@,|#_!!_#|D,' config.status >/dev/null; then
> > is_dynamic=true
> > else
> > is_dynamic=false
> > fi
> >
> > So the question is, is this thing needed at all, if yes why?
>
> Presumably Src/mkmakemod.sh would need to be generated to check that
> value in any supported manner. I don't recall a reason that that
> can't be done.
Why doesn't it parse config.h instead? I got
#define DYNAMIC 1
in config.h so this could be grepped easily.
Regards,
ismail
--
Never learn by your mistakes, if you do you may never dare to try again.
next prev parent reply other threads:[~2008-01-30 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 22:03 Ismail Dönmez
2008-01-29 22:38 ` Clint Adams
2008-01-30 4:42 ` Ismail Dönmez [this message]
2008-01-30 6:48 ` Ralf Wildenhues
2008-01-30 9:57 ` Peter Stephenson
2008-01-30 13:03 ` Eric Blake
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=200801300642.40468.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=Ralf.Wildenhues@gmx.de \
--cc=schizo@debian.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).