Issue 105503 - config_office: build fails on missing msvcp71.dll
Summary: config_office: build fails on missing msvcp71.dll
Status: CONFIRMED
Alias: None
Product: Build Tools
Classification: Code
Component: configure (show other issues)
Version: current
Hardware: PC Windows, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-01 09:31 UTC by pavel.lastovicka
Modified: 2017-05-20 11:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pavel.lastovicka 2009-10-01 09:31:08 UTC
Windows build fails during packaging because of missing msvcp71.dll in
external/msvcp71/. Configure does not report this. It should check for this
dependency as it does with other files in the external directory.
I build with --disable-build-mozilla --enable-build-mozab, using precompiled
binaries of Mozilla.
Comment 1 tml 2009-10-02 13:24:47 UTC
Is this report really for OOo 3.1.1? The prebuilt Mozilla DLLs for OOo 3.1.1 and
earlier *do* require msvcr71.dll.

Or is this for the development tree, what will become OOo 3.2 and later? The
prebuilt Mozilla DLLs for that indeed do not require msvcr71.dll, so there it is
unnecessary to refer to msvcr71 in the scp2/source/ooo/common_brand.scp file.

On the other hand, the prebuilt Mozilla DLLs for OOo 3.2 seem to be built with
MSVS8 and require msvcr80.dll, but there is nothing in dev300-m58 as far as I
can see to take care of that, to check for its presence and to bundle the merge
module for the VC80 CRT in the installer. Also, the MSVC80 runtime is supposed
to be installed only as side-by-side assemblies, and not in PATH, so as far as I
understand, the prebuilt Mozilla DLLs need to have manifests (either built-in or
separate .manifest files) in order for the msvcr80.dll to be found. 

Hopefully this will be fixed soon. Either by offering prebuilt Mozilla DLLs that
are built against the same VC90 CRT that OOo is built against, or taking care of
the manifest issue, and including the VC80 merge module in the installer.
Comment 2 pavel.lastovicka 2009-10-02 15:58:56 UTC
Yes this report is for OOO310_m19 :-)
And you are right that prebuilt Mozilla DLLs do require msvcr71.dll. But if
there will not be OO.o 3.1.2, I think it is now late to fix this issue.
Comment 3 tml 2009-10-02 17:01:05 UTC
Hmm, so is the problem you are reporting here just then that the build fails
late, when it should have failed much earlier already when running the configure
script?
Comment 4 pavel.lastovicka 2009-10-04 22:17:37 UTC
Exactly. It is unpleasant to start building in the evening and the next 
morning find that some dependency was not satisfied and have to wait some 
other hours for build to complete ;-)
Comment 5 pavel.lastovicka 2010-02-17 10:49:27 UTC
Setting the version tag to "current".  The problem still occurs with OO.o 3.2.
Unfortunately I don't have the canconfirm right.
Comment 6 pavel.lastovicka 2010-08-28 16:06:18 UTC
Confirming the issue.
It seems that current precompiled Mozilla binaries use MSVCR80 runtime, but #if
statement in common_brand.scp does not reflect this.
Comment 7 Marcus 2017-05-20 11:33:14 UTC
Reset assigne to the default "issues@openoffice.apache.org".