Thanks, that looks like that was the issue... On Sun, 9 Feb 2003, Lamont Granquist wrote: > On Sun, 9 Feb 2003, Craig Rodrigues wrote: > > On Sun, Feb 09, 2003 at 10:54:27AM -0800, Lamont Granquist wrote: > > > looks like nobody has fixed stlport since the last time gcc was > > > upgraded... > > > > I don't get these error messages on -current. > > > > > g++ -D_THREAD_SAFE -D_REENTRANT -fexceptions -I../stlport -Wall -W > > > -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -O > > > -pipe -march=athlon-mp -fPIC dll_main.cpp -c -o > > > ../lib/obj/GCC-FREEBSD/ReleaseD/dll_main.o > > > In file included from ../stlport/stl/_alloc.h:60, > > > from ../stlport/memory:28, > > > from dll_main.cpp:38: > > > ../stlport/new:36:49: ../g++/new: No such file or directory > > ^^^^^^^^^^^ > > > > This file should exist in /usr/include/g++/new. > > > > How did you install -current? > > its been updated frequently over the past 6 months - 1 year... i think > there's been at least two compiler changes since i started tracking > -current... > > > Did you read all the entries in /usr/src/UPDATING, especially > > the entry dated 20020831? > > mmm.... i don't think i did that because it was phrased as being > optional and only if you encountered problems... i'll try that, thanks > for pointing it out... > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > >
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message