zsh-users
 help / color / mirror / code / Atom feed
From: Danek Duvall <duvall@lorien.emufarm.org>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
Cc: "Roland Jesse" <jesse@mail.CS.Uni-Magdeburg.De>,
	"Zsh Users" <zsh-users@sunsite.auc.dk>
Subject: Re: 3.1.9 build fails at zftp.c when using Sun's WorkShop Compilers 5.0
Date: Fri, 18 Aug 2000 10:11:24 -0700	[thread overview]
Message-ID: <20000818101124.A9766@lorien.emufarm.org> (raw)
In-Reply-To: <000e01c00931$656c7cb0$21c9ca95@mow.siemens.ru>

On Fri, Aug 18, 2000 at 08:28:52PM +0400, Andrej Borsenkow wrote:

> I just found, that these live in -lresolv here. Damn, some developers should
> be shoot on the spot ... the problem (here, at least) is, that -lresolv MUST
> be after -lnsl (else name resolution won't work), so usual configure checks
> won't work ... I have to think about it.
> 
> Check, in which library these function live under Solaris. I suspect, they are
> in -lresolv as well.

On Solaris, inet_pton and friends live in -lnsl.  -lnsl and -lresolv are not
both necessary, only the former.  And -lsocket seems to require -lnsl.

Configure seems to always do the right thing on Solaris with regard to the
networking libraries, though.  And I do have a version of zsh 3.1.9-dev-1
built on Solaris 8 with the 5.0 compilers ...

Danek


  parent reply	other threads:[~2000-08-18 17:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-18 15:52 Roland Jesse
2000-08-18 16:09 ` Andrej Borsenkow
2000-08-18 16:12   ` Roland Jesse
2000-08-18 16:28     ` Andrej Borsenkow
2000-08-18 16:41       ` Andrej Borsenkow
2000-08-18 17:11       ` Danek Duvall [this message]
2000-08-21  6:54         ` Andrej Borsenkow
2000-08-21  7:02           ` Danek Duvall
2000-08-21 10:58             ` nm from networks libraries on Solaris 7, 8, 2.6? Andrej Borsenkow
2000-08-21 16:29               ` Danek Duvall

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=20000818101124.A9766@lorien.emufarm.org \
    --to=duvall@lorien.emufarm.org \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=jesse@mail.CS.Uni-Magdeburg.De \
    --cc=zsh-users@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).