[OmniOS-discuss] trouble compiling OmniOS

[Eric Sproul]

Have a look at the "mail_msg" file in the log directory for your
build, which should contain a concise summary of the build, looking
especially at the sections for various errors.  If those are non-empty
you can grep for those errors from nightly.log to drill down to root
causes.

Eric

On Sun, Feb 24, 2013 at 12:22 PM, Kent Watsen <kent at watsen.net> wrote:
>
> Hi Eric,
>
> I'm glad that I've been able to helped the project out   :)
>
> So, the build completed, but I'm unsure if it succeeded....
>
> In the window where I executed ./build.sh, I see:
>
> kent at compiler:/home/kent/omnios-build/build/illumos$ ./build.sh
> ===== Build started at Sun Feb 24 10:14:58 UTC 2013 =====
>
> Package name: illumos-gate
> Selected flavor: None (use -f to specify a flavor)
> Selected build arch: both
> Extra dependency: None (use -d to specify a version)
> The PKGSRVR (http://omnios.int.omniti.net:10002/) isn't available. All is
> doomed.
> An Error occured in the build. Do you wish to continue anyway? (y/n) y
> ===== User elected to continue after prompt. =====
> Verifying dependencies
> Preparing for build
> --- Creating temporary install dir
> Ensuring that Sun Studio is where Illumos thinks it is...
> --- fake SUNWspro link exists, good
> Creating build dir /code/omnios-151004
> Entering /code/omnios-151004
> Cloning OMNI Illumos Source...
> /code/omnios-151004/illumos-omnios /code/omnios-151004
> ~/omnios-build/build/illumos
>
> VERSION=\'omnios\-75e1472'
> Leaving /code/omnios-151004
> Entering /code/omnios-151004/illumos-omnios
>
> Changing illumos.sh variables to what we want them to be...
> Leaving /code/omnios-151004/illumos-omnios
> Entering /code/omnios-151004/illumos-omnios
>
> Getting Closed Source Bins...
> Leaving /code/omnios-151004/illumos-omnios
> Entering /code/omnios-151004/illumos-omnios
>
> Building extra tools needed for illumos pkgs...
> Leaving /code/omnios-151004/illumos-omnios
> Entering /code/omnios-151004/illumos-omnios
>
> Building illumos pkgs...
> Nightly failed
> An Error occured in the build. Do you wish to continue anyway? (y/n)  (how
> should I answer?)
>
> But /code/omnios-151004/illumos-omnios/log/nightly.log says:
>
> <SNIP/>
> sh /code/omnios-151004/illumos-omnios/usr/src/cmd/sgs/tools/chkmsg.sh -m
> ../common/elfedit.msg  ../common/elfedit.c ../common/sys.c ../common/util.c
> ../common/elfconst.c  ../common/elfedit_machelf.c ../common/util_machelf.c
> msg.c
>
> ==== Find core files ====
>
>
> ==== Check lists of files ====
>
> ==== Nightly distributed build completed: Sun Feb 24 10:46:25 UTC 2013 ====
>
> ==== Total build time ====
>
> real    0:27:18
>
>
> It says it completed - what gives?
>
> Also, comparing my compile-time to known Illumos build times, it seems
> comparable to the 2 x Xeon E5620  (total of 8 cores/16 threads @ 2.4GHz),
> whereas I have 2 x Opteron 2419 (total of 12 cores/12 threads @ 1.8GHz) -
> does it seem reasonable?   I suppose disk-access could also be a factor, but
> assume that it's not a significant bottleneck for either case...
>
> Thoughts?  - especially with regards to the "do you wish to continue"
> prompt?
>
> Thanks again,
> Kent
>
>
>
>
> On 2/24/13 11:12 AM, Eric Sproul wrote:
>
> (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
>
>
>