Le 09/11/2012 01:10, Schindler Karl-Michael a écrit :
OK. With the new patch, there is progress, but still one issue.
gcc -m32 -dynamiclib -dylib_install_name,libgrx20X-2.4.9.dylib -o ../lib/macosx/libgrx20X-2.4.9.dylib draw/bitblt.lo ...
fails with missing symbols from X11. Therefore, i tried
make LDOPT='-m32 -L/usr/X11/lib -lX11'
which gives a succesfull
gcc -m32 -L/usr/X11/lib -lX11 -dynamiclib -dylib_install_name,libgrx20X-2.4.9.dylib -o ../lib/macosx/libgrx20X-2.4.9.dylib draw/bitblt.lo ...
I would be better to include instead $(X11LIBS) in this line of src/makefile.osx: it does the same but keeps everything independant. I have corrected and uploaded to the GRX "more things" directory.
In fact I do not understand why this is necessary in OSX and not in X11. Including this change in src/makefile.osx and not src/makefile.x11 keeps the two issues independants.
In X11 including $(X11LIBS) is necessary only when compiling binaries $(UTILP) $(UTILPX) and test programs, not when compiling the libraries.
Looking into the two linux systems I have access to, I see - In one, a group computer to which I have full root access, there is no /usr/X11 directory, only a /usr/X11R6 directory which contains virtually nothing, only a bin subdirectory containing symlinks to mkfontdir and mkfontscale - In the other, a lab computer to which I have no root access, I see neither /usr/X11 nor /usr/X11R6 directories (but they could be hidden from ordinary users).
X11 files are contained in regular /usr/include, /usr/lib, /usr/lib32, /usr/lib64 directories, and thus they are not found through $(X11INCS) and $(X11LIBS). The only necessary stuff when compiling binaries seems to be -lX11 contained in $(X11LIBS).
Probably you can check on your system.
Maurice