mailing list of musl libc
 help / color / mirror / code / Atom feed
From: ojab <ojab@ojab.ru>
To: musl@lists.openwall.com
Subject: Re: libedit build, missing sys/ttydefaults.h & sys/errno.h
Date: Fri, 14 Dec 2012 00:15:25 +0400	[thread overview]
Message-ID: <50CA375D.1060305@ojab.ru> (raw)
In-Reply-To: <20121213185837.GC20323@brightrain.aerifal.cx>

On 13.12.2012 22:58, Rich Felker wrote:
> On Thu, Dec 13, 2012 at 02:29:28PM +0400, ojab wrote:
>> >Hi list,
>> >
>> >libedit-3.0 build fails with
>> >
>>> > >editline/readline.h:79:29: fatal error: sys/ttydefaults.h: No such file or directory
>>> > >fileman.c:14:23: fatal error: sys/errno.h: No such file or directory
>> >
>> >After adding sys/ttydefaults.h from NetBSD [1] (cleaned up version
>> >in the attached file) and replacing <sys/errno.h> with <errno.h> it
>> >builds/works fine.
>> >As far as I can see the same issues was reported about sysvinit [2].
>> >
>> >Can sys/ttydefaults.h be added to musl? Will <sys/errno.h> alias be
>> >added to musl? Or I should report issue to libedit developer
>> >instead?
> So far, support for wrong-location headers like <sys/errno.h> is
> inconsistent; we support some of them but not others. The long-term
> plan is to support all of the ones glibc does, but with #warning in
> the wrong version of it. I think you should report the bug upstream
> and try to get it fixed. It's definitely been more than 20 years since
> there was a system where <sys/errno.h> was needed, and I doubt such
> systems existed even back then.
>
> As for <sys/ttydefaults.h>, I'll look at it. I'm not familiar with
> what it's for. But it seems unused...
>
> Rich
>

Just FIY: issue with <errno.h> reported and already fixed in libedit.

//wbr ojab


  reply	other threads:[~2012-12-13 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 10:29 ojab
2012-12-13 17:25 ` John Spencer
2012-12-13 18:58 ` Rich Felker
2012-12-13 20:15   ` ojab [this message]
2012-12-13 20:40 ` John Spencer

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=50CA375D.1060305@ojab.ru \
    --to=ojab@ojab.ru \
    --cc=musl@lists.openwall.com \
    /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/musl/

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).