Mike Sullivan wrote:
> Sriram Natarajan wrote:
>
>>> But you probably aren't running indiana on sparc. Maybe you're trying
>>> an incremental build, which is known to not be well tested and have
>>> such problems?
>>>
>> I did dmake clobber from usr/src before doing nightly -n . does that
>> not constitute a fresh build ?
>
> It depends - you also need to delete the proto area (though these mkdirs
> appear to be local to cmd/erlang) but if you didn't tell nightly -i then
> it would do that.
>
> Though the script appears to do the mkdir, copy things, then delete the
> whole directory, so a clobber probably wouldn't have helped as these
> aren't done as part of the clobber. It looks more like perhaps a build
> was interrupted at just the wrong time (but that's strange if it happens
> on both sparc and x86, unless you're using the same workspace). You
> should probably go look at the workspace and see why that directory is
> there. Maybe you don't own it or something strange like that. I can't
> tell because we aren't in the same nfsv4 domain apparently.
>
> Still a resync should fix you unless it's an owner/perm thing,
> which you can just fix manually.
btw in your logs from around the time that directory was created I do
see this:
/usr/bin/sh ./install-doc
cp: cannot create
/export/home/sn123202/php-gate/proto/root_i386/usr/share/doc/erlang/doc/
flip_closed.gif: Permission denied
cp: cannot create
/export/home/sn123202/php-gate/proto/root_i386/usr/share/doc/erlang/doc/
otp_top.css: Permission denied
cp: cannot create
/export/home/sn123202/php-gate/proto/root_i386/usr/share/doc/erlang/doc/
pics/min_head.gif: Permission denied
(and so on). That's in php-gate/log/log.2008-09-09.17:24. So that might
explain it if the script failed to copy and decided to exit before it
rm -rf'd the directory. But I don't know if that's a problem you've
addressed on your end (again, wrong permissions or something) or if you
have found a different bug in erlang.
Mike
