Hello Ingo, Ingo Weinhold wrote: > > - <http://dev.haiku-os.org/ticket/3136> This makes many tests which use > > 'long double' fail. This is critical, because gnulib now assumes working > > 'long double' on all platforms. > > For sake BeOS binary compatibility Haiku does by default still use gcc > 2.95.3. I don't know whether "long double" support was generally broken in > this gcc version or if only the BeOS and Haiku ports are affected.
The test program works fine when compiled with gcc 2.95.3 for Linux/x86. So, only BeOS and Haiku are affected. > > - <http://dev.haiku-os.org/ticket/3143> st_ctime appears to be > > unimplemented. > > AFAIK our primary file system BFS (known as BeFS in the GNU/Linux world) > doesn't store st_ctime on disk and therefore treats it synonymous to > st_mtime. That can't be fixed until we break on-disk compatibilty. How much > of a problem is this with respect to gnulib? It is not a big problem. Causes one test failure only. But some programs (e.g. editors which watch the status of files being currently edited) will not work optimally if ctimes are nonexistent. > > What is the way to > > 1. distinguish a connected from an unconnected socket? > > I'm not a networking expert, but I suppose getpeername() should succeed > when connected (at least for protocols that require binding for > connections) and fail if unconnected. Thanks, I'll try this. > > - Mention the recommended configuration options for Haiku in the > > INSTALL file. Can you tell what is the difference (in intent and use) > > of /boot/home/config and /boot/common? I note the default PATH has > > /boot/home/config/bin before /boot/common/bin. > > The user's home > directory is /boot/home, software only for herself is installed in prefix > /boot/home/config. Software for all users is installed in prefix > /boot/common. ATM, having only a single user, it doesn't really make a > difference in which of these two locations something is installed, but as > soon as Haiku has grown full multi-user support only /boot/common will work > as desired, so we've already discouraged /boot/home/config. I.e. all > software packages should be configured with "--prefix=/boot/common". Thanks for explaining. Indeed, /boot/common appears to be the equivalent of /usr/local on other Unix systems - which is the default $prefix for configure. Bruno
