From: Zappleberry <Zappleberry@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ngspice broken package
Date: Thu, 29 Jul 2021 22:35:47 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32251@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
New issue by Zappleberry on void-packages repository
https://github.com/void-linux/void-packages/issues/32251
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
* Void 5.12.19_1 x86_64 GenuineIntel notuptodate rrmFFF
* package:
* ngspice-33_1
### Expected behavior
ngspice package to provide the binaries and files to run spice decks.
### Actual behavior
No ngspice binary provided. Only binary provided is cmpp (Code Model PreProcessor for Xspice)
### Steps to reproduce the behavior
* install ngspice via ``xbps-install ngspice``
* Try to run spice deck.
### Additional Debug information
running ``find / 2>&1 | grep -i ngspice`` does not return anything helpful or any binaries.
Output of ``xbps-query -Rf ngspice``
```
/usr/bin/cmpp
/usr/lib/libngspice.so.0.0.0
/usr/lib/ngspice/analog.cm
/usr/lib/ngspice/digital.cm
/usr/lib/ngspice/spice2poly.cm
/usr/lib/ngspice/table.cm
/usr/lib/ngspice/xtradev.cm
/usr/lib/ngspice/xtraevt.cm
/usr/share/licenses/ngspice/COPYING
/usr/share/man/man1/cmpp.1
/usr/share/ngspice/dlmain.c
/usr/share/ngspice/scripts/ciderinit
/usr/share/ngspice/scripts/devaxis
/usr/share/ngspice/scripts/devload
/usr/share/ngspice/scripts/setplot
/usr/share/ngspice/scripts/spectrum
/usr/share/ngspice/scripts/spinit
/usr/lib/libngspice.so.0 -> /usr/lib/libngspice.so.0.0.0
```
Forcing a reinstall does not help.
Typically ngspice provides a binary in ``/usr/bin/``
next reply other threads:[~2021-07-29 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 20:35 Zappleberry [this message]
2021-08-04 23:27 ` mtboehlke
2021-08-05 0:07 ` ericonr
2021-08-09 16:53 ` mtboehlke
2021-08-09 17:20 ` ericonr
2021-08-30 13:31 ` [ISSUE] [CLOSED] " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32251@inbox.vuxu.org \
--to=zappleberry@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).