Hi,
On Sun, Sep 25, 2011 at 1:44 PM, Manfred J. Krause wrote:
On Sun, Sep 25, 2011 at 1:20 PM, Pedro wrote:
Master 2011-09-24 has the same problem
Here is a screen capture of the error messages
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:Program Files\LibO-dev 3. 5\program\scalc.exe
R6034
An application has made an attempt to load the C runtime library
incorrectly.
Please contact the application’s support team For more information. [...]
Yes, I can confirm the "bad news" (on WinXP); [...]
See also: [Libreoffice-qa] WIN Master Builds broken
http://lists.freedesktop.org/archives/libreoffice-qa/2011-September/000218.html
See also:
Bug 30467 - required visual studio 2008 redistributable libraries not
installed, failed to start · Comment #21
https://bugs.freedesktop.org/show_bug.cgi?id=30467#c21
"This is a known problem. The executables lack any resource section, due to the
gbuildification of desktop module. We are working on it. Don't expect it to be
fixed this week though." [Fridrich Strba]
mjk
--
TDF Wiki · BugReport Details
http://wiki.documentfoundation.org/BugReport_Details
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.