gEDA-user: autorouter trouble, or maybe compiler trouble, or maybe layer trouble...

[John Griessen <john@xxxxxxxxxxxxxx>]

I wanted to use the autorouter and could not get either way to run today.

when I compile with ./configure --prefix=/opt/geda --enable-toporouter=no
or the default ./configure --prefix=/opt/geda I get the same symptom of running a
while, with 90% memory use, then seg fault.  I did some compiles with gcc-4.4,
then set it to use gcc-4.1, and about the same.  Then I thought maybe my
lack of setup was causing problems and simplified things a lot
and turned off some layers as suggested and still the same.

I have a layer group of three for top and three for bottom. They are different colors
for hand routing meaning, like:  top-sig1, top-sig2, top-PWR-GND.

Does having separate layers that are really just the same layer kill the autorouter?
Mine are grouped as
1,2,3,c: 4,5,6,s:7:8:9:10:11:12

As long as I don't start the autorouter from the GTK menu connects--> autoroute all rats,
everything is fine.

If I select 4 rats and run atoroute selected rats, I get similar results.  Seemed to go a little
longer before Segmentation fault

John
--
Ecosensory   Austin TX


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user