Re: Bizarre error running a program linked against a shared lib (help please!)
On 11 Oct 2000, Thomas Bushnell, BSG wrote:
> It's not just a binutils problem; it's a pervasive Debian problem.
>
> We seem to have a LOT of packages which use pre-release software.
In this case, the usage of the CVS binutils is a temporary solution to a
few problems that I encountered. I will almost definitely be reverting
back to using known releases again shortly (meaning within two weeks), but
I needed to get some of the patches that were going into the CVS rep into
the debian package and it wasn't feasible to backport them.
For anyone else who wants to complain about binutils being CVS: it won't
be forever...just another week or two max.
Didn't we already go down a similar road before with the "woody is
UNSTABLE...YMMV" type thread? Despite the fact that this is toolchain, I
think it still applies. I would always be willing to offer up a source
package for testing on other archs before uploading it, but nobody has
even asked me to do so yet. Also, if you want to see variances in the
stability of the toolchain, folks, perhaps you should walk a week on the
Alpha or MIPS side. I'm *constantly* dealing with toolchain issues on
Alpha and haven't even found time to mess with my MIPS yet because of it
(last I checked, MIPS wouldn't even bootstrap gcc because of a binutils
bug). Currently, gpc doesn't build on Alpha, but I'm perfectly happy to
forego an upload of gcc debs for Alpha for now to get the problems
fixed. In short, if that version doesn't work for you, have an older
version re-installed and let me know about the problems.
C
Reply to: