(adding list address back in-- my mistake to direct-reply last night) In https://github.com/omniti-labs/omnios-build/commit/fa210762018b66f066c5a0991c7633cea0d1b0eb I added some error handling and a comment on the TMPDIR setting. It's only "hard-coded" in the sense that it's set near the top of the script as opposed to somewhere like site.sh.
I've also updated http://omnios.omniti.com/wiki.php/BuildInstructions with your previous suggestions as well as a note about TMPDIR for the illumos build. Glad things are working for you! Eric On Sun, Feb 24, 2013 at 10:45 AM, Kent Watsen <k...@watsen.net> wrote: > > Right you are. My bad for not seeing that the "/code/omnios-151004: No > such file or directory" error happened first. The "how to build illumos" > doc uses "/code" in its examples, but it also says that the directory can be > anything, though it seems the OmniOS build hardcodes this value. A > directory-existence check followed by a nice error message would be nice - > especially given that the script requires being built by a user other than > "root" and yet creating a directory in '/' requires root-permissions. > Another nice add, to docs or scripts, would be to mention that detailed > output from the can be monitored in > /code/omnios\-151004/illumos\-omnios/log/nightly.log... > > Anyway, after creating /code and chmod-ing it to have good perms, the build > has been running error-free for ~10-15 minutes - yeah! Hopefully, with > 12-cores and 24GB, I'll have a result in a couple hours... > > Thanks for all the help so far! > > > > > On 2/24/13 12:31 AM, Eric Sproul wrote: > > After the deps are done the first error is the missing /code/... directory. > I would check to make sure you have write permission to that directory. It > also seems like we need better error handling around the dir creation. > > Eric > > _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
