From: idunham@lavabit.com
To: musl@lists.openwall.com
Subject: Re: R/GNU S: up with a couple hitches...
Date: Wed, 19 Sep 2012 00:17:34 -0400 (EDT) [thread overview]
Message-ID: <50767.132.241.246.168.1348028254.squirrel@lavabit.com> (raw)
In-Reply-To: <20120915000624.0e7cd735.idunham@lavabit.com>
> On Fri, 14 Sep 2012 23:51:10 -0400
> Rich Felker <dalias@aerifal.cx> wrote:
>
>> On Fri, Sep 14, 2012 at 08:21:07PM -0700, Isaac Dunham wrote:
...
>> > Not yet, unless you're using the g_hack branch and don't need rpc to
>> > actually _work_. libtirpc needs getifaddrs.
>>
>> Is the getifaddrs code there license-compatible with musl?
> Yes but it's only a stub I wrote (hence the comment about "don't need rpc
> to actually _work_"). It will almost certainly leave any software that
> uses getifaddrs crippled.
> And no, I' haven't tested what builds with it. Probably nothing in its
> present state (I don't have a proper header yet).
I have since gone looking and found that newlib has a BSDi-based version,
which looks like it might be usable on some arches with some minor (?)
changes and cleanup. There's a note about one codepath not being LP64
friendly, though, as well as one abort() that should be turned into a
retry or failure. (Apple used the same base for implementing getifaddrs,
FWIW)
Refer to newlib/libc/sys/linux/net/getifaddrs.c in the newlib source tree.
Not sure if
http://www.kegel.com/dkftpbench/dkftpbench-0.45/getifaddrs.c
ftp://ftp.inet.no/pub/barefoot/extracted/libscompat/getifaddrs.c
(elinks) src/osdep/getifaddrs.c
are worthwhile, though they are compatibly licensed (BSDi or 3-clause
BSDish).
> Also, I have mentioned once or twice that getifaddrs, when implemented,
> will require (BSD) <sys/queue.h> TAILQ_* macros. If any header contains
> copyrightable material, it's this one: hundreds of LOCs, implementing
> linked lists in macros.
<sys/queue.h> will only be needed for source compatibility only, not for
implementing it.
next prev parent reply other threads:[~2012-09-19 4:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 4:29 idunham
2012-09-13 4:41 ` Rich Felker
2012-09-13 7:08 ` Daniel Cegiełka
2012-09-15 3:21 ` Isaac Dunham
2012-09-15 3:51 ` Rich Felker
2012-09-15 7:06 ` Isaac Dunham
2012-09-19 4:17 ` idunham [this message]
2012-09-15 10:54 ` Daniel Cegiełka
2012-09-19 0:19 ` idunham
2012-09-19 2:59 ` Rich Felker
2012-09-19 4:44 ` idunham
2012-09-19 4:39 ` Rich Felker
2012-11-25 17:58 ` Daniel Cegiełka
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=50767.132.241.246.168.1348028254.squirrel@lavabit.com \
--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).