zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: honor STRIPFLAGS for modules
Date: Thu, 19 Apr 2001 20:28:27 +0100	[thread overview]
Message-ID: <3ADF3C5B.A508F9E2@u.genie.co.uk> (raw)
In-Reply-To: <20010419134611.A370@dman.com>

Clint Adams wrote:
> 
> > Does zsh_SEARCH_LIBS really need to do everything with AC_TRY_LINK_FUNC
> > then - couldn't it just save and restore LIBS and use AC_SEARCH_LIBS?
> 
> It could.  I thought that this way would be cleaner.  How would you

If it's a choice between configure or configure.in being cleaner, I'd
favour keeping configure.in cleaner because it is the one which has to
be understood by humans. I envisioned zsh_SEARCH_LIBS as just being save
LIBS, call AC_SEARCH_LIBS, restore LIBS making it simpler but I probably
am missing half its point such as if it needs to know what was added to
LIBS.

> determine what had been added by AC_SEARCH_LIBS in that event?

On the basis that we're limited to compatible /bin/sh code, comparing
SAVELIBS to LIBS isn't easy so fair enough.

> Well, this does have the side effect of having -l{termcap,curses,ncurses}
> being duplicated if they are one and the same for termcap and terminfo.

> The issue was not redundant libraries, however; it was unused libraries.

I'm not sure that I understand the difference. I only just realised that
on Linux termcap and curses are symlinked - yuk. So I guess the initial
patch was removing the duplicates by doing symbol searches to detect if
termcap/curses are one and the same which is fair enough provided there
is some tangible benefit of not linking both. If you say it makes a
difference on Linux then fine. I'm just not clear on why it was an
improvement other than possibly making the compile system cleaner. If
I'm asking stupid questions, ignore me: normally I'd have assumed you
know what you're doing and kept quiet if I didn't fully understand but
in this case I'm afraid I didn't.

So, this latest patch seems to be separating LIBS, and MAINLIBS for DSOs
and the main zsh binary - right? It sounds to me from the discussion
though that we almost need a separate $LIBS for every single module
though which is a bit worrying. Is the initial thing which has sparked
this off that the termcap/terminfo modules are the first modules which
are using libraries which the main zsh never previously loaded? Could
LIBS maybe remain just the common libraries and we then add the extra
libraries for the termcap module only?

Also, a while back when you implemented ${(k)terminfo} you asked if you
should also do this for termcap. Sorry if this is already done but if
not, I'd just like to add my vote in favour, even if you need to
constant table of termcap codes - it'd be useful.

Oliver


  reply	other threads:[~2001-04-19 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19  1:39 Clint Adams
2001-04-19  2:24 ` Zefram
2001-04-19 11:18 ` Oliver Kiddle
2001-04-19 12:40   ` Clint Adams
2001-04-19 17:15     ` Oliver Kiddle
2001-04-19 17:46       ` Clint Adams
2001-04-19 19:28         ` Oliver Kiddle [this message]
2001-04-19 19:47           ` Clint Adams

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=3ADF3C5B.A508F9E2@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --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).