Jan Haag wrote:
Thank you for the answers... I'll try and find out which packages are
affected.
At least I know what I'm facing now, and maybe one can get this old
script
back working, at least until all the packages detect X11 without it.
Hundreds of packages have been fixed already, so
Hi list,
I'm not sure wether or not this is the right place to ask, but on my
newly installed Mac OS X 10.6
it looks like any package depending on X11 doesn't find it... As far
as I understood the workflow
of the autoconf-script, the headers should be found, but the libraries
not...
The fink
Jan Haag wrote:
Hi list,
I'm not sure wether or not this is the right place to ask, but on my
newly installed Mac OS X 10.6
it looks like any package depending on X11 doesn't find it... As far
as I understood the workflow
of the autoconf-script, the headers should be found, but the
Jan Haag wrote:
Hi list,
I'm not sure wether or not this is the right place to ask, but on my
newly installed Mac OS X 10.6
it looks like any package depending on X11 doesn't find it... As far
as I understood the workflow
of the autoconf-script, the headers should be found, but the
Well... It basically shows up in configure saying
checking for X... no
That holds true for any package that checks for it... I only found it
in trying to install
libxfce4mcs3-4.2.3-1003, but other packages seem to have the same
problem.
I'm not too good when it comes to shell scripting, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It doesn't actually work on on a 10.5 setup which doesn't have a
/usr/X11/bin/xmkmf, either. That's the normal state of X11s that were
installed after OS 10.5.2 or so. People who started at 10.5.0 may still
have it, since Software Update doesn't
Thank you for the answers... I'll try and find out which packages are
affected.
At least I know what I'm facing now, and maybe one can get this old
script
back working, at least until all the packages detect X11 without it.
Jan
On Sep 10, 2009, at 10:16 PM, Alexander Hansen wrote:
