X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com From: "Branko (brankob AT s5tehnika DOT net) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] gnetlist/xorn: can't generate netlist on PCB backend To: geda-user AT delorie DOT com References: Message-ID: <920ada85-5b32-4b4b-70ee-524259b3ab09@s5tehnika.net> Date: Tue, 26 May 2020 09:43:46 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: sl Content-Transfer-Encoding: 8bit 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 BTW, I'm (Gentoo) using gcc-10.10.0 and guile-2.0.14, if that makes any difference. I tried recompiling with gcc-9.3.0 and guile-2.0.13, but for me it gave exact same results... On 26. 05. 20 06:19, Branko (brankob AT s5tehnika DOT net) [via geda-user AT delorie DOT com] wrote: > I usually run geda.git on my Gentoo. > > Recently I noticed trhat I can't for the life of me generate correct > netlist from schematics either manually or as schematic import from PCB. > > It doesn't work with xorn, gnetlist or gnetlist-legacy. > > The best I can do is get new "pcb" with just pure net specifications, > but without any elements and other fields, which makes file format invalid. > > All manual methods give me the same exact results. > It's not that the thing can't find any elements as it would otherwise > report an error( missing element). > > Here in the example I used a test with just two elements > Basic/resistor-1.sym > > I placed them on schematics, gave them both attribute footprint=0805, > named them as R1 and R2 and connected them in parallel with two nets. > > "gnetlist -v -g PCB  -o TEST4.pcb TEST4.sch" gives me output with this > content ( minus starred demacartion lines): > > /*************/ > unnamed_net2<-->R2-1 R1-1. > unnamed_net1<-->R2-2 R1-2.**** > /*************/ > > > Just those two lines. No some header and other fields, that one would > expect in pcb file... > > > > > >