From owner-freebsd-current Sat Nov 16 13:15:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19562 for current-outgoing; Sat, 16 Nov 1996 13:15:29 -0800 (PST) Received: from murrow.prognet.com (prognet.com [205.219.198.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA19557; Sat, 16 Nov 1996 13:15:16 -0800 (PST) Received: from peterh.dev.prognet.com (two89.dev.prognet.com) by murrow.prognet.com with SMTP id AA26299 (5.67b/IDA-1.5); Sat, 16 Nov 1996 13:14:44 -0800 Message-Id: <3.0b36.32.19961116131427.010daf60@prognet.com> X-Sender: peterh@prognet.com X-Mailer: Windows Eudora Pro Version 3.0b36 (32) Date: Sat, 16 Nov 1996 13:14:29 -0800 To: "Eric J. Chet" , Ernie Elu From: Peter Haight Subject: Re: guavac, libstdc++ Cc: ports@FreeBSD.org, current@FreeBSD.org, dob@nasvr1.cb.lucent.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 10:01 PM 11/13/96 -0500, Eric J. Chet wrote: >On Thu, 14 Nov 1996, Ernie Elu wrote: > >> Has anyone managed to get the guavac java compiler from >> http://http.cs.berkeley.edu/~engberg/guavac to compile under FreeBSD >> current? >> >> Everytime I try it gets a link error from the g++ file tree.h saying that >> the varialbe rb_NIL is unknown. I can't find that variable in any of the g++ >> libraries so it might be a bug that it's missing. >> >> - Ernie. >> > >Hello > There are three *.cc files in >/usr/src/contrib/libg++/libstdc++/stl > >random.cc >tree.cc >tempbuf.cc > >That are not being built under FreeBSD. Should these three files >be added to the build process for libstdc++? They really need >to be included into a library. I encountered this problem too. It is not that those files are not being compiled at all, but that they are not compiled into the shared library. I moved 'libstdc++.so.2.0' out of my /usr/lib and any STL stuff that uses red black trees now works. This only happened after I upgraded to the 2.2-961014-SNAP. I don't know whether this is still a problem.