Issue 123810 - Current Buildbot snapshot rev 1547747 installing and requires MS C++ 2008, msvc90.dll but package documentation says a msvcr100.dll is needed
Summary: Current Buildbot snapshot rev 1547747 installing and requires MS C++ 2008, ms...
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 4.1.0-dev
Hardware: PC Windows 7
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on: 120979
Blocks:
  Show dependency tree
 
Reported: 2013-12-05 15:57 UTC by V Stuart Foote
Modified: 2017-05-20 09:44 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description V Stuart Foote 2013-12-05 15:57:11 UTC 
On Windows 7 sp1, 64-bit en-US

The current Buildbot nightly rev1547747 installs Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 and msvc90.dll. 

I performed an /A administrative install for the first time in a while, and I first reverted the MSVC install that is run when the package is extracted. 

Then as package documentation readme.txt and readme.html indicate a msvcr100.dll is needed, attempt to launch with a 32-bit MS Visual C++ 2010 already present on system. However AOO rev1547747 will not launch. Brief--unreadable dialog message and abort--can't find any log record of the failed launch.

Download and install current 32-bit MS Visual C++ 2010 for msvcr100.dll.  AOO 4.1.0 rev 1547747 still will not launch. 

Install AOO rev1547747 packaged MS Visual C++ 2008 with its msvcr90.dll (x86 9.0.30729.6161) and AOO launches and fully functional.

Is this a Buildbot packaging issue--or is there some disconnect between stated C/C++ runtime requirements?  We had an older issue about requiring the msvcr100.dll for Java JRE stability, bug 120979 -- is the requirement still valid and shouldn't the AOO 4.1.0 dev snapshots be built against that runtime and it be packaged?
Comment 1 hdu@apache.org 2013-12-05 16:57:30 UTC 
(In reply to V Stuart Foote from comment #0)
> The current Buildbot nightly rev1547747 installs Microsoft Visual C++ 2008
> Redistributable - x86 9.0.30729.6161 and msvc90.dll.

Yes. It builds with MSVC2008 and the target depends on having a runtime matching to that compiler, i.e. the *90* version.

> I performed an /A administrative install for the first time in a while, and
> I first reverted the MSVC install that is run when the package is extracted.

So you uninstalled msvc90.dll and its friends?

> Then as package documentation readme.txt and readme.html indicate a
> msvcr100.dll is needed, attempt to launch with a 32-bit MS Visual C++ 2010
> already present on system. However AOO rev1547747 will not launch.
> Brief--unreadable dialog message and abort--can't find any log record of the
> failed launch.
> 
> Download and install current 32-bit MS Visual C++ 2010 for msvcr100.dll. 
> AOO 4.1.0 rev 1547747 still will not launch. 
> 
> Install AOO rev1547747 packaged MS Visual C++ 2008 with its msvcr90.dll (x86
> 9.0.30729.6161) and AOO launches and fully functional.

Yes. You C-runtime libs matching to the compiler used for building the app+libs are needed. With MSVC2008==VC9.0 the 90 runtime is needed.

> Is this a Buildbot packaging issue--or is there some disconnect between
> stated C/C++ runtime requirements?  We had an older issue about requiring
> the msvcr100.dll for Java JRE stability, bug 120979 -- is the requirement
> still valid

Yes, that requirement is valid until the Java7 problem described in http://www.duckware.com/tech/java6msvcr71.html is solved. Maybe it already is in newer versions.

> and shouldn't the AOO 4.1.0 dev snapshots be built against that
> runtime and it be packaged?

If AOO was building with MSVC2010 then this would be the case. But it currently doesn't, some adjustments to Makefiles and other solenv files would be needed.
 
I'd say the best status for this issue is NOT_AN_ISSUE. But an enhancement issue like "allow building with MSVC201*" would be great.
Comment 2 V Stuart Foote 2013-12-05 17:22:22 UTC 
(In reply to hdu@apache.org from comment #1)

> > I performed an /A administrative install for the first time in a while, and
> > I first reverted the MSVC install that is run when the package is extracted.
> 
> So you uninstalled msvc90.dll and its friends?

Yes, but just the AOO packaged Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161. Have a number of MSVC++ runtimes still present including--I think--earlier 2008 packaging.

If I were doing a full install, I would as usual not have paid much attention to the bundled MSVC runtime. But since I setup for an /A administrative install I actually RTM and noticed the discrepancy ;)
Comment 3 V Stuart Foote 2013-12-05 17:58:40 UTC 
The prior incubator Dev ML discussion that resulted in bug 120979 is here: http://markmail.org/thread/axfeyzyux66sz37h#query:+page:1+mid:khhdkhphbxkk7kjy+state:results

Understand it better now. Maybe a change to the packaging readme texts?

Also, just went ahead and opened the .msi installer package in Orca and the msvcr100.dll is still present there as originally done to resolve i120979.

So, as noted--not an issue, but perhaps the enhancement to move builds to MS Visual C++ 201x as noted

Lesson learned, sorry for the noise.
Comment 4 hdu@apache.org 2013-12-06 07:07:26 UTC 
(In reply to V Stuart Foote from comment #3)
> Understand it better now. Maybe a change to the packaging readme texts?

Please suggest a better readme text, if possible as a patch.

> So, as noted--not an issue, but perhaps the enhancement to move builds to MS
> Visual C++ 201x as noted

This is really overdue. Would you be interested in working on it? I'm sure you have all the skills needed to attack and solve that task.

> Lesson learned, sorry for the noise.

No problem at all. Of course its kind of AOO's fault, because its build system still depends on the old compiler.
Comment 5 hdu@apache.org 2013-12-06 08:17:44 UTC 
(In reply to hdu@apache.org from comment #4)
> Of course its kind of AOO's fault, because its build
> system still depends on the old compiler.

By the way: There is the "Capstone 2013" [1] project mentored by Jan. This project is on track to solve that problem and many others and make the build experience on Windows much more inviting.

[1] https://wiki.openoffice.org/wiki/Build_System_Analysis:capstone2013_windows_build
Comment 6 V Stuart Foote 2013-12-06 15:37:19 UTC 
(In reply to hdu@apache.org from comment #4)
 
>... Would you be interested in working on it? I'm sure
> you have all the skills needed to attack and solve that task.
>
Oh no!, that would be very bad. I scrape by with MSys and GCC for the occasional C or Fortran procedural program I need on Windows. Beyond that I'm mostly useless with C++.