From: karl@aspodata.se
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sci-electronics/ngspice-27-r1 missing tcl
Date: Tue, 22 Dec 2020 19:55:02 +0100 (CET) [thread overview]
Message-ID: <20201222185502.BB3088329F89@turkos.aspodata.se> (raw)
In-Reply-To: <24877.1608653945@owl.pooh.corner>
DaveF:
> >Neil Bothwick:
> >> On Wed, 16 Dec 2020 18:30:47 +0100 (CET), karl@aspodata.se wrote:
> >> > What can I do to make ./configure below use the suggested option ?
> >> > sci-electronics/ngspice-27-r1's build log contains:
...
> >> > Should you add --with-tcl=/usr/lib64 to ./configure
..
> >> Try EXTRA_ECONF="--with-tcl=/usr/lib64" emerge -1a ngspice
> >https://wiki.gentoo.org/wiki/Project:AMD64/Multilib_layout
> > gentoo now uses /usr/lib64. Tcl installs the program in /usr/lib64:
> ># grep /usr/lib64/tclConfig.sh /var/db/pkg/dev-lang/tcl-8.6.8/CONTENTS
> >obj /usr/lib64/tclConfig.sh 854158d4603ecea0e98975dac780e04f 1581626600
> > so if ngspice doesn't find tclConfig.sh, shouldn't that be considered
> > a bug ?
>
> Don't know. Is there a reason why ngspice-27-r1 in particular is required?
No, it is just that that version was pulled in by emerge @world.
> I added
> =sci-visualization/xgraph-12.1-r4 xgraph
> to package.license
> sci-electronics/ngspice ~amd64
> sci-visualization/xgraph ~amd64
> to package.accept_keywords
> and
> sci-electronics/ngspice tcl
> to package.use
>
> And
> emerge -1 ngspice
> built without any complaints.
...
Did that, and for some reason the problem went away ???
Tanks for the help.
Regards,
/Karl Hammar
prev parent reply other threads:[~2020-12-22 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 17:30 [gentoo-user] sci-electronics/ngspice-27-r1 missing tcl karl
2020-12-16 18:31 ` Neil Bothwick
2020-12-17 18:04 ` karl
2020-12-20 0:41 ` karl
2020-12-20 4:08 ` Michael Orlitzky
2020-12-21 19:42 ` karl
2020-12-21 22:01 ` Jack
2020-12-22 16:19 ` David M. Fellows
2020-12-22 18:55 ` karl [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=20201222185502.BB3088329F89@turkos.aspodata.se \
--to=karl@aspodata.se \
--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