Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
On Wednesday 27 September 2006 10:21 am, Chris Monson wrote:
> On 9/27/06, Ethan Merritt <merritt@...> wrote:
> > On Wednesday 27 September 2006 09:43 am, Daniel J Sebald wrote:
> > > I'd say this needs to be addressed before 4.2 release.
> > Nah. This is just one more oddity that an OSX packager would
> > have to sort out when building a binary distribution. Once the
> > user is up and running there is no problem at all.
> Is the fink distribution the proper place for this issue, then?
I'm going to have to throw up my hands at this point.
I'm not a Mac person, and I don't know who/where to send such
a report. From the various reports on this thread it seems that
the problem is present only on some Macs, or only some versions
of OSX, or I don't know what-all variant installed libraries.
If somebody associated with fink, or Darwin, or some other
OSX developers resource can provide a definitive answer then
fine. But I fear if we were to blindly 'fix' the build process
to work on Chris's machine, we would risk breaking it on other
The safest immediate solution may be to provide an entry under
"Known Problems" somewhere in the installation docs, warning
would-be OSX packagers to check that gamma works, and tell them
to force gnuplot to use its built-in gamma function if the build
process fails to find an appropriate gamma function from the
Longer term, the documentation of tgamma() suggests that if it
is present at all on any system, then it can safely be used.
But I don't want to make such a change prior to 4.2
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle WA