From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Problems compiling gv
Date: Wed Aug 8 07:06:01 2001 [thread overview]
Message-ID: <01080816061303.00611@localhost> (raw)
In-Reply-To: <01080815313101.00611@localhost>
On Wednesday 08 August 2001 15:31, you wrote:
> On Wednesday 08 August 2001 17:32, you wrote:
> > Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300):
> > > OK, I've changed the gv ebuild, though it's rather a guess, but it's
> > > the only thing I can think of.
> > > If that doesn't help after rsync, could you try to extract and install
> > > the gv sources yourself, and see if that works?
> > > A final question: after the make error, emerge shuold say it failed to
> > > run something - what's that something? I want to know if it failed to
> > > compile or to install.
> >
> > How do I do a clean rsync?
>
> There's no such thing. Did I mention such a thing?
>
> > bash-2.04# emerge --clean rsync
> > !!! Error: --clean is an invalid option.
> >
> > bash-2.04# emerge rsync clean
> > !!! Error: clean does not exist or is an invalid command-line option.
> >
> > Ok, I did a simple emerge rsync. Same error when emerging gv:
> >
> > make[1]: *** No rule to make target `gv.man', needed by `gv._man'.
> > Stop. make[1]: Leaving directory
> > `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: *** [all]
> > Error 2
> >
> > !!! ERROR: the make command did not complete successfully.
> > !!! ("make")
> > !!! Since this is a critical task, ebuild will be stopped.
> >
> > !!! emerge aborting on /usr/portage/app-text/gv/gv-3.5.8.ebuild .
> >
> > I downloaded the sources with ebuild gv fetch, and got the same error
> > when compiling.
>
> I didn't really expect the problem to be in the ebuild anyway.
> This all seems very strange, and I can't do much because I can't recreate
> the problem. If you could send me the entire compile output it might help,
> and then again it might not. I just don't know what to say :-(
>
> One thing I *can* do is simply disable the makefile's operation on the
> manpage. The manpage is actually distibuted pre-compiled (not latex source
> or something), so all the makefile does is add a .1 extension and install
> it. So I'll do that now. Wait a couple of hours after this post, emerge
> rsync and try again.
I'm committing to cvs now and it *should* do it. Make sure emerge rsync
updates the gv ebuild, I don't know how much time it may take for the new
version to be available via rsync.
In case even this fails, I think there's a slightly newer version of gv and
I'm going to make an ebuild for that now.
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next prev parent reply other threads:[~2001-08-08 13:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 15:51 [gentoo-dev] just a little feedback Tibor Rudas
2001-08-07 16:01 ` [gentoo-dev] Problems compiling gv roberto
2001-08-08 1:14 ` Dan Armak
2001-08-08 5:53 ` [gentoo-dev] Toshiba laptop (was: Problems compiling gv) roberto
2001-08-08 6:27 ` Dan Armak
2001-08-08 1:45 ` [gentoo-dev] Problems compiling gv Dan Armak
2001-08-08 5:32 ` roberto
2001-08-08 6:31 ` Dan Armak
2001-08-08 7:06 ` Dan Armak [this message]
2001-08-08 7:09 ` Dan Armak
2001-08-08 13:49 ` Dan Armak
2001-08-08 10:50 ` Daniel Robbins
2001-08-08 11:25 ` Dan Armak
2001-08-08 11:50 ` Daniel Robbins
2001-08-17 12:23 ` [gentoo-dev] just a little feedback Aron Griffis
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=01080816061303.00611@localhost \
--to=danarmak@gentoo.org \
--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