Hi,
after installing the prerequisites (64 bit OS and VS Professional) i've
found the current problem:
x64 object compilation was still done with X86 arch and not with AMD64
architecture.
Only gb_StaticLibrary_add_x64_generated_exception_objects exists for now
and
i am adding the similar machinery (add_x64_generated_cobjects) for
C-objects and will resubmit the patch.
Regards
David
On 19.10.2012 06:58, David Ostrovsky wrote:
Norbert,
Wow your early adoption of gerrit patchset verification is very
impressive.
Thank you for that!
Any chance of publishing the build error log here?
[...]
Regards
David
Am 19.10.2012 05:37, schrieb Norbert Thiebaud (via Code Review):
Norbert Thiebaud has posted comments on this change.
Change subject: gbuildification of expat
......................................................................
Patch Set 7: Fails
Failed build of 24540109372399455a17bd20a550f828013b8668 on
tinderbox: W2008R2@16-minimal_build
--
To view, visit https://gerrit.libreoffice.org/867
To unsubscribe, visit https://gerrit.libreoffice.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I3b3aa40f39ef82c70f6f28790b582c83e48bdf76
Gerrit-PatchSet: 7
Gerrit-Project: core
Gerrit-Branch: master
Gerrit-Owner: David Ostrovsky <David.Ostrovsky@gmx.de>
Gerrit-Reviewer: Norbert Thiebaud <nthiebaud@gmail.com>
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.