On 01/11/2018 09:29 PM, jan iversen wrote:
During today (updated master early evening) I started getting strange
linker errors:
When linking for ARM64 with or without debug I get:
Undefined symbols for architecture arm64:
"_lo_get_constructor_map", referenced from:
cppuhelper::detail::loadSharedLibComponentFactory(rtl::OUString
const&, rtl::OUString const&, rtl::OUString const&, rtl::OUString
const&, rtl::OUString const&,
com::sun::star::uno::Reference<com::sun::star::lang::XMultiServiceFactory>
const&, std::__1::function<com::sun::star::uno::XInterface*
(com::sun::star::uno::XComponentContext*,
com::sun::star::uno::Sequence<com::sun::star::uno::Any> const&)>*,
com::sun::star::uno::Reference<com::sun::star::uno::XInterface>*) in Kit.o
"_lo_get_factory_map", referenced from:
cppuhelper::detail::loadSharedLibComponentFactory(rtl::OUString
const&, rtl::OUString const&, rtl::OUString const&, rtl::OUString
const&, rtl::OUString const&,
com::sun::star::uno::Reference<com::sun::star::lang::XMultiServiceFactory>
const&, std::__1::function<com::sun::star::uno::XInterface*
(com::sun::star::uno::XComponentContext*,
com::sun::star::uno::Sequence<com::sun::star::uno::Any> const&)>*,
com::sun::star::uno::Reference<com::sun::star::uno::XInterface>*)
When I link for X86_64 it works fine.
Definitions for those functions are generated by bin/native-code.py. I
do see uses of that (and of the generated native-code.h) in module ios
(but have no further insight into that module).
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.