Update lang/fsharp to 1.9.6.2
Gabor PALI
Recently I started to use the F# programming language, and I found you
have already ported it to FreeBSD. However, it is a very old port, so
I created a patch to update it to version 1.9.6.2 (2008 September
CTP). I think I will track this software in the future, since I use
it day by day.
Because the changes to this port are so huge, I created a standalone
shar file and a patch to the latest version in the SVN repository (so
you can pick any of them):
http://people.freebsd.org/~pgj/patches/2009/01/17/fsharp.shar
http://people.freebsd.org/~pgj/patches/2009/01/17/fsharp.patch.diff
I have tested it on Tinderbox 3.1.2, but because of problems with the
lang/mono port, I only managed to tinderbuild it on 7.x-STABLE. It
works well for me (but please, note that it requires lang/mono>=2).
Any comment, suggestion, reply is welcome.
Cheers,
:g
Gabor PALI (pgj@freebsd.org)
(Sorry if you receive this email more than once.)
Phillip Neumann
El Jan 17, 2009, a las 6:07 PM, Gabor PALI (p...@freebsd.org) escribió:
>
> Hello,
>
> (Sorry if you receive this email more than once.)
Hi Gabor,
Sorry ive been very busy lately, havent had the chance to keep the
"queued mails" updated.
>
>
> Recently I started to use the F# programming language, and I found you
> have already ported it to FreeBSD. However, it is a very old port, so
> I created a patch to update it to version 1.9.6.2 (2008 September
> CTP). I think I will track this software in the future, since I use
> it day by day.
Greate!.
>
>
> Because the changes to this port are so huge, I created a standalone
> shar file and a patch to the latest version in the SVN repository (so
> you can pick any of them):
>
> http://people.freebsd.org/~pgj/patches/2009/01/17/fsharp.shar
> http://people.freebsd.org/~pgj/patches/2009/01/17/fsharp.patch.diff
>
> I have tested it on Tinderbox 3.1.2, but because of problems with the
> lang/mono port, I only managed to tinderbuild it on 7.x-STABLE. It
> works well for me (but please, note that it requires lang/mono>=2).
>
I didnt saw the update jet, but you mean problems running mono on
CURRENT?
> Any comment, suggestion, reply is welcome.
>
>
How do you want to keep it updated? You think its better to just put
the port in the FreeBSD ports tree and keep it there? or want to work
with the bsd# repo?
After wxs@ do the merge, the idea is to push new ports to the oficial
tree, we could include f-sharp.. :)
Thanks!
> Cheers,
>
Gabor PALI
On Sun, Jan 18, 2009 at 5:44 PM, Phillip Neumann <pneu...@gmail.com> wrote:
> Sorry ive been very busy lately, havent had the chance to keep the
> "queued mails" updated.
No problem :P
> I didnt saw the update jet, but you mean problems running mono on
> CURRENT?
I tried to tinderbuild lang/fsharp in 6-STABLE and 8-CURRENT jails,
and the build stuck at the compilation of the lang/mono port (I
included the error logs, if you are interested in them [1][2] -- I do
not say it is your problem, maybe the tinderbox should be tuned in
some way; the logs show almost the same error).
I am using this port on a 7.1-RELEASE (previously on a 7.1-PRERELEASE)
system, and it works fine.
> How do you want to keep it updated? You think its better to just put
> the port in the FreeBSD ports tree and keep it there? or want to work
> with the bsd# repo?
I would put there where it gets more attention. I am a doc committer
in the FreeBSD Project, so (with a little help of a porter) I can
commit directly to the ports tree (as I did before). There are about
two releases for F# per year (at most), so maintenance of this port
would consist of sending about two patches per year :)
> After wxs@ do the merge, the idea is to push new ports to the oficial
> tree, we could include f-sharp.. :)
The only requirement is to have support for mono 2.x, because it is
mandatory for F# 1.9.6.2. At the moment, mono 1.2.5.1 is included in
the official tree [3].
> Thanks!
You are welcome. I am also happy that I do not have to use Windows
just because F# :)
:g
[1] http://people.freebsd.org/~pgj/patches/2009/01/17/tb-6/mono-2.2_1.log
[2] http://people.freebsd.org/~pgj/patches/2009/01/17/tb-8/mono-2.2_1.log
[3] http://www.freshports.org/lang/mono/
Romain Tartière
On Sun, Jan 18, 2009 at 08:01:29PM +0100, Gabor PALI wrote:
> > I didnt saw the update jet, but you mean problems running mono on
> > CURRENT?
>
> I tried to tinderbuild lang/fsharp in 6-STABLE and 8-CURRENT jails,
> and the build stuck at the compilation of the lang/mono port (I
> included the error logs, if you are interested in them [1][2] -- I do
> not say it is your problem, maybe the tinderbox should be tuned in
> some way; the logs show almost the same error).
>
> I am using this port on a 7.1-RELEASE (previously on a 7.1-PRERELEASE)
> system, and it works fine.
Only have 7.x here... Looking at your log, gcc complains about
undeclared constants (NGROUPS, MAXLOGNAME, MAXCOMLEN) which are all
defined in sys/param.h...
Maybe the fix is as trivial as adding this header... Or find why it is
not included under some circumstances. I'll try to give this a look
tomorrow.
> > How do you want to keep it updated? You think its better to just put
> > the port in the FreeBSD ports tree and keep it there? or want to work
> > with the bsd# repo?
>
> I would put there where it gets more attention. I am a doc committer
> in the FreeBSD Project, so (with a little help of a porter) I can
> commit directly to the ports tree (as I did before). There are about
> two releases for F# per year (at most), so maintenance of this port
> would consist of sending about two patches per year :)
Working on this port within the framework of the BSD# project would mean
that we would not send updates of mono that would break down F#: before
starting to update mono and mono-based tools (PR being proceeded right
now) we spend a large amount of time checking all the ports we want to
provide actually work as expected.
It is however not mandatory to do so: "important" mono-based ports that
we do not maintain (e.g. banshee) are imported into the BSD# tree to
check that they work as expected with recent versions of mono, but we do
not take control over them. If we find a problem, we will mail you about
it to find a solution.
> > After wxs@ do the merge, the idea is to push new ports to the oficial
> > tree, we could include f-sharp.. :)
>
> The only requirement is to have support for mono 2.x, because it is
> mandatory for F# 1.9.6.2. At the moment, mono 1.2.5.1 is included in
> the official tree [3].
You can track ports/129724 to get the update status:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/129724
Kind regards,
Romain
--
Romain Tartière <rom...@blogreen.org> http://romain.blogreen.org/
pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)
Gabor PALI
On Sun, Jan 18, 2009 at 10:32 PM, Romain Tartière <rom...@blogreen.org> wrote:
[..]
> Working on this port within the framework of the BSD# project would mean
> that we would not send updates of mono that would break down F#: before
> starting to update mono and mono-based tools (PR being proceeded right
> now) we spend a large amount of time checking all the ports we want to
> provide actually work as expected.
Thank you for being so careful. It would be good to have lang/fsharp
in the official tree. With my colleagues I am working on a software
based on this language and it will be released as open source soon. I
would like to create a FreeBSD port for this software then, so it
might receive more attention.
> It is however not mandatory to do so: "important" mono-based ports that
> we do not maintain (e.g. banshee) are imported into the BSD# tree to
> check that they work as expected with recent versions of mono, but we do
> not take control over them. If we find a problem, we will mail you about
> it to find a solution.
Hm, I like this suggestion. I think after mono 2.x hits the official
tree, I could add the updated lang/fsharp port too. Should I take
(over) the maintainership of this port?
[..]
> You can track ports/129724 to get the update status:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/129724
Thanks for your great work!
:g
Romain Tartière
On Sun, Jan 18, 2009 at 10:32:09PM +0100, Romain Tartière wrote:
> On Sun, Jan 18, 2009 at 08:01:29PM +0100, Gabor PALI wrote:
> > I tried to tinderbuild lang/fsharp in 6-STABLE and 8-CURRENT jails,
> > and the build stuck at the compilation of the lang/mono port (I
> > included the error logs, if you are interested in them [1][2] -- I do
> > not say it is your problem, maybe the tinderbox should be tuned in
> > some way; the logs show almost the same error).
> >
> > I am using this port on a 7.1-RELEASE (previously on a 7.1-PRERELEASE)
> > system, and it works fine.
> Only have 7.x here... Looking at your log, gcc complains about
> undeclared constants (NGROUPS, MAXLOGNAME, MAXCOMLEN) which are all
> defined in sys/param.h...
>
> Maybe the fix is as trivial as adding this header... Or find why it is
> not included under some circumstances. I'll try to give this a look
> tomorrow.
Forgot to tell I can't reproduce the problem with FreeBSD-8.0-CURRENT:
mono-2.0.1 compiles without any problem. Can you please update your src
and retry?
Regards,