On 2013-03-06 18:18 +0100, Sven Joachim wrote: > Recapping the discussion from #646761, there are two problems leading to > differences across architectures: > > - curses.h includes the path to the build directory in a comment. The > culprit is this snippet from include/MKkey_defs.sh: > > ,---- > | cat <<EOF > | /* > | * These definitions were generated by $0 $DATA > | */ > | EOF > `---- > > Removing that snippet or using `basename $0` `basename $DATA` to get > rid of the directory name appears to be sufficient to make the headers > identical across Linux architectures. Thomas, would you be willing to > do either upstream?
Thomas has done it (using the "basename" solution) in the latest upstream patchlevel, so that obstacle is now gone. > - term.h differs across Linux and non-Linux architectures because the > former have termio.h and the latter don't. This appears to be > difficult to resolve, but since libc-dev is not currently > coinstallable for Linux and non-Linux architectures anyway, we could > ignore that fact for now. I'm going to do that, and anyone who really tries to install both (say) libncurses5-dev:kfreebsd-amd64 and libncurses5-dev:armhf (which currently requires both "--force-conflicts" and "--force-overwrite") can keep the pieces. > Or maybe have libncurses5-dev provide > libncurses-dev-linux on Linux and conflict with libncurses-dev-linux > on non-Linux architectures. Could be done later if there's need for it, but introducing an artificial virtual package just for that purpose is rather ugly. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
