Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 157724 - media-gfx/graphviz-2.8-r2 uses wrong tclsh command
Summary: media-gfx/graphviz-2.8-r2 uses wrong tclsh command
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Graphics Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 165460
  Show dependency tree
 
Reported: 2006-12-10 05:16 UTC by Andrzej Zaborowski
Modified: 2007-02-19 18:04 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Replacement graphviz-2.8-notcl.patch (graphviz-2.8-notcl.patch,635 bytes, patch)
2006-12-10 05:20 UTC, Andrzej Zaborowski
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Andrzej Zaborowski 2006-12-10 05:16:17 UTC
Graphviz Makefile uses the command "tclsh" to generate the manuals even if ./configure detected that tclsh is under a different name (say "tclsh8.4", as installed by portage). "tclsh" is hardcoded in tclpkg/gv/Makefile.am and should be changed to $(TCLSH) to avoid build errors.
Comment 1 Andrzej Zaborowski 2006-12-10 05:20:41 UTC
Created attachment 103741 [details, diff]
Replacement graphviz-2.8-notcl.patch

The graphviz-2.8-notcl.patch file currently found in /usr/portage/media-gfx/graphviz/files/ can be safely replaced with this one. It contains the same changes but replaces "tclsh" with $(TCLSH) as a bonus.
Comment 2 Chris Bainbridge (RETIRED) gentoo-dev 2007-02-19 17:47:20 UTC
/usr/bin/tclsh should be a link to tclsh-8.4. It's owned by dev-lang/tcl. If that link doesn't exist it's a problem with your install or the tcl ebuild. Please reopen if I've misunderstood the problem.
Comment 3 Martin von Gagern 2007-02-19 18:04:56 UTC
Still configure detecting one executable and the build process using another one sounds like a bug to me, even if it should not affect Gentoo.
It might be a good idea to report this issue upstream.