Closed Bug 120420 Opened 23 years ago Closed 22 years ago

btek build failing in make depend sometimes

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: mcafee, Assigned: cls)

References

Details

 
btek has been failing occasionally with this message:

Removing old dependencies file, .deps/.all.pp
gmake[2]: Leaving directory
`/export/tinderbox/Linux_2.2.14-5.0smp_Depend/mozilla/xpfe/bootstrap'
gmake[2]: Entering directory
`/export/tinderbox/Linux_2.2.14-5.0smp_Depend/mozilla/xpfe/bootstrap'
gmake[2]: Nothing to be done for `export'.
gmake[2]: Leaving directory
`/export/tinderbox/Linux_2.2.14-5.0smp_Depend/mozilla/xpfe/bootstrap'
gmake[1]: Leaving directory `/export/tinderbox/Linux_2.2.14-5.0smp_Depend/mozilla'
gmake: *** [depend] Error 2

Comparing this to a build log on btek that works, the next line
should have been the make depend stuff.  Any ideas here?
Try removing the @ from the @echo's at line 1452 in config/rules.mk so that we
can see what it's trying to do.  I'm wondering if the redirection to stderr is
causing a problem.
@ change in place on btek, let's watch for the next time this fails.
@ change didn't give me any clues.

Poking around some more, I notice this is a -j3 build,
none of the other builds are -j builds ... and no other
builds are hitting this red bump in the road.  Should we
try turning this off?  Any other ideas?
did anyone change anything on btek?  Why is this red only showing up on btek?
You sure that other builds aren't -j (parallel)? I see multiple gmake's running 
concurrently on mecca, for example. (But, one thing that is different about 
btek is that it is dual cpu).
I'm not sure about how -j/gmake works.

Turning off -j3 on btek to see if that gets us out of the red.
Yeah, btek is running a -j3 build. We should probably just de-`j'-ify it. Want I
should do that?
already de-jay-ed..
removing -j3 seems to have cured btek, maybe this is a parallel build
problem?
*** Bug 120412 has been marked as a duplicate of this bug. ***
btek has since stopped failing to build, my guesses point
to the -j3 flag that was removed.
Looks like a make bug.  I wasn't able to reproduce this on my boxes; all of
which use make 3.79.1.  Myotonic was suffering from the same problem but it went
away after I ugpraded myotonic to 3.79.1.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
verified invalid.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.