Hello Will, Which compiler you are using and what is the version of it? I am also facing the same problem on solaris. Also I am getting one more error as below when I link fontconfig to my application and compile it. ld: warning: file libgcc_s.so.1: required by /usr/openwin/lib/libfontconfig.so, not found Undefined first referenced symbol in file libiconv_open /usr/openwin/lib/libfontconfig.so libiconv /usr/openwin/lib/libfontconfig.so I am using gcc 2.95.3. Thanks and Regards, Rupa. -----Original Message----- From: fontconfig-bounces@lists.freedesktop.org [mailto:fontconfig-bounces@lists.freedesktop.org] On Behalf Of will Sent: Friday, March 03, 2006 12:49 AM To: Owen Taylor Cc: fontconfig@lists.freedesktop.org Subject: Re: [Fontconfig] iconv keeps fc-2.3.93 from compiling On Wed, 01 Mar 2006 06:55:35 -0500 Owen Taylor <otaylor@redhat.com> wrote:> On Wed, 2006-03-01 at 02:40 -0800, will wrote: > > Hi all, > > > > I am unable to compile fontconfig-2.3.93. > > > > I have libiconv 1.9.1-i586-4vl5 installed, as well as glibc 2.3.4. > > > > My system is: > > Dell Inspiron 5100 > > Vector Linux SOHO 5.1 > > 2.8GHz P4 > > ATI Radeon 7500 Mobility ( 64MB ) > > 768MB RAM > > > > fontconfig-2.2.96 compiles and installs fine. > > It''s just a mistake to put libiconv onto a system with a GLibc from > the last 5 years. You need to delete all traces of it off your system, > or all sorts of things will break in weird ways. > > (The problem looks like fontconfig included iconv.h from libiconv > rather than the correct system iconv.h, but wasn''t linked with the > libiconv -liconv.) > > Owen > >Finally got it to compile... you were right. I ended up having to upgrade glibc to 2.3.6 (PITA!!) Thanks for your help. _______________________________________________ Fontconfig mailing list Fontconfig@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fontconfig
Rupa Kamoji wrote:> Hello Will, > > Which compiler you are using and what is the version of it? I am also > facing the same problem on solaris. Also I am getting one more error as > below when I link fontconfig to my application and compile it.Solaris folks, Please try this patch, which is linked from freedesktop bug #4083. http://trs80.ucc.asn.au/gnometinderbox/patches/fontconfig-iconv.patch If it works, I''ll commit it. Of course, you should still listen to Owen if you''re on a glibc system. pat
When we build fontconfig 2.3.2 and earlier on Solaris, we use the iconv() in the system libc and never use libiconv, and it works fine. Haven''t tried the 2.3.9x series yet, but I would hope it''s the same. -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering Rupa Kamoji wrote:> Hello Will, > > Which compiler you are using and what is the version of it? I am also > facing the same problem on solaris. Also I am getting one more error as > below when I link fontconfig to my application and compile it. > > ld: warning: file libgcc_s.so.1: required by > /usr/openwin/lib/libfontconfig.so, not found > > Undefined first referenced > > symbol in file > > libiconv_open /usr/openwin/lib/libfontconfig.so > > libiconv /usr/openwin/lib/libfontconfig.so > > > I am using gcc 2.95.3. > > > Thanks and Regards, > Rupa. > > -----Original Message----- > From: fontconfig-bounces@lists.freedesktop.org > [mailto:fontconfig-bounces@lists.freedesktop.org] On Behalf Of will > Sent: Friday, March 03, 2006 12:49 AM > To: Owen Taylor > Cc: fontconfig@lists.freedesktop.org > Subject: Re: [Fontconfig] iconv keeps fc-2.3.93 from compiling > > On Wed, 01 Mar 2006 06:55:35 -0500 > Owen Taylor <otaylor@redhat.com> wrote: > >> On Wed, 2006-03-01 at 02:40 -0800, will wrote: >>> Hi all, >>> >>> I am unable to compile fontconfig-2.3.93. >>> >>> I have libiconv 1.9.1-i586-4vl5 installed, as well as glibc 2.3.4. >>> >>> My system is: >>> Dell Inspiron 5100 >>> Vector Linux SOHO 5.1 >>> 2.8GHz P4 >>> ATI Radeon 7500 Mobility ( 64MB ) >>> 768MB RAM >>> >>> fontconfig-2.2.96 compiles and installs fine. >> It''s just a mistake to put libiconv onto a system with a GLibc from >> the last 5 years. You need to delete all traces of it off your system, >> or all sorts of things will break in weird ways. >> >> (The problem looks like fontconfig included iconv.h from libiconv >> rather than the correct system iconv.h, but wasn''t linked with the >> libiconv -liconv.) >> >> Owen >> >> > > Finally got it to compile... you were right. I ended up having > to upgrade glibc to 2.3.6 (PITA!!) > > Thanks for your help. > _______________________________________________ > Fontconfig mailing list > Fontconfig@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/fontconfig > > _______________________________________________ > Fontconfig mailing list > Fontconfig@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/fontconfig
Alan Coopersmith wrote:> When we build fontconfig 2.3.2 and earlier on Solaris, we use the iconv() > in the system libc and never use libiconv, and it works fine. Haven''t > tried the 2.3.9x series yet, but I would hope it''s the same.Would it be correct to make fontconfig just ignore libiconv? It seems to cause nothing but grief! pat
Patrick Lam wrote:> Alan Coopersmith wrote: > >>When we build fontconfig 2.3.2 and earlier on Solaris, we use the iconv() >>in the system libc and never use libiconv, and it works fine. Haven''t >>tried the 2.3.9x series yet, but I would hope it''s the same. > > > Would it be correct to make fontconfig just ignore libiconv? It seems > to cause nothing but grief!For systems that have iconv() in libc? Probably. I thought libiconv was only really useful for systems that don''t have it in libc already. -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering
Alan Coopersmith wrote:> Patrick Lam wrote: > >> Alan Coopersmith wrote: >> >>> When we build fontconfig 2.3.2 and earlier on Solaris, we use the >>> iconv() >>> in the system libc and never use libiconv, and it works fine. Haven''t >>> tried the 2.3.9x series yet, but I would hope it''s the same. >> >> Would it be correct to make fontconfig just ignore libiconv? It seems >> to cause nothing but grief! > > For systems that have iconv() in libc? Probably. I thought libiconv > was only really useful for systems that don''t have it in libc already.Yeah. The problem is that it seems to cause negative progress, aka grief, for those who do have it in libc and who also have libiconv installed. pat