tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Cc: Sevan Janiyan <venture37@geeklan.co.uk>
Subject: Re: Fwd: textproc/mdocml 1.13.3 on Solaris 10
Date: Mon, 16 Mar 2015 18:25:02 +0100	[thread overview]
Message-ID: <20150316172502.GA895@britannica.bec.de> (raw)
In-Reply-To: <20150316153511.GA3872@athene.usta.de>

On Mon, Mar 16, 2015 at 04:35:11PM +0100, Ingo Schwarze wrote:
> Hi Sevan,
> 
> Kristaps Dzonsons cited Sevan Janiyan on Mon, Mar 16, 2015 at 09:58:39PM +0900:
> 
> > I've just stumbled across an issue with mdocml when building on
> > Solaris 10 via pkgsrc-current, mkdtemp(), dirfd() and vasprintf() are
> > not available on there hence build fails:
> 
> It is hard to believe these are really unavailable.  mkdtemp() and dirfd()
> are POSIX 2008.  Admittedly, vasprintf() is a GNU extension, but it is
> so common and important that i don't understand how a system could live
> without it.

Solaris 10 is likely older than POSIX 2008, so no real surprise there...

> Besides, this is a *linker* failure.  If these functions were really
> unavailable, there would be no prototypes in the header files, and
> the *compiler* would already fail.  So i suspect somebody merely
> hid the object code away in some other shared library, not -lc.

Missing prototypes are normally only a warning.

That said, since this is in the context of pkgsrc, the problem is likely
just missing logic for using LDADD.

Joerg
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2015-03-16 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <550659F9.8040505@geeklan.co.uk>
2015-03-16 12:58 ` Kristaps Dzonsons
2015-03-16 15:35   ` Ingo Schwarze
2015-03-16 17:25     ` Joerg Sonnenberger [this message]
     [not found]     ` <55072EB8.6060905@geeklan.co.uk>
     [not found]       ` <55072F9B.2040706@geeklan.co.uk>
2015-03-18 19:51         ` Ingo Schwarze

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=20150316172502.GA895@britannica.bec.de \
    --to=joerg@britannica.bec.de \
    --cc=tech@mdocml.bsd.lv \
    --cc=venture37@geeklan.co.uk \
    /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.
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).