Wayne (For some reason your reply is not on the bug website) I don't know how to hack the build process to remove the offending issues. If I did I would have posted a fix rather than a bug. My plan is this: I wrote a c-utility RenumKiCadPCB which provides geographic renumbering of the PCB with full back-annotation to the schematics and netlist. It recurses the schematic hierarchy completely. Other applications I tried prior to writing Renum either flat out failed, only worked in simple cases (i.e. no hierarchy), or had other major issues. I wrote this for me, posted it online, and have received positive feedback from its users. Because it was written as a command line program its user base is probably much less than would otherwise have been the case. Since this function is absent from PCBNew (though present in every other PCB CAD tool I've used) I thought it would make a good addition to the code base. I am pretty sure somebody who knows their way around KiCad could easily incorporate it into PCBNew so I proposed it and got no takers. I was also informed the feature set was already frozen (even though the most recent nightly build changed the menu bar on me). So, I figure if I can build KiCad I can: 1) learn something about a complex project; 2) learn more about c++; 3) learn how a gui is coded; 4) if I am lucky, follow the instructions here http://docs.kicad-pcb.org/doxygen/md_Documentation_development_tool-framework.html#tutorial which will allow me to make a version of PCBNew with Renum built in. If I accomplish 3 then perhaps it would be easier to the devs to consider incorporate this missing function into PCBNew in the future. If nothing else I would have learned something. Regardless, there is no point in having documentation which provides step by step build instructions if those instructions fail. Brian -----Original Message----- From: