Re: (patch) Adds a note about installing on FreeBSD

[Mats Bengtsson]

It seems that the FreeBSD "port" of Lilypond is simply a link to
the ordinary 1.6.0 tarball.
I couldn't find the macro USE_PYTHON anywhere in any file of
that version either, so I doubt that the solution you describe
actually solves any problem.

I also tried to search the mailing lists for freeBSD problems and
the only relevant question I could find were related to that
the python.h wasn't installed in a directory where gcc searches
by default. The workaround for such a situation is already mentioned
in INSTALL.txt (though it was not explicitly mentioned as a freeBSD
problem until after version 1.6.0).

For the record: the problem I refer to above and the corresponding
solution is described in
http://mail.gnu.org/archive/html/lilypond-user/2002-01/msg00032.html

If the actual problem is something else, please come back to the
mailing list.

The freeBSD related problems we have seen more recently on the
list have all been related to the incompatibility between
gcc 3.x and certain flex versions and is already well described
in INSTALL.txt.

   /Mats

Graham Percival wrote:
> On Fri, 23 May 2003 14:29:17 +0200
> Mats Bengtsson <address@hidden> wrote:
>
> > Isn't it better to actually help configure find Python?
> >
> > As far as I can see, USE_PYTHON isn't used anywhere in
> > Lilypond (at least not in version 1.7.18). What problem
> > does your instruction solve and what version is it relevant
> > for?
>
>
> Here's the information I received, from somebody who uses FreeBSD:
> -----
>   Well, if you ever get the newbie question "how do I get it to install
> on FreeBSD", here's the answer: The port doesn't properly check for the
> existance of Python, so you need to `make USE_PYTHON=yes all install`.
> -----
>
> Judging from the FreeBSD website, it appears that the version of
> Lilypond in their ports collection is 1.6.0.  I'm not familiar with the
> FreeBSD Ports collection, so I don't know if they simply use Lilypond's
> configure or whether there's an extra freebsd-specific dependency
> check.  This problem could have been caused from improper porting of
> Python.
>
> In case it isn't clear, this error occurs when using the FreeBSD port
> collection, not when compiling/installing Lilypond directly from source.
> As I said originally, this information might not be worth putting into
> INSTALL.txt, but I thought that including the information woudn't hurt.
>
> I don't know anything else about this matter, but I could forward any
> other questions to him.  Should I re-write the INSTALL.txt entry to be
> more clear than I'm talking about the FreeBSD Port, rather than actual
> Lilypond source?  Or is it not worth including at all?
>
>
> > Graham Percival wrote:
> >
> > > My brother reported difficulty installing Lilypond onto his FreeBSD
> > > system; here's how he solved it.  Since the trouble was in the
> > > FreeBSD port (rather than the actual Lilypond source) I wasn't
> > > certain if you wanted to bother putting it in INSTALL.txt, but I
> > > figured "better save than sorry".

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================