On 06/21/2011 10:06 PM, Andrew Poelstra wrote: On Tue, Jun 21, 2011 at 09:59:51PM -0400, Ethan Swint wrote:
416ccb60d759cd0e4e27d230a2af01bcc9f3ccdc (22 May 2011 committed by Krzysztof Kosciuszkiewicz: "hid/gtk: Cleanup conditional code because GTK 2.12 is required now") produces correct output. I'll run bisect on it and see if I can nail down which commit messes things up for me. Before you go to that much trouble, you might want to check and see if my pcb-printf commit was the cause. I see no problems, but my suspicion is that there is some overflow error somewhere. Are you running a 32-bit system? I'm running 64-bit. Here's the strange thing: compiling with git bisect, I always got a good gerber file output. I created a fresh, clean slate: git clone git://git.gpleda.org/pcb.git Then I ran: git bisect start git bisect good 416ccb60d759cd0e4e27d230a2af01bcc9f3ccdc git bisect bad 6808e757496cca0347d92d72851d0c34ae31b532 sh ./autogen.sh ./configure --disable-doc make ./src/pcb $FILENAME --export gerbers here in GUI-- git bisect good and repeat from autogen.sh. Every build came out good. BUT - when I ran git bisect reset then re-compiled and ran according to the above commands, I'm back to bad gerbers! I'll have to trouble-shoot more in the morning. Thanks for helping me track this down. -Ethan
_______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
