Date: Sat, 3 Apr 1999 13:47:11 -0800 (PST) From: Alex Zepeda <garbanzo@hooked.net> To: Ollivier Robert <roberto@keltia.freenix.fr> Cc: Amancio Hasty <hasty@rah.star-gate.com>, Steve Price <sprice@hiwaay.net>, Andreas Klemm <andreas@klemm.gtn.com>, current@FreeBSD.ORG Subject: Re: X problems using egcs as compiler Message-ID: <Pine.BSF.4.05.9904031345360.802-100000@zippy.dyn.ml.org> In-Reply-To: <19990403225146.A99040@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 3 Apr 1999, Ollivier Robert wrote: > According to Amancio Hasty: > > Actually, it probably means that the program must be compiled with > > "-fexecptions". > > The problem is that egcs 1.1.2 has its own crt*.o files and use them in > place of the FreeBSD one. By moving the files elsewhere, it works. I don't > know the effect on exceptions though. > > I tumbled in this problem when compiling Perl 5.005_03 with egcs and moving > the files away "solved" the problem. > > I don't know what David plan to do with these crt*.o files. David ? Personally, I'd vote for using the new runtime objects, and forcing binary incompatibility. It's worth it IMO for the exception handling support if nothing else. However, if you're dead set against it, just back up your runtime objects, and edit the spec file (like the egcs port forced you to do at one time, and probably still does). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9904031345360.802-100000>