> Stuck at this point
>
> -bash-3.2# nightly opensolaris.sh
> /tmp/onnv-3.4_nightly.lock: No such file or directory
> i386 build of onnv-3.4 apparently already started by on as .
>
Are you trying to build when logged in as user root?
I'm building as a non-root user; I'm buildig under
the ${STAFFER} user.
I suspect it is failing in the /opt/onbld/bin/nightly script in the
create_lock() shell function:
create_lock() {
lockf=$1
lockvar=$2
ldir=`dirname $lockf`
[ -d $ldir ] || newdir $ldir || exit 1
eval $lockvar=$lockf
while ! staffer ln -s $hostname.$STAFFER.$$ $lockf 2> /dev/null; do
....
The "staffer" command is an internal shell function in the nightly
script that tries to run a command under the userid ${STAFFER};
I suspect STAFFER isn't set to a valid user name for your system.
In case this doesn't help fixing the problem, try to remove the "2> /dev/null"
stderr output redirect in the above "staffer ln -s ..." command in
the /opt/onbld/bin/nightly script, so that you can see the error
message that is reported here...
> I was waiting for about 20 minutes at this
> point...Should I wait longer ?
> Nothing under log folders.
I suspect it is looping in the create_lock function,
thinking that another compilation is already running
because the lock symbolic link cannot be created.
Btw. the full nightly compilation can take some time,
my 2GHz dual core cpu systems need 2 - 2.5 hours
for the full compilation. And that's with disabled
"shadow compilation" (export CW_NO_SHADOW=1)
so that each file is compiled with SunC only, and
not twice with SunC and gcc.
--
This message posted from opensolaris.org
_______________________________________________
xen-discuss mailing list
[email protected]
