Bug 6550 - 2.4 Branch/HP-UX: Linker-Error (inline)
Summary: 2.4 Branch/HP-UX: Linker-Error (inline)
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.3
Hardware: x86 (IA32) HP-UX
: high major
Assignee: Keith Packard
QA Contact:
Depends on:
Reported: 2006-04-10 18:08 UTC by Christoph Bauer
Modified: 2006-04-11 01:01 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Christoph Bauer 2006-04-10 18:08:16 UTC
on HP-UX fontconfig fails with this error.

make[2]: Entering directory 
source='fc-case.c' object='fc-case.o' libtool=no \
DEPDIR=.deps depmode=hp /bin/sh ../depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -I.. -I/T/tcl_tk/8.5/add-on-
libs/hp7u11/include/freetype2 -I/T/tcl_tk/8.5/add-on-libs/hp7u11/include     -
O -Ae +DAportable -c fc-case.c
cc  -O -Ae +DAportable  -Wl,+vshlibunsats -Wl,-z -Wl,+s -Wl,-B,immediate -o fc-
case  fc-case.o  
/usr/ccs/bin/ld: Unsatisfied symbols:
   _fcValueLists (first referenced in fc-case.o) (data)
   _fcPatternElts (first referenced in fc-case.o) (data)
   FcDebugVal (first referenced in fc-case.o) (data)
make[2]: *** [fc-case] Error 1

I think of inline definition which are used in the library only should
go in a new header file or should be hidden for the tools by a 
statement or somthing like that.

Comment 1 Dom Lachowicz 2006-04-10 22:24:11 UTC
Can you remove the word "inline" from those functions in fcint.h and let me know
what happens? Thanks.
Comment 2 Christoph Bauer 2006-04-10 22:36:27 UTC
Same error. the linker expects a definition for

extern FcValueList ** _fcValueLists;
extern FcValueList ** _fcPatternElts;

These variables are used in the inline functions. for gcc
no problem if neither the function is used nor there is
a defintion for the external variables.
Comment 3 Patrick Lam 2006-04-11 08:08:45 UTC
Should be fixed now.
Comment 4 Christoph Bauer 2006-04-11 18:01:57 UTC
Ok, compilation is fine now.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.