public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Voegele <voegelas@users.sourceforge.net>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] Re: tetex ebuild problem
Date: Sat Oct 13 01:39:01 2001	[thread overview]
Message-ID: <m2itdk6lex.fsf@columbus.localdomain> (raw)
In-Reply-To: <20011012161923.L2138@red.ces.clemson.edu>

Grant Goodyear writes:

> When emerging tetex-1.0.7-r2.ebuild on my new
> Athlon rc6 box I get the following error: [...]
> Has anybody else encountered this error?

I emerged tetex-1.0.7-r2.ebuild yesterday with the following options:

CHOST="i586-pc-linux-gnu"
CFLAGS="-mcpu=i586 -march=i586 -O3 -pipe"
CXXFLAGS="-mcpu=i586 -march=i586 -O3 -pipe"
USE="berkdb cups esd ipv6 mitshm mmx nas nls ogg opengl oss pam perl \
     readline ssl tcpd ungif vorbis X"

I don't use the flag "libwww". My portage tree was last updated on 8th
October.

I can't build xfig though. I get the message:

/bin/sh: Doc/xfig._man: No such file or directory

I think that this bug is related to XFree 4.1.



      reply	other threads:[~2001-10-13  7:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 14:19 [gentoo-dev] tetex ebuild problem Grant Goodyear
2001-10-13  1:39 ` Andreas Voegele [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=m2itdk6lex.fsf@columbus.localdomain \
    --to=voegelas@users.sourceforge.net \
    --cc=gentoo-dev@cvs.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