On 2012-09-29 14:57 +0200, Sven Joachim wrote:

> Control: severity -1 wishlist
>
> On 2012-09-29 14:27 +0200, Francois Gouget wrote:
>
>> The amd64 version conflicts with the i386 one which makes it
>> impossible to install both. As a result the
>> /usr/lib/i386-linux-gnu/libncurses.so symbolic link is missing so that
>> developping 32bit applications using this library is impossible on a
>> 64bit system.
>>
>> Furthermore this development package does not seem to be multiarch aware as 
>> there is no Multi-Arch field.
>>
>> My understanding is that as long as there are no
>> architecture-dependent headers there is no obstacle (i.e. no toolchain
>> issue) to tagging the development package as 'Multi-Arch: same'. The
>> symbolic link (and any static libraries) should be no issue as they
>> are already in the architecture-qualified folders.
>
> Unfortunately the headers _are_ currently architecture dependent, see
> #646761/#646977.

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?

- 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.  Or maybe have libncurses5-dev provide
  libncurses-dev-linux on Linux and conflict with libncurses-dev-linux
  on non-Linux architectures.

Other opinions?

Cheers,
       Sven


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to