In my case, I don't really want to debug gcc, but I want to make an
upstream bug report as precise as possible. So including a stack
trace would be a bonus. It should help narrowing the nature of the
bug, so that the appriopriate upstream author can start
investigating, thus saving them time.
Thanks for your prompt answer.
yes, space & bandwidth. the packages get 100%-200% bigger. and if you
really want to debug gcc, you need the source and you build it
yourself. gcc-snapshot is intended to check for bugs in development
versions of gcc, such that package maintainers can have it installe
Hi,
This error prevented me from installing gcj-3.0
Package: libgcj2-dev 1:3.0-1
The error can be seen at
http://packages.debian.org/unstable/devel/libgcj2-dev.html
DEPENDS on :
libgcc0 (>= 1:3.0-0pre010613) (NOT AVAILABLE)
No Description Available
Thanks for your work anyway!
Daniel
3 matches
Mail list logo
