public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bertram Scharpf <lists@bertram-scharpf.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading tetex, not finding crti.o
Date: Wed, 29 Nov 2006 20:56:19 +0100	[thread overview]
Message-ID: <20061129195619.GA13112@bart.bertram-scharpf.homelinux.com> (raw)
In-Reply-To: <456DD792.2000608@electronsweatshop.com>

Hi Randy,

Am Mittwoch, 29. Nov 2006, 13:55:14 -0500 schrieb Randy Barlow:
> fix_libtool_files.sh 3.4.5
> 
> That should do the trick :)

Sorry, it seems it doesn't. What kind of tool is that?

Bertram


> Bertram Scharpf wrote:
> >I am trying to upgrade teTex using `emerge -pvuD tetex'. The
> >compiling process aborts with an error message saying that
> >this file could not be found:
> >
> >  /usr/lib/gcc/i386-pc-linux-gnu/3.4.5/../../../crti.o
> >
> > [...] present is
> >
> >  /usr/lib/gcc/i386-pc-linux-gnu/3.4.6/../../../crti.o
> >                                     ^
> >
> >How can I tell the ebuild that my compiler is version 3.4.6?

-- 
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-11-29 20:01 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 [this message]
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

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=20061129195619.GA13112@bart.bertram-scharpf.homelinux.com \
    --to=lists@bertram-scharpf.de \
    --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