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
