From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: compatability: heirloom-utils +.5, libarchive -1
Date: Tue, 3 Jan 2012 18:38:08 +0100 [thread overview]
Message-ID: <20120103173808.GH14961@port70.net> (raw)
In-Reply-To: <20120103060600.2190fc2b@newbook>
* Isaac Dunham <idunham@lavabit.com> [2012-01-03 06:06:00 -0800]:
> heirloom-utils: They are trying to support other nonstandard linux
> libcs, so they check for __GLIBC__ | __uclibc__ to determine whether
> dirent.h is present & sufficient; if dietlibc is detected, both
> unistd.h & dirent.h are used. The fallback is sys/dirent.h This should
> probably be __linux__ | _POSIX_SOURCE triggers dirent.h inclusion, then
> __diet__ triggers unistd.h; but if libc5/newlib are nonconformant here,
> then that logic would be inadequate.
i had to fix things in heirloom to be able to compile
it with pcc+musl
i did about the same hacks, but then i ran various tests
and some of the more obscure tools failed so i figured
heirloom is not that good quality, eg.:
nl -b a -v 0
(i would never use nl but it turns out the build
script mess of dash does ..for whatever reason)
> Also, could PATH_MAX be exported unconditionally, or is that
> nonstandard? Currently, defining any of the standard compatability
> macros enables it.
i think you cannot export it unconditionally
PATH_MAX is in limits.h which is also specified by iso c
so you cannot just export it if posix is not required
explicitly
> This is needed for the kernel to build without defining HOSTCFLAGS,
> though it really wants -D_GNU_SOURCE
>
> Isaac
next prev parent reply other threads:[~2012-01-03 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 14:06 Isaac Dunham
2012-01-03 17:38 ` Szabolcs Nagy [this message]
2012-01-05 2:05 ` Isaac Dunham
2012-01-06 8:41 ` Rich Felker
2012-01-06 14:08 ` Szabolcs Nagy
2012-01-07 1:38 ` Isaac Dunham
2012-01-03 17:49 ` Rich Felker
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=20120103173808.GH14961@port70.net \
--to=nsz@port70.net \
--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).