On Thu, 1 Aug 2013 08:50-0700, David Wolfskill wrote:
(Sorry I overlooked that you were clearing /usr/obj at the start of your
build.)
Since Oliver is running on amd64, it wouldn't hurt if he, and the rest
of us, also nukes /usr/obj/lib32. After I started using amd64, I
always run rm -Rf
This is strange:
Accidentally I started from two different terminals on the same box
rm -rf /usr/obj/usr make -j2 buildworld
While the first proceess had a headstart, the second killed
the /usr/obj entries and so both jobs died immediately.
But after that, I tried simply again
make buildworld
On Thu, 1 Aug 2013 17:26:18 +0200
O. Hartmann ohart...@zedat.fu-berlin.de wrote:
This is strange:
Accidentally I started from two different terminals on the same box
rm -rf /usr/obj/usr make -j2 buildworld
While the first proceess had a headstart, the second killed
the /usr/obj entries
On Thu, Aug 01, 2013 at 05:36:53PM +0200, O. Hartmann wrote:
...
Solving the problem is via deleting
/usr/src/tools/build/libegacy.a
This is strange, I wouldn't expect a on demand created file
in /usr/src. What happens on boxes were /usr/src is a NFS mount and
read only for building
On 8/1/13 11:36 PM, O. Hartmann wrote:
On Thu, 1 Aug 2013 17:26:18 +0200
O. Hartmann ohart...@zedat.fu-berlin.de wrote:
This is strange:
Accidentally I started from two different terminals on the same box
rm -rf /usr/obj/usr make -j2 buildworld
While the first proceess had a headstart, the
