Bug#480437: ncurses5-config reports incorrect information
On 2012-12-07 01:30 +0100, Colin Watson wrote:
On Mon, Jun 27, 2011 at 05:01:15PM +0200, Sven Joachim wrote:
I see two possible solutions:
1) Mark ncurses-bin Multi-Arch: foreign.
2) Move ncurses{w,5}-config to their respective -dev packages and drop
the ncurses-bin dependency.
1) has the disadvantage that the output of ncurses5-config --libs and
ncurses5-config --libdir is incorrect for foreign arches. The
downside of 2) is that it becomes impossible to make the -dev packages
Multi-Arch: Same (AIUI this is currently not allowed anyway, but may be
in the future[2]).
It certainly is allowed (and becoming commonplace) now. And I see that
you've since marked ncurses-bin Multi-Arch: foreign, which seems
reasonable.
Right, since I initially also marked the -dev packages Multi-Arch: same,
which turned out to be premature since the headers unfortunately are
arch-dependent.
We could just declare that anyone who wants correct ncurses
configuration in a multiarch universe needs to use pkg-config instead.
This already has broadly sensible cross-building support, whereas
attempting that with ncurses{5,w5}-config would require work more or
less equivalent to just switching to pkg-config.
Actually, the only thing in ncurses{w,}5-config which differs across
architectures is the --libdir option, and I don't think this causes
real problems in cross-building. The --libs option I also mentioned
is already taken care of by the 03-debian-ncursesconfig-omit-L.diff
patch.
I don't know whether you know this, but there definitely exist packages
that require both the build and host architecture versions of
libncurses{5,w5}-dev in order to cross-build successfully, due to
performing both native and cross passes when cross-building. texinfo is
such a case which I ran across recently.
Thanks, I was not aware of that.
Therefore, I don't think a solution that prevents the -dev packages
becoming Multi-Arch: same is correct.
Making the -dev packages coinstallable is definitely a goal for Jessie,
please followup on #689131 if you're interested. The current bug should
just be closed, I think.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#480437: ncurses5-config reports incorrect information
On Mon, Jun 27, 2011 at 05:01:15PM +0200, Sven Joachim wrote:
I see two possible solutions:
1) Mark ncurses-bin Multi-Arch: foreign.
2) Move ncurses{w,5}-config to their respective -dev packages and drop
the ncurses-bin dependency.
1) has the disadvantage that the output of ncurses5-config --libs and
ncurses5-config --libdir is incorrect for foreign arches. The
downside of 2) is that it becomes impossible to make the -dev packages
Multi-Arch: Same (AIUI this is currently not allowed anyway, but may be
in the future[2]).
It certainly is allowed (and becoming commonplace) now. And I see that
you've since marked ncurses-bin Multi-Arch: foreign, which seems
reasonable.
We could just declare that anyone who wants correct ncurses
configuration in a multiarch universe needs to use pkg-config instead.
This already has broadly sensible cross-building support, whereas
attempting that with ncurses{5,w5}-config would require work more or
less equivalent to just switching to pkg-config.
I don't know whether you know this, but there definitely exist packages
that require both the build and host architecture versions of
libncurses{5,w5}-dev in order to cross-build successfully, due to
performing both native and cross passes when cross-building. texinfo is
such a case which I ran across recently. Therefore, I don't think a
solution that prevents the -dev packages becoming Multi-Arch: same is
correct.
Cheers,
--
Colin Watson [cjwat...@ubuntu.com]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#480437: ncurses5-config reports incorrect information
On 2009-08-29 09:53 +0200, Sven Joachim wrote:
On 2008-05-10 02:40 +0200, John Darrington wrote:
ncurses5-config should be shipped by libncurses5-dev and not
ncurses5-bin and it should give the correct information.
I agree that ncurses5-config should be in libncurses5-dev. As long as
it is in ncurses-bin, at least the output of ncurses5-config --version
is not guaranteed to be correct.
This has been worked around in 5.7+20100313-2 by adding a strict
versioned dependency of libncurses5-dev to ncurses-bin. In the light of
Multi-Arch approaching[1,2], this might need to be revised: if an admin
wants to install a foreign-arch libncurses5-dev, he has to replace the
native ncurses-bin as well which is not probably not very desirable.
I see two possible solutions:
1) Mark ncurses-bin Multi-Arch: foreign.
2) Move ncurses{w,5}-config to their respective -dev packages and drop
the ncurses-bin dependency.
1) has the disadvantage that the output of ncurses5-config --libs and
ncurses5-config --libdir is incorrect for foreign arches. The
downside of 2) is that it becomes impossible to make the -dev packages
Multi-Arch: Same (AIUI this is currently not allowed anyway, but may be
in the future[2]).
Any other ideas?
1.
http://anonscm.debian.org/gitweb/?p=collab-maint/ncurses.git;a=commit;h=f9e74cbe811e06c0914c13dab8ce361d25114d6d
2. http://lists.debian.org/debian-devel-announce/2011/06/msg2.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#480437: ncurses5-config reports incorrect information
severity 480437 normal retitle 480437 ncurses5-config should be in libncurses5-dev thanks On 2008-05-10 02:40 +0200, John Darrington wrote: Package: ncurses-bin / libncurses5-dev Version: 5.6+20080308-1 Severity: important ncurses-bin ships the ncurses5-config binary. Running ncurses5-bin --cflags reports -I/usr/include/ncurses But this is wrong. The package does not provide /usr/include/ncurses. Even if libncurses5-dev is installed, then it puts the header files in /usr/include NOT /usr/include/ncurses Consequently any build configurations which rely on ncurses5-config will break. As Thomas Dickey had already pointed out, this has been fixed in the meantime, ncurses5-config --cflags only prints an empty line currently. ncurses5-config should be shipped by libncurses5-dev and not ncurses5-bin and it should give the correct information. I agree that ncurses5-config should be in libncurses5-dev. As long as it is in ncurses-bin, at least the output of ncurses5-config --version is not guaranteed to be correct. Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#480437: ncurses5-config reports incorrect information
Package: ncurses-bin / libncurses5-dev Version: 5.6+20080308-1 Severity: important ncurses-bin ships the ncurses5-config binary. Running ncurses5-bin --cflags reports -I/usr/include/ncurses But this is wrong. The package does not provide /usr/include/ncurses. Even if libncurses5-dev is installed, then it puts the header files in /usr/include NOT /usr/include/ncurses Consequently any build configurations which rely on ncurses5-config will break. ncurses5-config should be shipped by libncurses5-dev and not ncurses5-bin and it should give the correct information. J' -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://pgp.mit.edu or any PGP keyserver for public key. signature.asc Description: Digital signature
