Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 3 Jan 2012 18:38:08 +0100
From: Szabolcs Nagy <>
Subject: Re: compatability: heirloom-utils +.5, libarchive -1

* Isaac Dunham <> [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

> This is needed for the kernel to build without defining HOSTCFLAGS,
> though it really wants -D_GNU_SOURCE
> Isaac

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.