Re: Issue starting Gorm, ProjectCenter, GWorkspace..etc on netbsd 5.0.2

[Nicola Pero]

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" <nick.allgood@gmail.com>
Sent: Wednesday, 10 November, 2010 01:54
To: "Fred Kiefer" <fredkiefer@gmx.de>
Cc: discuss-gnustep@gnu.org
Subject: Re: Issue starting Gorm, ProjectCenter, GWorkspace..etc on netbsd 5.0.2

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
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 <nick.allgood@gmail.com> 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 <fredkiefer@gmx.de> 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?
>>
>
>