both cube and seg seems to do some funky stuff with flex/bison, if I'm
not entirely mistaken. Cube, for example, uses a rule that builds
"cubeparse.o" from "cubescan.c". (which in turnis built from flex/bison
files).

Is there any reason why we don't build a file called "cubescan.o" from
"cubescan.c" and thus simplify the rules a bit?

//Magnus


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Reply via email to