On Nov 29, 8:24pm, Christos Zoulas wrote:
} On Nov 29, 5:01pm, jnem...@cue.bc.ca (John Nemeth) wrote:
}
} | The reason I noticed it was due to a build failure. The system
} | I was building it on is:
} |
} | NetBSD msgate 7.0_BETA NetBSD 7.0_BETA (GENERIC.201408231540Z) amd64
} |
} | (Yes, it needs to be updated, but that's beside the point.) Granted,
} | this did point out an additional problem, which is: why was it
} | using the system headers and not the headers from the source tree
} | (a full cvs update was done immediately before the build)?
}
} Is that the tools build or the regular build? The tools build is supposed
} to work as consistently as possible across platforms. At least the ioctls
} are not NetBSD only (FreeBSD has them too).
Tools build. Full command line is:
./build.sh -j 10 -R /usr/local/NetBSD-current/amd64-releasedir -D
/usr/local/NetBSD-current/amd64-destdir -T
/usr/local/NetBSD-current/amd64-tooldir -O
/usr/local/NetBSD-current/amd64-objdir -X /usr/local/NetBSD-current/xsrc -x -u
-m amd64 tools sourcesets release iso-image-source |& tee ../buildlog
} | BTW, if you're going to take out getdisksize(), then there is
} | really no point in having #ifdef DIOCGSECTORSIZE, since it won't
} | work even if it does compile.
}
} It does work with parameters from the command line, as it always did.
True, but extremely sucky.
}-- End of excerpt from Christos Zoulas
