Re: Link error: undefined reference to `__mulodi4' with Clang 32-bit

slacka <lukebenes -AT- hotmail.com>
Wed, 3 May 2017 10:00:30 -0700 (MST)

I build with x86 because my home laptop is a Dell Precision M90 Core Duo
T2700 which is a 32-bit CPU. This machine has a gorgeous 16:10 display which
is hard to find these days. The other machine is just a 32-bit image on a VM
that I spool up to verify bugs.  It does have the added benefit of less
memory usage than its x86-64 bit counterpart. 


Up until these recent 2 regressions (jpeg-turbo and mulodi4) , I've been
building 32-bit builds with Clang for the past couple of years.




--
View this message in context: 
http://nabble.documentfoundation.org/Link-error-undefined-reference-to-mulodi4-with-Clang-32-bit-tp4213636p4213759.html
Sent from the Dev mailing list archive at Nabble.com.

Context

Link error: undefined reference to `__mulodi4' with Clang 32-bit · Luke Benes
- Re: Link error: undefined reference to `__mulodi4' with Clang 32-bit · Stephan Bergmann
  - Re: Link error: undefined reference to `__mulodi4' with Clang 32-bit · slacka
    - Re: Link error: undefined reference to `__mulodi4' with Clang 32-bit · Stephan Bergmann
      - Re: Link error: undefined reference to `__mulodi4' with Clang 32-bit · slacka

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.