X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=AWfmaUlEjKR5OFbKRUMlCvnJoXKugCdo/k6gT8FTVeM=; b=XO3DBwKPEWQTO3UIxdc8b7uAFktZocrg3J5nFLKeyP37E3DRoZIDm8QT67Wyt+7yw0 cKW49SDYAL/MouqWOHYMkUPTllV4NPDYsXxyAjzriDZ2TNLSxD2qDawmFoGzz+NpvUBz IW8ef3OZppB6coA7rDg4ftlDGIIvPsu89fkCeB9/Gl/uac7ksfl/bBPtwKT+Glw9UTl0 XkISHho9uu/mJdHCqBSXPboY2E/2OZY3HJmwmMVc8snX/V3N7TQ/gPB3tbGFpwMmqnNq 7F1kW03jzMFRVE3dRP58yIesGddhs/RGbL+NO77i2R4FTHzs+N2Wrn2PjmriYh1luc65 TxvA== MIME-Version: 1.0 X-Received: by 10.52.114.230 with SMTP id jj6mr10700730vdb.66.1433548353926; Fri, 05 Jun 2015 16:52:33 -0700 (PDT) Date: Fri, 5 Jun 2015 15:52:33 -0800 Message-ID: Subject: [geda-user] how to avoid 'Cant find PINLABEL pin1 called for in netlist'? From: "Britton Kerin (britton DOT kerin AT gmail DOT com)" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Reply-To: geda-user AT delorie DOT com For hierarchical design, I use an io symbol containing a pin with pinnumber and pinseq attributes for each point where a connection to the subcircuit is intended. In the subcircuit schematic, that symbol then gets pinlabel and refdes attributes set to the desired PINLABEL, and I create a subcircuit symbol containing pins with a matching PINLABEL attribute (and appropriate source attribute) for use in the main circuit. It all works but PCB ends up complaining: 'Cant find PINLABEL pin1 called for in netlist' This makes me sad because I don't ever get to see PCB congratulate me on my completed layout :/ What is the simple way to avoid this problem? Thanks, Britton