> The cerr not found thing is one of two problems. gcc3 is pickier
> about namespace issues than gcc2, so you need to say std::cerr or
> using namespace std;. However, the more common case is people
> thinking they can link c++ programs with 'cc' rather than 'c++'
>
> My C++ programs are large e
In message: <[EMAIL PROTECTED]>
Kenneth Culver <[EMAIL PROTECTED]> writes:
: I don't think kde3 compiles on the latest -CURRENT though, I've been
: trying to compile that for several days, and every time the linker says
: that things like cout and other standard c++ things aren't found
Kenneth Culver wrote:
> > In any case, the more verbose error reports are highly appreciated.
> > Could you please post the error messages you are getting (assuming your
> > next try of installworld with clean /usr/include does not help).
>
> Yeah, I can do that, the only reason I didn't do it t
> In any case, the more verbose error reports are highly appreciated.
> Could you please post the error messages you are getting (assuming your
> next try of installworld with clean /usr/include does not help).
Yeah, I can do that, the only reason I didn't do it this time is because
my home pc i
In any case, the more verbose error reports are highly appreciated.
Could you please post the error messages you are getting (assuming your
next try of installworld with clean /usr/include does not help).
On Thu, 11 Jul 2002 10:51:34 -0400 (EDT)
Kenneth Culver <[EMAIL PROTECTED]> wrote:
> > Thi
> This is FAQ. Have you deleted obsolete g++ include files? Do mv
> /usr/include /usr/include.old; mkdir /usr/inlcude before making
> buildworld.
I think I did that but I guess another try couldn't hurt...
Ken
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
On Thu, 11 Jul 2002 10:43:29 -0400 (EDT)
Kenneth Culver <[EMAIL PROTECTED]> wrote:
> I don't think kde3 compiles on the latest -CURRENT though, I've been
> trying to compile that for several days, and every time the linker
> says that things like cout and other standard c++ things aren't found.
I don't think kde3 compiles on the latest -CURRENT though, I've been
trying to compile that for several days, and every time the linker says
that things like cout and other standard c++ things aren't found.
Ken
On Wed, 10 Jul 2002, M. Warner Losh wrote:
> I'm not sure what the deal with X is, b
On (2002/07/11 11:01), Benjamin Close wrote:
>I'm using current from just after the KSE & libc_r fix. However it
> appears that XFree86-client c++ stuff is still broken. Is there a
> planned time when this will be fixed or am I missing something else?
> (XFree-libraries compiled and instal
I'm not sure what the deal with X is, but I have several non-X11 C++
programs that work just fine.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Jul 11, 2002 at 11:01:04AM +0930, Benjamin Close wrote:
> Hi All,
>I'm using current from just after the KSE & libc_r fix. However it
> appears that XFree86-client c++ stuff is still broken. Is there a
> planned time when this will be fixed or am I missing something else?
> (XFree-l
Hi All,
I'm using current from just after the KSE & libc_r fix. However it
appears that XFree86-client c++ stuff is still broken. Is there a
planned time when this will be fixed or am I missing something else?
(XFree-libraries compiled and installed without a hitch ).
rm -f glxinfo
LD_LIBR
12 matches
Mail list logo