X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net;
	s=badeba3b8450; t=1607297568;
	bh=EB0tNh0FXKhjTsISfHv5ubGkylOHNrLBzKcqXkkp8sI=;
	h=X-UI-Sender-Class:From:To:Subject:Date:In-Reply-To:References;
	b=eo+KMqeC+4OY+5CJNlseQVf5gZnAedxRUQiRK9boWR6/tq8gUhnpkQCdijER+ZYGw
	tsyhJUPZlfx8V3neeSQbzRJ+4rE/PTIb6CvrLELm/HZ+VoC5zpco37uTdWCa0EncKj
	eHVEVnU8QwSvhbsiIzWb5PaV2BtU7mOe9UK1DVlo=
X-UI-Sender-Class:	01bb95c1-4bf8-414a-932a-4f6e2808ef9c
MIME-Version:	1.0
Message-ID:	<trinity-20db38af-81cc-4404-af8a-fa6e497f67fb-1607248630018@3c-app-gmx-bs48>
From:	"Klaus Rudolph (lts-rudolph AT gmx DOT de) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
To:	geda-help AT delorie DOT com
Subject:	Re: [geda-help] using net names on multiple sub schematics used by
	single symbol
Date:	Sun, 6 Dec 2020 10:57:10 +0100
Importance:	normal
Sensitivity:	Normal
In-Reply-To:	<alpine.DEB.2.21.2012051633460.2665@nimbus>
References:	<c6376b29-a72c-6ae0-1b39-081ecb97ec1c AT gmx DOT de>
	<alpine DOT DEB DOT 2 DOT 21 DOT 2012051633460 DOT 2665 AT nimbus>
X-UI-Message-Type:	mail
X-Priority:	3
X-Provags-ID:	V03:K1:JTDJijYO3P7FM3UGOjuG1pIMICLhFUcpfhVQxtnTeJw165sPHVpPeqCw4zBSBU58/IlzM
	u3qG6+f07WsF7lih6nY1uXZHOTuJmULeovnF/t/T1UPeJfwC31Xvbb0pFp0UXim9IWqu5gWTcEBa
	xNuFam0gzboog8wZa8rLoKFDcfmbkezr/eO2pYnf6m9cZ3cdYxDPkLB9KX9fQo8/cs5DvZXER1gj
	jpd39SpkU5wFkNxdw/8nfo0rW+hH2eLWxTK7sKY4u3/S08g1Wmp9AZrcfKuilOmADgGo5DZcn3nh
	rE=
X-Spam-Flag:	NO
X-UI-Out-Filterresults:	notjunk:1;V03:K0:ftimncBu7Qw=:SI08X78ilINp7BZecPQhZe
	FDRcDwN8YqO3U9d/A7I3rxArfU0GWXEKVFQrFoiWstEk4BrEIr4SBObmpg4jxc7RJMhjI/hw8
	tno+ennvwDVrPN2aD0PHlj8i+TV/KFTC4078MSTIV2SzIMZ9I70kZe+IFCMaHXwU4SwraY1r7
	1bUc8Xj4SVrAvP6HBY89ryxWDNU6XtveM7L1vpBm+J6TfFVZkb2FKSgEWTHMDWav2DZBrSIB8
	DPRWBrUCHc6ADT4HzH8PMu7crAeG2Qdrj+Lig4BEkDYbgIqPtZOKXFNmXi1GnDTL8YVRJJeGo
	LZQFpXAboZWi00nBE5RThGcHrlr/XRrgA2iEQRHrVU6jD9uu4kEwCPkvxgzrLf30yMzAeaMGI
	rOa4TseEp05y8lVh1A/UpKGsx2vf7zLI6cYSM/GK0HVgzNb2mCkVDbzcfb70kUxUdPK5FOIe2
	aRbzoTbZ1OwLSlNfq6PjV/bkLbdhn3VP+E3SElWUaZksN4l19RQbpAVYInqhlngGn4YEt6GuK
	sX1V1of3onlT1brqQ7FlfDBITh9qSb6uWfBfWmNPbehFDzK1Yix/3QlPgWkH4BTI5FK8uZueV
	Q5JTMj8iilpa8=
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id 0B6NXcuw032643
Reply-To:	geda-help AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-help AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Am 05.12.20 um 16:34 schrieb Roland Lutz:
> On Fri, 4 Dec 2020, Klaus Rudolph (lts-rudolph AT gmx DOT de) [via geda-help AT delorie DOT com] wrote:
>> error: net name conflict across hierarchy: net name `A2/SIG1' is used by
>> net `SIG1' on page `A2/' and by net `SIG1' on page `A2/'
>> error: net name conflict across hierarchy: net name `A1/SIG1' is used by
>> net `SIG1' on page `A1/' and by net `SIG1' on page `A1/'
>
> This appears to be a bug in gnetlist.
The "same" problem occurs if you use a device with slots on different pages of a hierarchical schematic. If U101 slot 1 is on sub1.sch and U101 slot2 on sub2.sch for example, you get also these kind of error messages.

> I'm on it.

Great!

Klaus

- Raw text -