I'm looking for some help in debugging this problem. Is there an intermediate step I can run to try and figure out if the problem is with the footprint or my schematic? What triggers the m4 library to kick in?
I see a long discussion thread about your particular problem, so I won't interfere there. However, to see what libraries are searched for footprints, you can run gsch2pcb in double verbose mode:
gsch2pcb -v -v project It will print out a detailed itinery of what it is doing while processing your board. THis is very useful for debug purposes like the one you have at hand. Stuart _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
