Re: gEDA-user: How do you find bad M4 elements in gattrib?

[sdb@xxxxxxxxxx (Stuart Brorson)]

One suggestion:

Run gsch2pcb in "double verbose" mode:

gsch2pcb -v -v foo

It will provide a lot of spew as it processes each component, and
might let you figure out which one is faulty.

BTW:  Why use the M4 stuff if you know some of the components are
buggy?

Stuart


> 
> 
> When I run gsch2pcb I get the following error output.
> How do I track done which specific M4 element is bad?
> 
> stdin:3: m4: Bad expression in eval:  /2
> stdin:3: m4: Bad expression in eval:  /2
> stdin:3: m4: Bad expression in eval:  /2
> stdin:3: m4: Bad expression in eval:  /2
> stdin:3: m4: Bad expression in eval:  /2
> stdin:3: m4: Bad expression in eval:  /2
> stdin:3: m4: Bad expression in eval:  /2
> stdin:3: m4: Bad expression in eval:  /2 +20
> stdin:3: m4: Bad expression in eval:  /2 +20
> stdin:3: m4: Bad expression in eval:  /2 +20
> stdin:3: m4: Bad expression in eval:  /2 +20
> stdin:3: m4: Bad expression in eval:  /2 +20
> stdin:3: m4: Bad expression in eval:  /2 +20
> stdin:3: m4: Bad expression in eval:  /2 +20
> 
> ----------------------------------
> Done processing.  Work performed:
> 3 file elements and 24 m4 elements added to Neonlr812.pcb.
> 
> Next steps:
> 1.  Run pcb on your file Neonlr812.pcb.
>     You will find all your footprints in a bundle ready for you to place.
>