From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NOOhH-0006Ex-NN for garchives@archives.gentoo.org; Sat, 26 Dec 2009 04:56:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BEAC2E0662; Sat, 26 Dec 2009 04:55:35 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by pigeon.gentoo.org (Postfix) with ESMTP id 7734DE0662 for ; Sat, 26 Dec 2009 04:55:35 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NOOgb-0005Jb-9l for gentoo-amd64@lists.gentoo.org; Sat, 26 Dec 2009 05:55:29 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Dec 2009 05:55:29 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Dec 2009 05:55:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: [gentoo-user] chromium failed to start up Date: Sat, 26 Dec 2009 04:55:07 +0000 (UTC) Message-ID: References: <53e35fd50912252031q53a5bc77y7f7d8cb79af0df61@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Cc: gentoo-user@gentoo.org Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 333a1c22-07c6-479c-9061-79d9822f67c2 X-Archives-Hash: 3e0535b102ea55a9b95b89680e46fb08 Xi Shen posted on Sat, 26 Dec 2009 12:31:24 +0800 as excerpted: > my system is gentoo amd64, kde 4.3, and have recently updated. last tim= e > i emerged chromium and it works fine. but after updated the world, my > chromium cannot start up. it reports segment fault. Did you do a revdep-rebuild after the last update? Chances are, one of=20 chromium's dependencies was updated, changing its abi, and chromium (and=20 perhaps other packages) that depend on it need rebuilt to match the new=20 abi. It's revdep-rebuild that takes care of this, but if you don't run it=20 routinely, you'll likely have a BUNCH of stuff to rebuild. FWIW,=20 lafilefixer (with the --justfixit option) can reduce that bunch of stuff=20 by fixing *.la files that point to other *.la files, to point to the=20 libraries directly instead. Also, you may wish to read up on LDFLAGS=3D"-Wl,--as-needed" and consider= =20 using it too, as it helps kill indirect dependencies. (Say application X=20 uses library Y, which depends on library Z, but application X doesn't use= =20 any of library Z's functionality directly, so it shouldn't need to=20 directly depend on it, and shouldn't need to be rebuilt when only library= =20 Z changes. Only library Y would need rebuilt. The as-needed LDFLAGS=20 help this happen, thus reducing substantially the number of rebuilds=20 needed, but at a cost of occasionally causing a legit depend to be=20 missed. But flameeyes has been working on this as one of his projects,=20 so it doesn't happen very often with at least mainline packages any more,= =20 tho it might in obscure corner cases, the reason it's not yet the=20 default. So... consider it carefully as there's a major upside and=20 generally only obscure case downside, but do be aware of the issues if=20 you decide to use it.) Of course, the LDFLAGS as-needed won't help much until you've recompiled=20 a good part of your system at least once with it in place. But the=20 lafilefixer thing is just about perfect -- very little downside, it=20 doesn't take long to run compared to even a couple package rebuilds, and=20 it can be put to use immediately after you merge it! =3D:^) Together, these reduce the number of revdep-rebuilds SUBSTANTIALLY, and I= =20 run it after every update session. (Actually, my revdep-rebuild invoking= =20 script automatically runs lafilefixer --justfixit before it runs revdep- rebuild, just to be sure, so I only invoke that script after the update=20 and it takes care of both.) --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman