On 2011-10-26 23:31 +0200, Thomas E. Dickey wrote:
> Quoting Sven Joachim <svenj...@gmx.de>:
>
>> Package: libncurses5-dev
>> Version: 5.9-2
>> Severity: normal
>> User: debian-d...@lists.debian.org
>> Usertags: multiarch
>>
>> When I marked the -dev packages as "Multi-Arch: same", I naively assumed
>> that the header files would be identical across architectures. A check
>> of libncurses5-dev:kfreebsd-i386 and libncurses5-dev:i386 reveals that
>> this is actually not the case:
>
> ...the generated-by stuff is a build-artifact that doesn't really matter,
> but the termio/termios stuff is hard to eliminate, since it in turn is
> eliminating some work by the applications that use the header files.
This is certainly true from your upstream perspective, however in Debian
the difference is currently non-functional since it's in an #else branch
that is not reached.
OTOH, it's not impossible that somebody ports Debian to an architecture
where this is not the case, although that seems unlikely to me, since
such a system would probably not be very POSIX compliant.
The safe action would be to move term.h to the multiarch include paths.
We then need compatibility symlinks in the lib{32,64}*-dev packages.
> The alternative would be to make the generated config.h (ncurses_cfg.h)
> included by each of the "public" header files, and to include that from
> another place (architecture-dependent).
That would be good since it frees us from the burden to check all the
header files.
In any case, since -dev packages with header files in multiarch include
directories are currently not allowed¹ to be "Multi-Arch:same" anyway,
my proposal would be to just remove the Multi-Arch field from the -dev
packages for now and only worry about a solution when libc6-dev becomes
"Multi-Arch:same".
Cheers,
Sven
¹
http://wiki.debian.org/Multiarch/Implementation#Issues_to_be_aware_of_when_converting
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
