| View previous topic :: View next topic |
| Author |
Message |
knightk
n00b
Joined: 19 Apr 2006
Posts: 4
|
 Posted: Tue Jan 02, 2007 9:09 am Post subject: [SOLVED]emerge media-gfx/graphviz failed 2.8-r2 |
 |
|
Hi
The following is the error message while comipling media-gfx/graphviz 2.8-r2
| Code: | tclsh ./gv_doc_writer.tcl
make[3]: tclsh: Command not found
make[3]: *** [gv_perl.man] Error 127
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/var/tmp/portage/media-gfx/graphviz-2.8-r2/work/graphviz-2.8/tclpkg/gv'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/media-gfx/graphviz-2.8-r2/work/graphviz-2.8/tclpkg'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/media-gfx/graphviz-2.8-r2/work/graphviz-2.8'
make: *** [all] Error 2
!!! ERROR: media-gfx/graphviz-2.8-r2 failed.
Call stack:
ebuild.sh, line 1593: Called dyn_compile
ebuild.sh, line 951: Called src_compile
graphviz-2.8-r2.ebuild, line 78: Called die
!!! Compile Failed!
!!! If you need support, post the topmost build error, and the call stack if relevant.
|
is it the tclsh problem?? thx
Last edited by knightk on Thu Jan 18, 2007 1:05 am; edited 1 time in total |
|
| Back to top |
|
 |
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
|
| Back to top |
|
|
bugloaf
n00b
Joined: 17 Apr 2005
Posts: 19
|
| Posted: Sat Jan 06, 2007 7:50 pm Post subject: |
|
|
I had the same problem. I tried emerging with the new patch file mentioned in the bug report, but emerge failed digest verification, so I built it step-by-step with ebuild, and that seemed to work. But when I ran revdep-rebuild (what I was originally trying to do), it acted as if graphviz was still not emerged, and emerge failed in the same way. I was probably just making some newbie error, but rather than figure it out, I did this, which worked:
cd /usr/local/bin/
ln -s tclsh8.4 tclsh |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Sat Jan 06, 2007 9:21 pm Post subject: |
|
|
Yeah, any time you make a change to an ebuild, it will fail digest checks. All you need to do in that case is do "ebuild some.ebuild digest" and then emerge as normal.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Sat Jan 06, 2007 9:24 pm Post subject: |
|
|
Of course, if you don't keep the altered ebuild in some local overlay, it'll just get overwritten next time you sync.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
knightk
n00b
Joined: 19 Apr 2006
Posts: 4
|
| Posted: Thu Jan 18, 2007 1:02 am Post subject: |
|
|
I used the following command to update the digest
| Code: | | ebuild XXX.ebuild digest |
and it's work now. and thanks for didymos's reply |
|
| Back to top |
|
|
|
Portage & Programming
