Re: [gentoo-dev] GCC-3.1/KDE 3.0.1

[Lars Pechan]

Hello,
I now have only one gcc (as built by gcc-3.1r4) and no outstanding patches. I 
did an emerge unmerge on gcc-3.1r1 since that was reported as installed by 
qpkg. Didn't make any major changes however...

Interesting about portage and 2.95.3/3.0.4 as I've built a decent chunk of my 
new system using 3.1 only and haven't had any sandbox-related problems 
(yet??).

The htdig ebuild is indeed crapping out because of gcc-3.1 complaining about 
using a deprecated header (iostream.h, fstream.h etc instead of iostream, 
fstream). The following is a workaround that will build it with gcc-3.1:

CPPFLAGS=-Wno-deprecated emerge htdig

There's still lots of noise during compilation about the same issue.  Adding 
the same flag to CFLAGS and CXXFLAGS will get rid of it.

On the fam-oss problem  I've sent a mail to the maintainer at SGI. For anyone 
interested this is the error message:

c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include 
-DCONFIG_ETC_CONFIG_PATH=\"/etc/fam.conf\"    -Wno-deprecated -c 
Scheduler.c++
Scheduler.c++:37: uninitialized const member `Scheduler::IOTypeInfo::iotype'
Scheduler.c++:38: uninitialized const member `Scheduler::IOTypeInfo::iotype'
make[2]: *** [Scheduler.o] Error 1
make[2]: Leaving directory `/var/tmp/portage/fam-oss-2.6.7/work/fam-2.6.7/fam'

I shall kick off the next stage now and see what nastities we may have bumped 
into in the morning...

/Lasse

On Mon, 27 May 2002 19:57, Matthew Kennedy wrote:
> Howdy,
>
> On Sun, 2002-05-26 at 18:39, Lars Pechan wrote:
> > 1) The fam-oss library doesn't build. This is the File Alteration Monitor
> > from SGI used by both KDE and Gnome I believe. The problem relates to a
> > const member of a class not getting initialized (IIRC Scheduler.c++ lines
> > 37 and 37).
>
> Please submit a bug report on that one... it might also be related to
>
> the following though:
> > 2) HTDig (required by kdevelop) doesn't build. It craps out during
> > configure complaining about
> > missing libstdc++. I had a quick look and it looks for <fstream.h> to
> > trigger whether there's a c++ library in place or not. That file does
> > exist but possibly in a directory that isn't on the default search path.
> > C++ standards call for the header to be called <fstream> and there is
> > indeed an <fstream> in the /usr/include/g++-3.1/libstdc++ or thereabouts
> > ;-).
>
> Check that you don't have more than one gcc version installed. This
> seems to come up a lot, and the reason usually turns out to be that more
> than one gcc is installed. If it still craps out, please report in
> bugzilla.
>
> > I'm a bit surprised I haven't seen anyone else mentioning this? There
> > seems to be lots of people building gcc-3.1-systems...
>
> Please check out package.mask, there are several gcc3.1 patches in there
> which need to be tested before being unmasked.
>
> Also, use a portage compiled with gcc 3.0.4 or 2.95.3... that works
> around a known problem with sandbox/gcc3.1.
>
> Also, if you get unresolved symbol issues with fam-oss, try a "make
> mrproper" on your /sur/src/linux after backing up your .config. Then run
> "make dep clean" after restoring your .config.
>
> Keep the gcc3.1 issues coming :)
>
> Matt