From owner-freebsd-stable@FreeBSD.ORG Sat May 18 03:04:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 859AE229 for ; Sat, 18 May 2013 03:04:28 +0000 (UTC) (envelope-from MGASS@csbsju.edu) Received: from smtp1.computing.csbsju.edu (smtp1.computing.csbsju.edu [152.65.184.22]) by mx1.freebsd.org (Postfix) with ESMTP id 3CFA5C11 for ; Sat, 18 May 2013 03:04:27 +0000 (UTC) X-AuditID: ac10425b-b7f726d000006b64-59-5196ec30c034 Received: from Mail-HTCAS1.ad.csbsju.edu (Unknown_Domain [172.16.66.43]) by smtp1.computing.csbsju.edu (Symantec Messaging Gateway) with SMTP id 15.6E.27492.03CE6915; Fri, 17 May 2013 21:49:20 -0500 (CDT) Received: from nx.csbsju.edu (172.16.66.48) by MAIL-HTCAS1.ad.csbsju.edu (172.16.66.43) with Microsoft SMTP Server id 14.3.123.3; Fri, 17 May 2013 21:49:20 -0500 Received: by nx.csbsju.edu (Postfix, from userid 1401) id 6D12818092E; Fri, 17 May 2013 21:49:20 -0500 (CDT) Date: Fri, 17 May 2013 21:49:20 -0500 From: Michael Gass To: Jeremy Chadwick Subject: Re: Command line not responding Message-ID: <20130518024920.GA32753@csbsju.edu> References: <20130517175653.GA15498@csbsju.edu> <20130517185513.GA88287@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20130517185513.GA88287@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA11TbUxTVxjm9OP2UnrY7aW0r0WMu9Fk2QYCmdEljripmfHHYn9sWXCZtPTS dpTS9bYOdMlEHF9Dx9AxZQxUcDDEmFXGx/hRLGwZkChki4KKw2zKKFQYG9uc2ce9vRQu/rl5 z/Oc93nej3NJOV2lNpIOl5f1uMxOhlAr2qmXnklJm601pd2o3ba1v4Te+uiLV7fLdp9aaFTs rqg4p9wry1Jvs7JOxwHWsykzW23vK2kj3J3rClsrQvLDqNlQiWJJoJ6DD8+WycRYDyN3LhGV SE3S1FUEF65NKsTDeQQ3w2dRJSL5gwvKij1CgoLaCOFAh1KICT4u++a4Qoh11AZomp5QCbGc Wg/Vnd9H4gTqKVi4Pxq5g6lN0PJ1c8SYprKgPRRQibgWBk//rBBzn4UzvQuEYCunkqDlX1KA Y6nNMN/2HyHEibzVycFOQpRJhtrq2/JqRNdJlOokSnUrSmeQvA0ZuXyvOz01pyDf7fM6XLbU HM7CveVLZa0+PxKHvK8bNfyWHkQUiRgNnt9Va6KV5gNcUX4Q5ZEyxogPTZw00QmWAmuR3czZ 93M+S76D4xwFLiYRX5nmr8cvcx6fk+UYHR4M8TBehi0+Zx6zDquvf2yiDRIhzu3IcRT4uP0+ jzOIgJTzqVOckGo1Fx1kPQWiYBAlkQrGgG8cnd1LUzazl81jWTfribLvkCSTjFFMTAyt97A2 tjDX4eTfkbRSwO8LJWmltFisAXuEHigpE6n3STzx/AkTbVytuLpkGRkbRDZSw6wR7WnObc7n HDaptQ6PRqYRpUTbBPyRgGqiaMQyGd8SRqRfUZHaDaG3jWvxXAm/jUThht3nWt2l0YADgigl YSNuRj3uPMKnPSEhBEPjetwr4GtWyUk9Q+gDGf8uQHwEWv7/fKy7BHwx0scSIzZH464ZHoxb AiO9rcW9kcqXJaQ2GecRiajJRAgMtyJorfhKBvfCQzJo/bJFDovX7yngxD9VSrjc162E5j8X ldAwdoyAQLiPgJ7WAQJqFqcIaDhSroLvemZUcHqynIRTTRdi4Zc712Lh+HCpGhpCj9Tw4O79 OJgd/zsObk4f00D9lXoMNT8OYbjU9JD/XC6Ph9ufPYgH/9W/4qGjo1EL3WNNWvCHO2gYn6zX hfhly1aW7TU/Pg4dVgobxFEquuwtAqqJokvLThOXvawinYjxMCqqmSnNHjh4q19v+n1j2ecv Hi2umhtN8m+OGUliVBdzf9jgTx0o3q7pqp1SpbyXWZhxaGfXyLw9q7MkO7wlbUKb+ab318Ey +o/c9tdadvawKbvoPVUvZ7xief1dbeiTgczk0kbrG+d2aB7u+0neOO9Kf2HH5PincLe9v2Ru z/BYxXjet4yCs5vTn5Z7OPP/Ntuyqp8FAAA= Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 May 2013 03:04:28 -0000 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 NO_PROFILE=true INSTALL_NODEBUG=true #WITHOUT_DILLO_IPV6=yes #WITH_DILLO_DLGUI=yes # added by use.perl 2013-05-17 11:04:30 PERL_VERSION=5.12.4 # File: src.conf WITHOUT_PROFILE=true WITHOUT_BLUETOOTH=true > The _ThreadRuneLocale thing has come up before, but on -CURRENT circa > early 2012. It happened to a user when trying to build kernel (really) > and that user was tinkering about in make.conf and src.conf heavily, > messing with Clang. I personally remove Clang from my systems entirely > for many reasons, by simply doing WITHOUT_CLANG=true in src.conf and > thus rely entirely on gcc. > > My recommendation, and this isn't going to make you happy: > I may do this if I cannot get things to work otherwise. I appreciate the advice. > Boot into single-user, mount your filesystems, and try commands there, > in hopes that they work. If they do: > > pkg_delete -a -f > cp -pR /usr/local /usr/local.old > rm -fr /usr/local/* > reboot > > Boot into multi-user, log in, and things should be fine. Next: > > rm -fr /var/db/ports/* > rm -fr /usr/ports/distfiles/* > find /usr/ports -type d -name "work" -exec rm -fr {} \; > > Now begin rebuilding your ports. If you prefer to use packages, go > right ahead, given that this was just announced a few days ago: > > http://lists.freebsd.org/pipermail/freebsd-announce/2013-May/001476.html > > But I tend to build everything from source, barring large-ish packages > (things like cmake, python27, perl) which I pkg_add -r. > > My attitude has always been when something catastrophic impacts a very > large number of commands (particularly a library with a missing symbol > that a very large number of programs link to), start fresh. It's > not worth scrambling around with leftover cruft in place that could > appear months later and make you say "I thought I fixed that!", where > you then have to follow up to a thread months old and admit "actually > there is more breakage..." > > Footnote: I am likely to get a large amount of backlash for proposing > the above, with claims that will equate it to fixing a minor cut by > amputating the entire limb. My response to such: that's nice. > > -- > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | -- Michael Gass mgass@csbsju.edu