public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading tetex, not finding crti.o [solved]
Date: Sat, 2 Dec 2006 20:07:49 -0700	[thread overview]
Message-ID: <7573e9640612021907y43e9d9ebq26f15a58e6ae2cab@mail.gmail.com> (raw)
In-Reply-To: <20061203022919.GA28312@bart.bertram-scharpf.homelinux.com>

On 12/2/06, Bertram Scharpf <lists@bertram-scharpf.de> wrote:
>   - remove the 3.4.6 version by "emerge -C ..."
>     (almost nothing works now)
>   - create symlinks "/usr/i386-pc-linux-gnu/gcc-bin" -> "..i686..."
>     "/usr/i686-pc-linux-gnu/gcc-bin/3.4.6" -> "... /4.1.1"
>   - re-emerge gcc, glibc and several other packages
>
> This was probably too much effort, but I'm happy that it
> works at all.

Ok, it sounds like you just upgraded gcc versions.  So an "emerge -e
world" is called for if you want to be safe.

-Richard
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2006-12-03  3:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 18:36 [gentoo-user] Upgrading tetex, not finding crti.o Bertram Scharpf
     [not found] ` <456DD792.2000608@electronsweatshop.com>
2006-11-29 19:56   ` Bertram Scharpf
2006-11-29 20:13     ` Randy Barlow
2006-11-29 20:12 ` Richard Fish
2006-11-29 20:12   ` Richard Fish
2006-11-30 13:30   ` Bertram Scharpf
2006-12-01  2:54     ` Richard Fish
2006-12-01  4:13       ` Randy Barlow
2006-12-01  4:48         ` Richard Fish
2006-12-03  2:29       ` [gentoo-user] Upgrading tetex, not finding crti.o [solved] Bertram Scharpf
2006-12-03  3:07         ` Richard Fish [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7573e9640612021907y43e9d9ebq26f15a58e6ae2cab@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox