From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Somebody with gcc knowledge here? (Was: termcap moodule problem on Cygwin )
Date: Wed, 31 Jan 2001 10:00:18 +0100 (MET) [thread overview]
Message-ID: <200101310900.KAA05976@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Wed, 31 Jan 2001 11:50:03 +0300
Andrej Borsenkow wrote:
> > > - move termcap (and terminfo) back into main zsh.
> >
> > You could force it to be statically linked by changing the `link' line to
> > test for cygwin in termcap.mdd. See existing `link=' in terminfo.mdd for
> > how this works. You can make this depend on a configure test for whether
> > termcap is static.
> >
>
> Of course, I am idiot. Even more so as I cannot build zsh with static termcap:
So I'm not the only idiot. Good.
This happened to me, too. Somehow the Makefile calls the recursive
`make's twice when collection the module object files to be put into
stamp-modobjs. Since I don't really understand that part of the
Makefile anymore, I just added a `sort -u' in the rule that checks if
the new stamp-modobjs.tmp differs from existing stamp-modobjs. But I'm
pretty sure this isn't the right way to solve it.
Then I forgot to mention it on the list. Sorry.
So... Zefram? Anyone?
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2001-01-31 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 9:00 Sven Wischnowsky [this message]
2001-01-31 9:47 ` Bart Schaefer
2001-01-31 9:57 ` Andrej Borsenkow
2001-01-31 17:55 ` Zefram
2001-02-01 5:55 ` Andrej Borsenkow
2001-02-01 16:39 ` Bart Schaefer
2001-02-01 16:54 ` Andrej Borsenkow
2001-02-01 19:23 ` Zefram
2001-02-02 8:42 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2001-01-30 10:34 termcap moodule problem on Cygwin Peter Stephenson
2001-01-31 8:50 ` Somebody with gcc knowledge here? (Was: termcap moodule problem on Cygwin ) Andrej Borsenkow
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=200101310900.KAA05976@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).