On 13/06/2005, at 11:48, Dave Vasilevsky wrote:
On Jun 12, 2005, at 9:03 AM, Jeremy Higgs wrote:
error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.4" but "10.3"
during configure
make[1]: *** [neo_cgi.so] Error 1
The compile continues, but the file (neo_cgi.so) is not compiled,
and ther
On Jun 12, 2005, at 9:03 AM, Jeremy Higgs wrote:
error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.4" but "10.3"
during configure
make[1]: *** [neo_cgi.so] Error 1
The compile continues, but the file (neo_cgi.so) is not compiled,
and therefore not installed... which is a bit of a problem.
On 13/06/2005, at 0:04, Jeff Whitaker wrote:Jeremy Higgs wrote: Hi everyone,I'm trying to update the trac, silvercity and clearsilver packages to support python 2.4 (as well as trac to the latest version), but I'm having an issue compiling clearsilver on 10.4.1... I get this following:/sw/bin/pyt
Jeremy Higgs wrote:
Hi everyone,
I'm trying to update the trac, silvercity and clearsilver packages to
support python 2.4 (as well as trac to the latest version), but I'm
having an issue compiling clearsilver on 10.4.1... I get this following:
/sw/bin/python2.4 setup.py build_ext --inplac
Hi everyone,
I'm trying to update the trac, silvercity and clearsilver packages to
support python 2.4 (as well as trac to the latest version), but I'm
having an issue compiling clearsilver on 10.4.1... I get this following:
/sw/bin/python2.4 setup.py build_ext --inplace
adding inc_path $(NE
On Thursday, December 12, 2002, at 04:14 PM, David R. Morrison wrote:
I will present a third way of looking at it: if you set this flag at
10.2,
you change the compiled binaries and hence the debs. Do we want to
violate
long-standing Fink policy by doing this without changing
version/revis
I will present a third way of looking at it: if you set this flag at 10.2,
you change the compiled binaries and hence the debs. Do we want to violate
long-standing Fink policy by doing this without changing version/revision
numbers?
-- Dave
---
On Thu, 2002-12-12 at 17:37, Ben Hines wrote:
> I disagree with this, and think that fink should set it to 10.2 for all
> packages. Have you replicated this "theoretical" library breaking
> scenario? Show me.
I think that's the wrong way to look at it. Have you confirmed that
setting it works
On Thursday, December 12, 2002, at 08:23 AM, Benjamin Reed wrote:
On Thu, 2002-12-12 at 11:14, David R. Morrison wrote:
So, the suggested strategy is that we should add an item to the FAQ
which
tells users not to worry if they get the "weak dylibs" warning, and we
should also implement a "Se
On Thu, 2002-12-12 at 11:14, David R. Morrison wrote:
> So, the suggested strategy is that we should add an item to the FAQ which
> tells users not to worry if they get the "weak dylibs" warning, and we
> should also implement a "SetMACOSX_DEPLOYMENT_TARGET" command in Fink so
> that maintainers c
After some discussion on #fink this morning, we arrived at a strategy for
handling the MACOSX_DEPLOYMENT_TARGET environment variable.
Seems that this has been present since the July developer tools, and was
defaulting to 10.1. In the near future, the compiler will start issuing
warnings when this
11 matches
Mail list logo
