>From sfwnv-discuss-bounces at opensolaris.org Wed Feb 11 06:45:26 2009
>Marcel Telka wrote:
>> Hi Jan,
>>
>> On Wed, Feb 11, 2009 at 02:07:32PM +0100, Jan Hnatek wrote:
>>> Hi all,
>>>
>>> when I was running nightly on jade/zod, I was always getting failures
>>> with no packages created, but I didn't find any apparent reason for
>>
>> Why do you think the packages are not created? Any error message somewhere?
>Nightly should end by creating ./packages in $CODEMGR_WS/, right?
it should create packages where you told it to in the env file via
PKGARCHIVE, which likely is there yes.
>That doesn't happen. 'grep pkgmk nightly.log' is empty.
but you should look at the log more (or nightly, it's a script).
looking for '^====' can get you to each section though configure kinda
messes that up with its output, but at the end of your nightly.log you'll see:
==== Not creating non-DEBUG packages ====
>The only problem are the dmake messages (not warnings, warnings would get
>filtered).
>I think they cause $this_build_ok in nightly to be set to "n", which skips
>package creation...
>
>>
>>> this. Reports include:
>>> ==== Build errors (non-DEBUG) ====
>>>
>>> dmake: defaulting to parallel mode.
>>> dmake: defaulting to parallel mode.
note that since nightly lists this in an 'error' section that means
it thinks it is an error, therefore it doesn't build packages because
it thinks the build failed.
nightly apparently is not filtering that out since there is no
'warning' in the message so it thinks make failed.
>>>
>>> so I'd suppose the nightly script should have
>>> another egrep -v for this. I have:
>>> NIGHTLY_OPTIONS="-dmpW";
>>> in my sfw-developer.sh.
>>>
>>> Another question is why I am getting this while others probably don't?
>>
>> Whay are you getting what? The dmake warning message?
>Yes, the dmake messages.
>
>>
>> Are you running nightly with environment cleaned up?
>I do.
>[ nohup env - /ws/onnv-tools/onbld/bin/nightly ./sfw-developer.sh & ]
>
>hnhn
It looks like you might be building something with dmake that you
shouldn't. nightly actually disables that warning by telling dmake
to use parallel mode:
{mike_s:jade:44} grep MODE /opt/onbld/bin/nightly
DMAKE_MODE=parallel;
export DMAKE_MODE
which likely means some part of your build dropped that variable
then ran dmake. It looks like that may be in hunspell.
You seem to be wanting to use $(CCSMAKE) by putting that in the
environment there, but then you run $(MAKE) later
{mike_s:jade:57} grep MAKE Makefile.sfw
TARGET_ENV += MAKE="$(CCSMAKE)"
TARGET_ENV64 += MAKE="$(CCSMAKE)"
(cd $(VER); env - $(TARGET_ENV) $(MAKE) -e)
(cd $(VER64); env - $(TARGET_ENV64) $(MAKE) -e)
(cd $(VER); env - $(TARGET_ENV) $(MAKE) check)
you need to force the right make by actually running $(CCSMAKE)
otherwise $(MAKE) would be dmake from nightly, or whatever make
was run by hand.
Mike
