[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [grave] libstdc++2.8 needs versioned dependencies



Adam P. Harris wrote:
> 
> Well, if you look at /usr/doc/jade/buildinfo.Debian, you shall see that
> I am well aware of this package and it's what I used to build jade
> after backing off from egcs:

On the Alpha, since egcs is our default compiler (don't ask), we too are
having problems with jade.  I'm tempted to compile it with the latest
egcs snapshot that I packaged up (I do it every week for Alphas) to see
if anything is remedied on our end at least.

> By the way, g++272 is very excellent and nice and it was bascially smooth
> as silk to install it and use it.  Works great!

Hmmm...well, I feel Ray's pain here since I'm one of the people
pressuring him to oust g++272 due to it being outdated and not multiple
architecture friendly.  On the Alphas at least, g++272 will not build
very easily and, even if we get it to, it doesn't support alot of the
features of libstdc++ from egcs.  I suppose we could split "the tree",
so to speak, when it comes to other architectures, but I think Ray is
just trying for some unity (and therefore personal sanity on his part)
amongst the architecture ports for something so integral as a
fundamental library and compiler.

> What I would like to know, actually, is whether I should be notifying
> the jade upstream maintainer (James Clark) that his C++ is not up to
> snuff, and here's why, or alternatively, submit a bug against egcs.
> I think someone would have to look through the jade source to really
> determine that however.

I may take a look at jade's code also to see if I spot anything obvious,
but RL may take a front seat here time-wise.  There's been alot of talk
on the egcs list about multiple inheritance problems lately, so that may
be the cause of this whole thing (disclaimer: I haven't actually looked
at the code involved yet).  

If you can, let me know what it's doing and I'll see if I get comparable
results on the Alpha.

Chris


--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: