On Fri, Feb 10, 2006 at 06:21:05PM -0200, Jose Carlos Medeiros wrote: > > Ah, I didn't notice that this bug was about memory usage in g++; I assumed > > it was a C++ standards bug, like so many others. Still, this seems to be > > the only package in all the archive that has such a problem, and the only > > package which build-depends on g++-3.3; could this bug be addressed by > > making changes to the VBA source as a workaround? > I tried to contact upstreamer, but nobody anwser me :( > last release of VBA is dated "2004-05-22". > Maybe this project was dead.
Well, if no one has updated it to work with g++4 yet, it seems effectively dead, yes. > > Er, I don't understand what you mean by an "ABI C++ problem". Certainly, > > having looked at the package now, I don't see how it *can* compile > > successfully via g++-3.3 with a build-dependency on libgtkmm-2.4-dev and > > libglademm-2.4-dev, since these packages are built for the g++-4.0 ABI now. > libgtkmm-2.4-dev and libglademm-2.4-dev, are just used to link with > GTK frontend. > The file that not compile is a doesnt use these libs. So you would build the GTK frontend with g++, even if using an older compiler for the main program? I guess that's ok, if there's an older compiler to use. > When I tried to compile VBA with g++3.4 or g++4.0 , g++ consume all my > memory and swap .. I dont receive error,, then its difficult > debug,, Maybe g++ group can do it. > Well, Popcon tell that 61 person use or installed VBA, I think > this is few person. and maybe we can put off VBA from Etch, as VBA is > the last package that need g++3.0. > What do you think ? I think that if VBA isn't fixed to use g++3.4 or g++4.0, this is the likely outcome. I don't think Matthias is going to want to maintain g++3.3 in etch for the benefit of a single package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
