-----Original Message----- From: Patrick Stinson [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 5:55 PM To: Patrick Stinson Subject: RE: Emacs errors, undefined references to osream::[*] after 4.4 -> 5.0 upgd
no, after a new install, I'm still getting the link errors for the undefined reference to ostream members. I've got no idea. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Patrick Stinson Sent: Sunday, December 01, 2002 3:31 PM To: Garrett Rooney Cc: freebsd-current Subject: RE: Emacs errors, undefined references to osream::[*] after 4.4 -> 5.0 upgd mmm, yeah, I might try removing all of the headers and doing another installworld -----Original Message----- From: Garrett Rooney [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 2:48 AM To: Patrick Stinson Cc: freebsd-current Subject: Re: Emacs errors, undefined references to osream::[*] after 4.4 -> 5.0 upgd On Sunday, December 1, 2002, at 09:40 AM, Patrick Stinson wrote: > After doing a complete upgrade (on a clean system, no less) from 4.4 > 5.0, > I;ve found that every now and again I get the same compiler error > regarding > undefined references to cerr, ostream operators, etc. I'm building the > gcc33 > port assuming it's a compat. issue with the libs, but has anyone else > seen > this? Also, all versions of emacs sparatically seg fault upon startup. > thanks. i don't know about the emacs thing, but the compiler errors sound like the kind of thing you see when you try to link a c++ program with gcc instead of g++. also, there are some issues with old header files from a 4.X system that's been updated to 5.0. the details should be in UPDATING. -garrett -- garrett rooney Remember, any design flaw you're [EMAIL PROTECTED] sufficiently snide about becomes http://electricjellyfish.net/ a feature. -- Dan Sugalski 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
