This is kinda a followup from the thread on misc@ "Error building -ntpd on -current" which i started. Before posting this same hypothesis on misc@ i would like to hear something from you as well cause... I''ve got two different machines which i keep current and on one of them i built flashboot from a current snapshot. On that machine then i was unable to complete a successful build of OpenBSD with the error described on misc@ Instead on the other machine i was able to build current and the only difference (without taking hw but that''s not failing) between the two is that on the first one i built flashboot. So here come my question: Could be that building flashboot (with build.sh and mk-mini.conf) and setting BSDOBJDIR on a different directory other then /usr/obj could cause the problem? I''ve to admit i got not many clues. Thanks for your time. -- Massimo
Massimo Lusetti wrote:> Instead on the other machine i was able to build current and the only > difference (without taking hw but that''s not failing) between the two is > that on the first one i built flashboot. > > So here come my question: Could be that building flashboot (with > build.sh and mk-mini.conf) and setting BSDOBJDIR on a different > directory other then /usr/obj could cause the problem?If you have accidentally done a "make build" or a "make includes" with DESTDIR set but using the mk-mini.conf, then you could have clobbered something. If you are really paranoid, then you could try running the build under systrace with a very simple policy that permits everything except for writes under /usr/src -d
On Sun, 2006-07-09 at 18:57 +1000, Damien Miller wrote:> If you have accidentally done a "make build" or a "make includes" with > DESTDIR set but using the mk-mini.conf, then you could have clobbered > something.Thanks for clarifying it. I was thinking of something similar but was not too sure of what could exactly have been the problem, since i scheduled the built with a custom made scripts that''s probably exact.> If you are really paranoid, then you could try running the build under > systrace with a very simple policy that permits everything except for > writes under /usr/srcI''ll try it really soon. Thanks! -- Massimo.run();