Hi Anthony, Thank you very much for the spNet. I'm trying to compile your tool. The result is below:
$ make Making all in src make[1]: Entering directory `/home/alexb/Download/geda/spnet/spnet-0.9.1/src' gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"spnet\" -DVERSION=\"0.8\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 -DHAVE_STRFTIME=1 -DHAVE_STRCHR=1 -DHAVE_STRDUP=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -I. -I../include -Wall -g -O2 -MT io.o -MD -MP -MF .deps/io.Tpo -c -o io.o io.c In file included from io.c:15: ../include/str.h:14: error: conflicting types for ‘getline’ /usr/include/stdio.h:653: note: previous declaration of ‘getline’ was here make[1]: *** [io.o] Error 1 make[1]: Leaving directory `/home/alexb/Download/geda/spnet/spnet-0.9.1/src' make: *** [all-recursive] Error 1 Could you please give a hint what is wrong? I'm using F11, x86_64. Thanks, Alex. On 06/22/2009 03:33 PM, Anthony Shanks wrote: > What is your end goal here? Just to have hierarchical schematics or do > be able to produce a hierarchical netlist? IMHO hierarchical > schematics in gschem work perfectly fine, it's netlisting them that as > of right now is very hackery/broken which is why I started a new > netlister spNet. You can download the latest version here > http://spnet.code-fusion.net but be warned the documentation is very > shotty/inaccurate since I haven't officially released it yet. Refer to > my last post on this list for more details. > > On Sat, Jun 20, 2009 at 2:39 AM, Christoph Lechner<cl0...@l-mx.de> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> I'm just trying around with hierarchy. This is my first hierarchy >> design, and some questions remained open. I used the gTAG example as a >> starting point. >> >> What symbols do you use to 'declare' the pins in the subcircuit? I used >> the in-1.sym and out-1.sym, but using the refdes for the pin identifier >> looks like a hack to me. Is the used of these two symbols still state of >> the art or are there better ways to follow? >> So when renumbering the parts in the file, refdes_renum attaches a 1 >> suffix to all the refdes attributes of the in-1 and out-1 symbols on the >> sheet, which is just a mess. Some Perl warnings pop up on the command >> line, BTW. >> >> What can I do to fix it? >> >> I run the outdated gEDA suite 1.4.0, but I md5-verified that in-1.sym, >> out-1.sym and refdes_renum are the same in the newest 1.4.3 release. >> >> CU >> - - Christoph >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.7 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iD8DBQFKPK5TWo2QgtqY4K8RAti1AJ0RMEC0h2rsUvEKnXhVL+ebRrZtMgCggxiP >> OZN6KKI5RRXeZz9sXfMpPKM= >> =4tCj >> -----END PGP SIGNATURE----- >> >> >> _______________________________________________ >> geda-user mailing list >> geda-user@moria.seul.org >> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user >> >> > > > _______________________________________________ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user > > _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user