On Thu, 2012-08-16 at 10:51 +0800, James Chen wrote:
> > Cool - I assume you noticed you need to follow a build from the
> >top-level with something like:
> >
> > cd android/experimental/LibreOffice4Android/
> > make clean all install
...
> Michael, Thanks for the advice. Thank you!
On Tue, 2012-08-14 at 22:38 +0800, James Chen wrote:
> Thanks, tml and all of you! It builds successfully.
Cool - I assume you noticed you need to follow a build from the
top-level with something like:
cd android/experimental/LibreOffice4Android/
make clean all install
>> There are several "undefined reference" errors according to
>>vcl:PDEFWriter
>> and PDFWriterImpl during tail_build.
>
>Should be fixed since yesterday evening, git pull -r and try again.
>
>--tml
Thanks, tml and all of you! It builds successfully.
___
> There are several "undefined reference" errors according to vcl:PDEFWriter
> and PDFWriterImpl during tail_build.
Should be fixed since yesterday evening, git pull -r and try again.
--tml
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
There are several "undefined reference" errors according to vcl:PDEFWriter
and PDFWriterImpl during tail_build.
Complete log can be found at http://pastebin.com/9zhVBvf2
Any advice? Thanks.
James
___
LibreOffice mailing list
LibreOffice@lists.freedes
>On 13/08/12 12:04, James Chen wrote:
>> Encounter another error while building freetype
>>
>> log for /Users/jamchen/Developer/Android/libreoffice_core/freetype
>> dmake:
>>
>>/Users/jamchen/Developer/Android/libreoffice_core/solenv/inc/settings.mk:
>> line 55: Error: -- Include file
>>
>>/
On Mon, 2012-08-13 at 12:53 +0200, Michael Stahl wrote:
> this indicates freetype is missing a dependency on the "solenv" module,
> have fixed that on master now, please try again
Oooh - I've seen that for ages and not seen how to fix it - and just
worked around it by re-running make ;-)
On 13/08/12 12:04, James Chen wrote:
> Encounter another error while building freetype
>
> log for /Users/jamchen/Developer/Android/libreoffice_core/freetype
> dmake:
> /Users/jamchen/Developer/Android/libreoffice_core/solenv/inc/settings.mk:
> line 55: Error: -- Include file
> /Users/jamchen/D
Encounter another error while building freetype
log for /Users/jamchen/Developer/Android/libreoffice_core/freetype
dmake:
/Users/jamchen/Developer/Android/libreoffice_core/solenv/inc/settings.mk:
line 55: Error: -- Include file
/Users/jamchen/Developer/Android/libreoffice_core/solver/unxandr.pr
Hi, Stephan,
>>
>> Thanks for pointing out and the hints.
>> Removing /opt/local/bin from PATH does not work for me.
>
>Even not with a clean rebuild from scratch afterwards? I'd assume some
>mis-configuration (likely caused by picking up MacPort's
>/opt/local/bin/pkg-check) was still manifest i
On 08/13/2012 08:38 AM, James Chen wrote:
ld: warning: ignoring file /opt/local/lib/libiconv.dylib, file was built
for unsupported file forma
ld: warning: ignoring file /opt/local/lib/libz.dylib, file was built for
unsupported file format
ld: in /opt/local/lib/libiconv.2.dylib, file was built for
>>ld: warning: ignoring file /opt/local/lib/libiconv.dylib, file was built
>> for unsupported file forma
>> ld: warning: ignoring file /opt/local/lib/libz.dylib, file was built for
>> unsupported file format
>> ld: in /opt/local/lib/libiconv.2.dylib, file was built for unsupported
>> file format
>
> ld: warning: ignoring file /opt/local/lib/libiconv.dylib, file was built
> for unsupported file forma
> ld: warning: ignoring file /opt/local/lib/libz.dylib, file was built for
> unsupported file format
> ld: in /opt/local/lib/libiconv.2.dylib, file was built for unsupported
> file format
Hmm, w
>I don't think that's a good idea, it mixes up options for the build
>and host platforms. (Consider the case of cross-compiling from an
>Intel Mac to PowerPC-based Mac, in theory it should be possible to use
>a current Xcode and SDK for the build platform code, and Xcode 3 +
>10.4 SDK for the host
> In my environment, Mac OS 10.8 and Xcode 4.4.1, without specifying Mac OS
> X SDK version, it picks 10.6 as Mac OS X SDK.
> And then it failed since it can't find gcc-4.2.
Ah, OK. Was there some Xcode that came with both a 10.6 SDK *and* a
gcc 4.2 then? Making this SDK and compiler selection wor
In my environment, Mac OS 10.8 and Xcode 4.4.1, without specifying Mac OS
X SDK version, it picks 10.6 as Mac OS X SDK.
And then it failed since it can't find gcc-4.2. So I tried to use option
--with-macosx-sdk with 10.8.
It's building now!
During applying --with-macosx-sdk option, I found some ty
Thank you, tml!
I've pulled latest code and I'm trying to build it.
According to the location of Xcode.app, I recall it's kind of personal
preference. :P I thought it was misplaced so I move it back.
Luckily, xcode-select and xcrun are still in /usr/bin.
Thanks, again. I'll report in the result
The root cause to your problem is that you are building the MacOSX
build-time software as 64-bit code, and LO (including the build-time
tools that it builds in order to use them later during the build)
needs to be built as 32-bit code on the Mac. (And Windows, BTW. It's
only for Linux that LO can b
18 matches
Mail list logo
