unarchive 366064
forcemerge 366064 364095
quit
Thorsten Glaser wrote:
as written in #366064 I think that this is actually a gcc bug anyway.
These two seem related – should they be merged?
Sounds good to me. Thanks, Thorsten.
People stuck on old platforms: please see
Hi,
as written in #366064 I think that this is actually a gcc bug anyway.
These two seem related – should they be merged?
bye,
//mirabilos – t...@d.o
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out
tag 364095 + wontfix
thanks
proposing to close. we don't ship g++-3.3 anymore.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: binutils
Version: 2.16.1cvs20060117-1
Severity: important
For the same source in all three cases:
compiled w/ g++-4.0 and linked with current binutils - OK
compiled w/ g++-3.3 and linked with current bintuils - FAIL
compiled w/ g++-3.3 and linked with older binutils - OK
I get
4 matches
Mail list logo
