241802 - Make mail_chrome fails when using --enable-chrome-format with =flat or =symlink

Status: RESOLVED WORKSFORME

(Thunderbird :: Build Config, defect)

Description

[Karsten Düsterloh]

When using --enable-chrome-format with =flat or =symlink, the build process
tries to handle non-existent chrome jar files and fails. Thunderbird will run
from $objdir/dist/bin/ nonetheless, just not from $objdir/dist/Thunderbird/.

Last lines of build output:

make[4]: Entering directory
`/cygdrive/f/Projekte/Mozilla/Mozilla.org/tbdev/mail/config'
/usr/bin/make mail_chrome
make[5]: Entering directory
`/cygdrive/f/Projekte/Mozilla/Mozilla.org/tbdev/mail/config'
/cygdrive/f/Projekte/Mozilla/Mozilla.org/mozilla/build/cygwin-wrapper
g:/Programme/Mozilla/MozTools/bin/nsinstall -D ../../dist/thunderbird/tmpchrome/comm

unzip -o -d ../../dist/thunderbird/tmpchrome/comm ../../dist/bin/chrome/comm.jar
unzip:  cannot find ../../dist/bin/chrome/comm.jar,
../../dist/bin/chrome/comm.jar.zip or ../../dist/bin/chrome/comm.jar.ZIP.
make[5]: *** [mail_chrome] Error 9
make[5]: Leaving directory
`/cygdrive/f/Projekte/Mozilla/Mozilla.org/tbdev/mail/config'
make[4]: *** [libs] Error 2
make[4]: Leaving directory
`/cygdrive/f/Projekte/Mozilla/Mozilla.org/tbdev/mail/config'
make[3]: *** [libs] Error 2
make[3]: Leaving directory `/cygdrive/f/Projekte/Mozilla/Mozilla.org/tbdev/mail'
make[2]: *** [tier_99] Error 2
make[2]: Leaving directory `/cygdrive/f/Projekte/Mozilla/Mozilla.org/tbdev'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/cygdrive/f/Projekte/Mozilla/Mozilla.org/tbdev'
make: *** [build] Error 2

Setting platform/OS to all, because I'm seeing this for Win2k and =flat, and
Stefan Borggraefe mailed me an equivalent unixoid stack for =symlink.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 10/03 - 10/13)]

Build process finishes with --enable-chrome-format=flat without any error message. 

Comment 2

[Phil Ringnalda (:philor)]

That would have been from the repackaging step that went away in bug 289448 - orphan bits of code hung around through 1.8, but there's no longer a mail_chrome target anywhere in the trunk tree, so making it can't cause a problem any more :)