reassign 644708 binutils-gold
found 644708 2.21.52.20110606-2
close 644708 2.21.53.20110910-1
thanks
On 2011-10-09 15:03 +0200, Laurent Dard wrote:
> Le 09/10/2011 10:35, Matthias Klose a écrit :
>> reassign 644708 tcsh
>> thanks
>>
>> $ cat foo.c
>> char tgetent ();
>> int
>> main ()
>> {
>> return tgetent ();
>> ;
>> return 0;
>> }
>>
>> the failing test works for me. the linker line is however missing the
>> libraries.
>
> Thanks.
>
> Here is a test to isolate the bug:
> cat > foo.c <<eof &&
> char tgetent ();
> int main ()
> {
> return tgetent ();
> ;
> return 0;
> }
> eof
> su
> for DISTRIB in testing unstable ; do
> echo "### $DISTRIB ###"
> apt-get -y --force-yes install binutils/$DISTRIB \
> binutils-multiarch/$DISTRIB binutils-dev/$DISTRIB \
> binutils-gold/$DISTRIB binutils-doc/$DISTRIB > /dev/null
> for x in termcap {,n}curses ; do gcc foo.c -l$x ; done
> done
>
> The result is:
> ### testing ###
> /usr/bin/ld: error: cannot find libncurses.so.5
> collect2: ld returned 1 exit status
> /usr/bin/ld: error: cannot find libncurses.so.5
> collect2: ld returned 1 exit status
> /usr/bin/ld: error: cannot find libncurses.so.5
> collect2: ld returned 1 exit status
> ### unstable ###
> Reading changelogs...
>
> Obviously, it's not related to tcsh at all...
> To which package does this bug belong?
To binutils-gold, and it seems to have been fixed in this version:
,----
| binutils (2.21.53.20110910-1) unstable; urgency=low
| [...]
| * For native builds, add the multiarch directories to the default
| search path.
|
| -- Matthias Klose <[email protected]> Sat, 10 Sep 2011 13:06:01 +0200
`----
> libncurses5?
We could add a versioned Breaks against binutils-gold, but that would
not really help wheezy users, and for upgrades from squeeze this issue
will eventually be irrelevant. Or we could temporarily add
/usr/lib/$(DEB_HOST_MULTIARCH)/libncurses{,w}.so.5 symlinks to help the
gold linker find the libraries. Matthias, any idea when binutils will
migrate to testing?
Cheers,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
