From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Modular X
Date: Sat, 01 Apr 2006 22:29:15 +0200 [thread overview]
Message-ID: <442EE29B.9060907@mid.email-server.info> (raw)
In-Reply-To: <1143922368.11529.15.camel@keelie.localdomain>
Jim wrote:
> Would this be a problem with the EBuild or with the app? I am try to
> install tightvnc and get the following error.
>
>>>> Source unpacked.
>>>> Compiling source
> in /var/tmp/portage/tightvnc-1.2.9-r1/work/vnc_unixsrc ...
> /usr/portage/net-misc/tightvnc/tightvnc-1.2.9-r1.ebuild: line 41: xmkmf:
> command not found
>
> !!! ERROR: net-misc/tightvnc-1.2.9-r1 failed.
> Call stack:
> ebuild.sh, line 1526: Called dyn_compile
> ebuild.sh, line 923: Called src_compile
> tightvnc-1.2.9-r1.ebuild, line 41: Called die
>
> I take it xmkmf is no longer used in xorg 7.0?
alexander@blatt /var/db/pkg $ epm -qf `which xmkmf `
imake-1.0.1-r1
Please file a bug against tightvnc, as it's missing
a dependency.
BTW: Why use tightvnc at all? Realvnc 4 is as fast in
my experience and there's still somebody workign on it -
seeing that the last update to tightvnc is dated
July 2005, I doubt that anybody maintains it anymore.
Alexander Skwar
--
Just don't make the '9' format pack/unpack numbers... :-)
-- Larry Wall in <199710091434.HAA00838@wall.org>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-01 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 20:12 [gentoo-user] Modular X Jim
2006-04-01 20:29 ` Alexander Skwar [this message]
2006-04-01 20:58 ` Rick van Hattem
2006-04-01 21:47 ` Jim
2006-04-02 9:06 ` W.Kenworthy
2006-04-02 14:26 ` Rick van Hattem
2006-04-02 16:19 ` Toby 'qubit' Cubitt
2006-04-03 6:23 ` Alexander Skwar
2006-04-03 15:35 ` Toby 'qubit' Cubitt
2006-04-03 21:02 ` Alexander Skwar
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=442EE29B.9060907@mid.email-server.info \
--to=listen@alexander.skwar.name \
--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