Open Bug 959933 Opened 6 years ago Updated 6 years ago

comm-central |make config.mk| does not states CLOBBER is necessary, and fails to configure.

Categories

(MailNews Core :: Build Config, defect)

x86
Linux
defect
Not set

Tracking

(Not tracked)

People

(Reporter: ishikawa, Unassigned)

References

Details

Hi, 

Yesterday, I  experienced that |make config.mk| failes to configure after an update
due to  |mozilla/js/src/js| being a file while the updated configure seems to
require this to be a directory.
Removal of MOZ_OBJ directory makes configure succeeded.

Here is a slightly edited moz.build news post exchange(s) regarding this.

(2014/01/14 15:34), Mike Hommey wrote:

[ to my earlier report of the configure failure, and the success
after the removal of $MOZ_OBJ/mozilla/js/src/js/src ]

> On Tue, Jan 14, 2014 at 03:04:23PM +0900, ishikawa wrote:
>> OSError: [Errno 20] Not a directory: '$MOZ_OBJ/mozilla/js/src/js/src'
>> configure: error: $MOZ_SRC/mozilla/js/src/configure failed for js/src
>> configure: error: $MOZ_SRC/mozilla/configure failed for mozilla
>> *** Fix above errors and then restart with               "make -f client.mk
>> build"
>> make[1]: *** [configure] Error 1
>> make[1]: Leaving directory `$MOZ_SRC'
>> make: *** [$MOZ_OBJ/config.status] Error 2
>>
>>
>> Before the removal of the $MOZ_OBJ directory,
>> $MOZ_OBJ/mozilla/jsr/src/js was a symlink to a large file,
>> and thus the error.
>> js -> ../src/shell/js (created on Dec 24)
>>
>> After the removal of the $MOZ_OBJ directory,
>> configure proceeded without a hitch.
>>
>> Just a note to share.
>> OS: Debian GNU/Linux 32-bit.
>> Updated to the latest comm-central source using "python client.py
>> checkout"
>
> This comes from bug 950298.
>
> So I take it that comm-central doesn't warn about necessary clobbers,
> or you ignored such a warning. If the former, please file a bug against
> mailnews core::build config.
>

Right, comm-central did not warn about necessary clobbers (at least
conspicuously.). I will check the log again [it is on a different PC],
to make sure that the necessity of clobber was not mentioned at all in
the log, and file a bug against core::build config.

And I confirmed that there is no display about the necessity of
clobber
after the update done by |python client.py checkout| on the said PC.

So I am filing this bug.

This is with comm-central tree.

TIA

PS: You can find the full exchange in moz.build newsgroup or mailing list.
E.g.: 
https://groups.google.com/forum/#!topic/mozilla.dev.builds/hBdZXto4gRs
See Also: → 950298
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.