Issue 17372 - OOo 1.1RC on Linux needs freetype >=2.0.5
Summary: OOo 1.1RC on Linux needs freetype >=2.0.5
Status: CLOSED DUPLICATE of issue 16872
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-07-24 16:20 UTC by simix
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description simix 2003-07-24 16:20:15 UTC 
I have tried to install 1.1rc on RedHat 7.2 and it appears that freetype >=
2.0.5 is needed on the system. The installer crashes with the following error:
/home/simix/net/OpenOffice.org1.1/program/soffice.bin: relocation error:
/home/simix/net/OpenOffice.org1.1/program/libvcl645li.so: undefined symbol:
FT_Activate_Size

I found out that FT_Activate_Size wa introduced in freetype 2.0.5 and I, like
may others, have older version installed.

So, my naive question is whether FT could be linked statically into the binaries
to make them independant of the OS?
Comment 1 dankegel 2003-07-25 02:32:13 UTC 
See also
issue 16872 - Crash in i18npool component_getFactory() upon startup
issue 16450 - OOo1.1 rc1 FR localized can't install lipspa645li.so

I think this is a dup of issue 16450.  I think the fix is noted in
issue 16872.  I'll let the developers say for sure...

Thanks for your clear report!
Comment 2 Olaf Felka 2003-07-25 08:24:55 UTC 
Yes ,duplicate.

*** This issue has been marked as a duplicate of 16872 ***
Comment 3 Olaf Felka 2003-07-25 08:25:32 UTC 
Why not making a query before writing an issue?
Comment 4 simix 2003-07-25 11:03:00 UTC 
What did I make wrong please?

I have posted to bug 16872 before but I couldn't find an analysis why
this problem exists. You said it may be a problem with FR localization
but that's not the case.

So then, I investigated the problem and created a new report which is
clear to understand and other peoples will find it easily.

FYI, I did query for the bug first but couldn't find it.