From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: error compiling shadow 4.1.5.1
Date: Tue, 21 May 2013 17:42:53 -0700 [thread overview]
Message-ID: <20130521174253.6df5590b@newbook> (raw)
In-Reply-To: <519B6A4A.8030809@barfooze.de>
On Tue, 21 May 2013 14:36:26 +0200
John Spencer <maillist-musl@barfooze.de> wrote:
> On 05/21/2013 06:49 AM, Isaac Dunham wrote:
> > Adding<sys/socket.h> above<netdb.h> helps get it building.
> [...]
> > undefining this makes it build.
In other words, use this command line:
ac_cv_member_struct_utmp_ut_addr_v6=no \
ac_cv_member_struct_utmpx_ut_addr_v6=no \
/configure --without-nscd --without-libpam
But "it" is "one particular file", not the whole package.
login still FTBFS.
ut_addr_v6 being detected breaks things for a completely unrelated
reason, though:
sizeof(sa->sin_addr) and sizeof(sa->sin6_addr)
are failing.
But what's a good replacement? Or shall we make it transparent?
> do you have a patch handy ?
See this part:
> > Finally, there's an unconditional use of ruserok; of course they
> > check whether it returns 0 or 1 on failure, but assume it's present!
> maybe we also should report the bugs upstream.
The status at present:
-missing <sys/socket.h> in libmisc/utmp.c
-need to make ruserok conditional.
-(musl or upstream bug?) shadow assumes that members sin(6)_addr of
struct sockaddr_in (type struct in(6)_addr) are completely defined.
Do we want to implement ruserok?
Here's a (public domain) ruserok stub conforming to the manual
description:
int ruserok(const char *rhost, int s, const char *ruser, const
char *luser)
{
return -1;
}
Thanks,
Isaac Dunham
prev parent reply other threads:[~2013-05-22 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 0:17 Matias A. Fonzo
2013-05-21 2:58 ` Isaac Dunham
2013-05-21 3:14 ` Rich Felker
2013-05-21 4:49 ` Isaac Dunham
2013-05-21 12:36 ` John Spencer
2013-05-22 0:42 ` Isaac Dunham [this message]
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=20130521174253.6df5590b@newbook \
--to=idunham@lavabit.com \
--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).