Date: Tue, 21 May 2013 09:24:34 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Michael Gass <mgass@csbsju.edu> Cc: Jeremy Chadwick <jdc@koitsu.org>, freebsd-stable@freebsd.org Subject: Re: Command line not responding Message-ID: <alpine.BSF.2.00.1305210922110.79332@wonkity.com> In-Reply-To: <20130518024920.GA32753@csbsju.edu> References: <20130517175653.GA15498@csbsju.edu> <20130517185513.GA88287@icarus.home.lan> <20130518024920.GA32753@csbsju.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 May 2013, Michael Gass wrote: > On Fri, May 17, 2013 at 11:55:13AM -0700, Jeremy Chadwick wrote: >> On Fri, May 17, 2013 at 12:56:53PM -0500, Michael Gass wrote: >>> Running 9.0-Stable on an i386. >>> >>> Whenever I type a command at the prompt I get >>> the output >>> >>> /usr/local/lib/libintl.so.9: Undefined symbol "_ThreadRuneLocale" >>> >>> and nothing else - the command will not run. Just the >>> above output. Commands like "ls" and "exit" work, but not much >>> else. This happends whether I am logged in a user or as root. >>> Cannot even halt the system from the command line. >>> >>> Started to happen after trying to update the freetype2 port. >>> Got an error msg while updating libXft-2.1.14. From that point >>> on I cannot use the command line. >>> >>> I have no idea what to try. Any suggestions. >> > > >> First provide the contents of /etc/make.conf and /etc/src.conf. >> > > Thanks for getting back to me. Here are the contents of the two > files. I rebuilt the kernel last fall and have updated ports > fairly regularly since. Things have worked fine until today when > I tried to update ports. > > # File: make.conf > # The ? in the below is for buildworld > CPUTYPE?=pentium2 > # Uncomment the below for general builds. > CFLAGS= -O -pipe > # Uncomment the below for kernel builds. > # COPTFLAGS= -O -pipe It is almost always a mistake to set CFLAGS in make.conf. Not only does it not improve performance, it frequently causes problems. It will sometimes decrease performance for ports that can safely use custom CFLAGS themselves, because it prevents them from using those custom flags. In other words, custom CFLAGS provide few or zero improvements, and have a significant risk of causing problems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1305210922110.79332>