X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Mon, 13 Mar 2023 23:20:56 +0100 (CET) From: Roland Lutz To: "David W. Schultz (david DOT schultz AT earthlink DOT net) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] pcb vs gschem In-Reply-To: <339a45aa-0be9-0dc4-4d7e-5eca99133061@earthlink.net> Message-ID: References: <339a45aa-0be9-0dc4-4d7e-5eca99133061 AT earthlink DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Hi David, On Mon, 13 Mar 2023, David W. Schultz (david DOT schultz AT earthlink DOT net) [via geda-user AT delorie DOT com] wrote: > The error when I try to import a netlist is: > > ERROR: Could not find backend `pcbfwd' in load path. > > Is there some magic in the gschem build that I should be doing? > > It looks like pcb is installed to /usr/share/pcb while "which gschem" yields > "/usr/local/bin/gschem". There is a /usr/share/gEDA directory but there is > justs one file in it. PCB brings its own netlister backend called `pcbfwd' and installs it to PREFIX/share/gEDA/scheme/gnet-pcbfwd.scm Since your PCB and gEDA/gaf installation prefixes differ, gnetlist doesn't find this backend. While fixing the backend load path should in theory work, the easiest way to fix this would probably be to copy /usr/share/gEDA/scheme/gnet-pcbfwd.scm to /usr/local/share/gEDA/scheme/gnet-pcbfwd.scm Roland