X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Envelope-From: hsank AT nospam DOT chipforge DOT org
X-Envelope-To: <geda-user AT delorie DOT com>
Date: Sun, 28 Feb 2016 18:32:27 +0100
Message-ID: <20160228183227.Horde.g66UEijK5I0FnHyBsmI3bZU@webmail.in-berlin.de>
From: Hagen SANKOWSKI <hsank AT nospam DOT chipforge DOT org>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] hierarchical design - two symbols pointing to one
 schematic
References: <20160223152120 DOT Horde DOT _z0FeIbOqDDq7i7gKTXCeK4 AT webmail DOT in-berlin DOT de>
 <94CB9E71-127E-4690-9FFC-39722F79260B AT noqsi DOT com>
In-Reply-To: <94CB9E71-127E-4690-9FFC-39722F79260B@noqsi.com>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
Reply-To: geda-user AT delorie DOT com

Hello.

Thanks for your answer.
During this week I rectify my design, but still ending up - after a long,
long runtime something in hours on a VirtualBox with a lot of RAM and 4 CPUs -
with a gnetlist line which said: Killed.

Well, I tried to do my hierarchical design a little bit smaller and run just
a sup-page (which is still hierarchical) successfully thrue gnetlist.

I got a bunch of lines from gnetlist for my hierarchical design like this:
"Found a pin [Y300/Y2] on component [26] which does not have a label!"

Well, I found the Source Code via DuckDuckGo here (sorry for the bad  
reference!)
http://ljh4timm.home.xs4all.nl/gaf/dox_gnetlist/s__hierarchy_8c_source.html

IMHO the arguments for the fprint(stderr, ..) function should be swapped.

00206                 nl_current->component_uref,
00207                 pl_current->pin_number);

The first argument should be the pin number, the second one should be  
the component.
This lines, I guess, are coming from hidden VDD and GND nets inside my  
hierachichal
symbols.

Nevertheless I like to feed my whole gschem-Design now into PCB now.
So who is killing my gnetlist-process inside gsch2pcb? Any suggestion how to
find/avoid the reason for the gnetlist-death?

Regards,
Hagen Sankowski


-- 
"They who can give up essential liberty to obtain a little temporary
safety, deserve neither liberty nor safety." Benjamin Franklin (1775)