I managed to do a strings /usr/X11R7/lib/libfreetype.so | grep FTC_Manager_New and got nothing returned BUT on the (now magically working) netbsd VM it yields the same results.
I'm half tempted to maybe create a new VM from scratch and install netbsd and then once I get the essentials I need to maybe try building from SVN again to see what comes about. Nick On Thu, Nov 11, 2010 at 6:16 PM, Lars Sonchocky-Helldorf < [email protected]> wrote: > > Am 12.11.2010 um 02:04 schrieb Nick Allgood: > > > When I do the following I don't get anything: >> >> grep FTC_Manager_new /usr/X11R7/lib/libfreetype.so.6 ...but as I said I >> see it in the .h >> >> Would grepping for a string like that in a compiled binary even work in >> the first place? >> > > not on all platforms. From the man page of grep on Darwin: > > -a, --text > Process a binary file as if it were text; this is equivalent > to > the --binary-files=text option. > > >> Nick >> > > regards, > > Lars > > > >> On Thu, Nov 11, 2010 at 5:23 PM, Nick Allgood <[email protected]> >> wrote: >> Where exactly IS the library installed... libgnustep-back >> >> Nick >> >> >> On Thu, Nov 11, 2010 at 4:18 PM, Fred Kiefer <[email protected]> wrote: >> You seem to have both X11R6 and X11R7 in your path, which is a bad >> thing. Still the configure script only lists references to the X11R7 >> directory, no idea why R6 should ever turn up in a gcc command line. >> >> Did you try to run the grep statement I send you? Having FTC_Manager_New >> in the header is good, having it in the library itself is the important >> thing :-) >> >> An ldd output for the GNUstep back library would help more than the one >> for ProjectCenter. >> >> Am 11.11.2010 01:33, schrieb Nick Allgood: >> > * freetype version is 6.3.17 >> > >> > * Looks like /usr/X11R7/include/freetype2/freetype/ftcache.h includes >> > FTC_Manager_New >> > >> > * I don't see but the 1 version of libfreetype >> > >> > * ldd of ProjectCenter: >> > ----------- >> > >> > ./ProjectCenter: >> > -lc.12 => /usr/lib/libc.so.12 >> > -lobjc.2 => /usr/lib/libobjc.so.2 >> > -lpthread.0 => /usr/lib/libpthread.so.0 >> > -lgmp.10 => /usr/pkg/lib/libgmp.so.10 >> > -ltasn1.3 => /usr/pkg/lib/libtasn1.so.3 >> > -lz.1 => /usr/lib/libz.so.1 >> > -lintl.0 => /usr/lib/libintl.so.0 >> > -lgpg-error.0 => /usr/pkg/lib/libgpg-error.so.0 >> > -lgcrypt.11 => /usr/pkg/lib/libgcrypt.so.11 >> > -lgnutls.26 => /usr/pkg/lib/libgnutls.so.26 >> > -lm.0 => /usr/lib/libm.so.0 >> > -lxml2.2 => /usr/pkg/lib/libxml2.so.2 >> > -lxslt.1 => /usr/pkg/lib/libxslt.so.1 >> > -lffi.5 => /usr/pkg/lib/libffi.so.5 >> > -lkvm.5 => /usr/lib/libkvm.so.5 >> > -lrt.0 => /usr/lib/librt.so.0 >> > -lgnustep-base.1.21.1 => >> > /usr/GNUstep/Local/Library/Libraries/libgnustep-base.so.1.21.1 >> > -lungif.4 => /usr/pkg/lib/libungif.so.4 >> > -lpng14.14 => /usr/pkg/lib/libpng14.so.14 >> > -ljpeg.8 => /usr/pkg/lib/libjpeg.so.8 >> > -ltiff.3 => /usr/pkg/lib/libtiff.so.3 >> > -lgnustep-gui.0.19.0 => >> > /usr/GNUstep/Local/Library/Libraries/libgnustep-gui.so.0.19.0 >> > -lProjectCenter.0.6.0 => >> > /usr/GNUstep/Local/Library/Libraries/libProjectCenter.so.0.6.0 >> > >> > ------ >> > >> > >> > >> > * X11R6 seems to have the same directory structure as X11R7 BUT it >> doesn't >> > seem there is much in there... the X11R6 directory is 344K while the >> X11R7 >> > is 250MB...so that tells me everything resides in X11R7 >> > >> > * Xbinaries are linked too /usr/X11R7/bin .. there is nothing in >> > /usr/X11R6/bin >> > >> > *All GNUstep binaries are the latest via SVN (But the same issues >> occurred >> > with the most recent tarball distributions as well as the stuff in >> pkgsrc >> > for netbsd...which is a version behind the current tarball distro) >> > >> > -- config.log is attached >> > >> > >> > Nick >> > >> > >> > On Wed, Nov 10, 2010 at 12:14 PM, Nicola Pero < >> > [email protected]> wrote: >> > >> >> It may be a red herring. ;-) >> >> >> >> I agree with Fred that the most important thing is getting more >> information >> >> ... in particular >> >> related to the original error message ... >> >> >> >> * which version of freetype are you using ? >> >> >> >> * does you freetype library actually include FTC_Manager_New or not ? >> >> >> >> * do you have multiple versions of the freetype library installed by >> any >> >> chance ? >> >> >> >> * try using 'ldd' on your executable and on the various shared >> libraries >> >> to see what >> >> libraries are being used >> >> >> >> * since you have both X11R6 and X11R7, what files do you have in the >> two >> >> directories ? >> >> >> >> * are your X binaries (or X programs that work) linked to libraries in >> >> X11R6 or X11R7 or both ? >> >> >> >> * are the GNUstep binaries the same ? Any difference you can spot >> with >> >> other X binaries ? >> >> >> >> * any other information that may be useful ... worth posting it (don't >> >> worry about attaching >> >> too much information) >> >> >> >> Without more information, none of us can really help much. We can just >> >> guess, but without solid >> >> information, our guesses won't necessarily have much relationship to >> >> reality. ;-) >> >> >> >> Thanks >> >> >> >> -----Original Message----- >> >> From: "Nick Allgood" <[email protected]> >> >> Sent: Wednesday, 10 November, 2010 01:54 >> >> To: "Fred Kiefer" <[email protected]> >> >> Cc: [email protected] >> >> Subject: Re: Issue starting Gorm, ProjectCenter, GWorkspace..etc on >> netbsd >> >> 5.0.2 >> >> >> >> _______________________________________________ >> >> Discuss-gnustep mailing list >> >> [email protected] >> >> http://lists.gnu.org/mailman/listinfo/discuss-gnustep >> >> Same results on my home vm.. $PATH has both /usr/X11R6/bin and >> >> /usr/X11R7/bin and they are real directories >> >> >> >> Nick >> >> >> >> On Tue, Nov 9, 2010 at 9:18 AM, Nick Allgood <[email protected]> >> >> wrote: >> >> >> >>> In both my VM's (work and home) that have netbsd .. they both have >> >>> /usr/X11R6/bin and /usr/X11R7/bin .. and I just verified they indeed >> are >> >>> distinct directories (not symlinks) >> >>> >> >>> Oddly enough, Project Center and Gorm magically started to work on the >> >> work >> >>> VM of netbsd yesterday.. I have no clue why either.. i didn't touch >> >>> it...though my home one is still having the same issue in this thread. >> >>> >> >>> When i get home I'll give my home one a whirl and see if i can check >> out >> >>> the PATH and configure stuff >> >>> >> >>> Thanks! >> >>> >> >>> Nick >> >>> >> >>> On Tue, Nov 9, 2010 at 2:07 AM, Fred Kiefer <[email protected]> >> wrote: >> >>> >> >>>> Hi Nick, >> >>>> >> >>>> with Nicola's findings I think it is important to have a look at the >> >>>> config.log and config.h files produced by configure. Somehow two >> >>>> different versions of X11 are found and this is a problem in itself >> and >> >>>> needs to be fixed. And this may resolve your original issue as well. >> >>>> Are these directories actually different or is one a link to the >> other >> >>>> and where could the wrong one come from? Here you should check your >> path >> >>>> environment variable: >> >>>> echo $PATH >> >>>> >> >>>> Cheers >> >>>> Fred >> >>>> >> >>>> Am 08.11.2010 22:10, schrieb Fred Kiefer: >> >>>>> Am 08.11.2010 13:56, schrieb Nicola Pero: >> >>>>>> >> >>>>>>>> freetype-config --libs >> >>>>>>>> >> >>>>>>>> and it should return the right command options, but obviously it >> >>>> doesn't. >> >>>>>>> >> >>>>>>> It looks like the problem is that it is providing the correct >> flags >> >> to >> >>>> pass to ld, but we are passing them to gcc. >> >>>>>> >> >>>>>> Why do you say that ? Any evidence ? >> >>>>>> >> >>>>>> What I personally immediately noticed in that linker command line >> is >> >>>> that it has both -Wl,-R/usr/X11R6/lib -L/usr/X11R6/lib >> >>>>>> *and* -Wl,-R/usr/X11R7/lib -L/usr/X11R7/lib. Wouldn't these refer >> to >> >>>> different releases of X11 ? Is it wise to link >> >>>>>> against the two at the same time ? Wouldn't you get conflicting >> (or >> >>>> just the wrong) libraries linked in ? >> >>>>> >> >>>>> Well spotted! I overlooked this even when copying the link line into >> >> my >> >>>>> mail and editing it. Any idea how this could happen? Do we screw up >> >>>>> within configure or later one? >> >> >> >> _______________________________________________ >> Discuss-gnustep mailing list >> [email protected] >> http://lists.gnu.org/mailman/listinfo/discuss-gnustep >> > >
_______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
