| 1 |
On 1/12/07, Roberto Martinez <mrrobinhood5@××××××.com> wrote: |
| 2 |
> On Sat, 13 Jan 2007 20:24:57 -0600, William Kenworthy <billk@×××××××××.au> |
| 3 |
> wrote: |
| 4 |
> |
| 5 |
> > On Thu, 2007-01-11 at 06:34 -0600, Roberto Martinez wrote: |
| 6 |
> > this sort of thing is often due to inconsistent/missing libraries |
| 7 |
> > |
| 8 |
> > 1. run revdep-rebuild |
| 9 |
> > 2. `ldd /usr/bin/firefox` and look for inconsistent/missing libraries |
| 10 |
> > 3. `strace /usr/bin/firefox` and see if where it dies gives a clue |
| 11 |
> > |
| 12 |
> > BillK |
| 13 |
> > |
| 14 |
> |
| 15 |
> revdep-rebuild came up with some libraries, but I think I might have an |
| 16 |
> issue with Portage as I've noticed that /etc/portage does not point |
| 17 |
> anywhere... Any ideas where its supposed to symlink ? #gentoo is not very |
| 18 |
> helpful ( at least the peers ) |
| 19 |
|
| 20 |
/etc/portage should be a directory, not a symlink. This is where you |
| 21 |
create package.keywords to enable ~ARCH builds, package.unmask to |
| 22 |
enable explicitly masked packages, package.use to set per-package USE |
| 23 |
flags, etc. |
| 24 |
|
| 25 |
The symlink you're thinking of is /etc/make.profile and it should |
| 26 |
point to something like |
| 27 |
/usr/portage/profiles/default-linux/x86/2006.1/desktop. |
| 28 |
|
| 29 |
> Calculating dependencies \ |
| 30 |
> emerge: there are no ebuilds to satisfy "=app-office/openoffice-bin-2.0.2". |
| 31 |
|
| 32 |
As a general rule, I always run revdep-rebuild with -p and ignore any |
| 33 |
gripes about openoffice-bin. Openoffice-bin comes with a lot of |
| 34 |
private libraries the supercede those in /usr/lib and reddep-rebuild |
| 35 |
doesn't know how to resolve those correctly. |
| 36 |
|
| 37 |
There's no ebuild for openoffice-bin-2.0.2 because that release is no |
| 38 |
longer in portage. Running emerge -u openoffice-bin will upgrade you |
| 39 |
to 2.1.0 which is currently the only open office binary release in |
| 40 |
portage. |
| 41 |
|
| 42 |
Running ldd on /usr/bin/firefox won't give any useful information |
| 43 |
since that is just a script that runs mozilla-launcher with the real |
| 44 |
binary. Instead, run ldd on /usr/lib/mozilla-firefor/firefox-bin which |
| 45 |
is the actual binary. You should not get any 'not found' messages. If |
| 46 |
anything is 'not found' then you need to move on to which package |
| 47 |
needs to be rebuilt. |
| 48 |
|
| 49 |
dcm |
| 50 |
|
| 51 |
dcm |
| 52 |
-- |
| 53 |
gentoo-user@g.o mailing list |
Archives