From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: musl vs util-linux: main issues
Date: Sun, 17 Mar 2013 21:58:46 -0700 [thread overview]
Message-ID: <20130317215846.920449a9.idunham@lavabit.com> (raw)
Hello,
I've been poking at util-linux 2.22.2 in hopes of getting it to compile (one of the Puppy developers was trying to get it for rev, mount, umount, and losetup; I'm not sure why he didn't use busybox).
The following are the issues I ran across so far, building with _GNU_SOURCE defined:
-include/cpuset.h (replacement for some macros that glibc includes via sched.h):
Assumes that <sched.h> defines __cpumask, __NCPUBITS, __CPUELT, __CPUMASK, cpu_set_t.
glibc defines these in <bits/sched.h>, so they might vary by arch.
Several other places, including agetty:
Need macros from <sys/ttydefaults.h>.
cfdisk: __sighandler_t for sighandler_t (easy to fix)
Thank you,
Isaac Dunham <idunham@lavabit.com>
reply other threads:[~2013-03-18 4:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130317215846.920449a9.idunham@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).