public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lars Pechan <lars.pechan@paradise.net.nz>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] GCC-3.1/KDE 3.0.1
Date: Mon, 27 May 2002 11:39:27 +1200	[thread overview]
Message-ID: <200205271139.27014.lars.pechan@paradise.net.nz> (raw)

Hello,
I'd just thought I'd post a brief mentioning of a couple of problems I ran 
into trying to build KDE 3.0.1 on a gcc-3.1 system. 

Sorry for the lack of detail but I don't have access to the build system at 
the moment. If necessary, I can dig out the details and file these as bugs.

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). 


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 ;-).

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...

/Lasse



             reply	other threads:[~2002-05-26 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-26 23:39 Lars Pechan [this message]
2002-05-27  7:57 ` [gentoo-dev] GCC-3.1/KDE 3.0.1 Matthew Kennedy
2002-05-27 13:15   ` Lars Pechan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200205271139.27014.lars.pechan@paradise.net.nz \
    --to=lars.pechan@paradise.net.nz \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox