On Jan 20, 2012, at 3:30 AM, Arthur Norman wrote:
> to investigate further why your test scripts are failing. I believe macports
> isn't providing all the necessary libraries.
>>
>> I'm not sure what you mean by forcing -lX11 -lXext, but you should be
> linking to the macports X11 libs (i.e. those in the /opt/local/... path).
>>
> What I mean is that when it set CFLAGS, LIBS etc in its customised way it had
> not put -lX11 into LIBS and so I need to. This is all to do with just what it
> expects me to set up via my configure script and what it will insist on
> having its own settings for. Somewhere there may be a lengthy explanation on
> their web-site of what they do and require and expect, and why they do it
> that way! But at present it seems that they expect me to put in -lX11 but not
> -L/usr/X11R6/lib while on native xcode I need to put in both.
I don't think you should do this. For instance, in the config.log for CSL I
found:
configure:6574: checking Xlib.h presence
configure:6574: /Developer/usr/bin/clang -E -I/opt/local/include
-I/usr/X11R6/include -I/usr/X11R6/include conftest.c
conftest.c:33:10: fatal error: 'Xlib.h' file not found
#include <Xlib.h>
^
1 error generated.
But MacPorts puts the X11 LIBS in /opt/local/include/X11 and Xlib.h is in that
directory. Now, if you look in the portfile I have listed port:xorg-libX11
under depends_lib. If its not passing that path to the config/makefile then we
need to find out why?
Can someone on the dev-list please verify?
Mark
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
