Re: Bizarre error running a program linked against a shared lib (help please!)
On 11 Oct 2000, Thomas Bushnell, BSG wrote:
> What will you do if there is no final binutils release between now and
> the release of woody?
There already is, so this is moot already. There was no doubt in my mind
that another release would happen (at least not from HJL...official GNU
releases tend to be few and far between), though. If this became an
issue, I would obviously step in to remedy the situation somehow.
Anyway, what's so bad about using a snapshot in some cases? I know it may
not look fantastic, but it's not like other packages don't already do this
(some don't even do normal version numbers anymore and, instead, just use
dates). You basically have a choice: buggy officially-released versions
or snapshots that fix the problems, but don't look as good on paper. In
either case, this last problem was a small hiccup (the m68k problem is a
larger priority than "hiccup", so don't get me wrong James) in the grand
scheme of the package. There is also no way to compare this to the RH7.0
situation with gcc either, since the releases of binutils that I have
packaged do not affect binary compatibility.
If it's everyone's choice, I'd be perfectly happy to just package up the
vanilla 2.10 release again and upload it. Sure, it would break several
archs, but if the majority wants it that way... Like I said, I'm doing
the best that *I* can right now given the situation. I don't mind being
questioned about it, but I don't like the attitude that I've been getting
in this thread over a temporary decision.
C
Reply to: