On Jan 27, 2008, at 5:53 PM, Daniel J. Luke wrote:
It doesn't look like that was the problem in this case, since it
fails the same way for me when I remove that symlink. I don't have
the same problem with configure on my other Leopard machine, so I
suppose there's something peculiar with
Daniel J. Luke wrote:
Looks like it fails with the 'Broken X11 install. No X11 headers' error
even if you run it with -without-x
As a workaround:
./configure LDFLAGS=-L/usr/X11/lib
Works for me...
Rainer
___
macports-dev mailing list
Rainer Müller:
Looks like it fails with the 'Broken X11 install. No X11 headers'
error even if you run it with -without-x
As a workaround:
./configure LDFLAGS=-L/usr/X11/lib
Works for me...
Errors like these are sometimes caused by the stupid symlink:
/usr/include/X11 - ../X11/include/X11
Daniel J. Luke wrote:
Looks like it fails with the 'Broken X11 install. No X11 headers'
error even if you run it with -without-x
I can reproduce this, on Leopard. It's a bug, will add to Trac once it
wakes up from the coma.
i.e. it reports that error even *with* all headers, if you
On Jan 27, 2008, at 3:24 PM, Anders F Björklund wrote:
Looks like it fails with the 'Broken X11 install. No X11 headers'
error even if you run it with -without-x
As a workaround:
./configure LDFLAGS=-L/usr/X11/lib
Works for me...
Errors like these are sometimes caused by the stupid
checking build system type... powerpc-apple-darwin9.1.0
checking host system type... powerpc-apple-darwin9.1.0
checking target system type... powerpc-apple-darwin9.1.0
checking for sw_vers... sw_vers
checking Mac OS X version... 10.5.1
checking Xcode version... 3.0
checking MacPorts version...
On Jan 26, 2008, at 5:46 PM, Ryan Schmidt wrote:
Sooo what's goin' on here, Daniel? :)
Sorry, the machine I run the regen on was upgraded to 10.5 recently. I
thought I had installed the X11SDK, but I could have missed it.
--
Daniel J. Luke
