[Mono-devel-list] [LONG] Any Interest in FreeBSD Patches? Then see attached.

[Dick Porter]

On Fri, 2004-07-16 at 20:47, John Merryweather Cooper wrote:
> I'm the FreeBSD maintainer for mono and I've finally gotten a
> reasonable, working mono on FreeBSD (at least on -CURRENT, FreeBSD
> 5.2).  In the hopes that some of this might get integrated into the next
> release (and make my job a little easier), I've attached the patches
> necessary to get Mono 1.0 working.  All of these patches can be had via
> cvsweb at:

Thanks for this.

> # extra-patch-signbit  ONLY NEEDED FOR FREEBSD 4.x

This one will have to wait for Paolo to get back.

> # patch-configure
> #####
> 
> The build environment in the FreeBSD Ports system defines two
> environment variables:  PTHREAD_CFLAGS and PTHREAD_LIBS.  The contents
> of these two environments vary depending on the FreeBSD version,

How does this patch impact FreeBSD builders of the tarball?  I'm
assuming PTHREAD_CFLAGS and PTHREAD_LIBS won't be set automatically for
them.  Is it possible to have a set of probably-correct defaults, and
let the ports build override them?

> # patch-ligbc_Makefile.in
> # patch-ligbc_configure
> # patch-libgc_dbg_mlc.c
> # patch-libgc_dyn_load.c
> # patch-libgc_include_private_gcconfig.h
> # patch-libgc_ltmain.sh
> # patch-libgc_os_dep.c
> # patch-libgc_threadlibs.c

These patches should be fed upstream to the libgc people, see
http://www.hpl.hp.com/personal/Hans_Boehm/gc for their site.  The
mailing list info is at the bottom of that page.  We update to new
versions of libgc fairly often.

> # patch-ltmain.sh

ltmain is a generated file (from libtool.)

> # patch-mono_Makefile.in

Again, Makefile.in is a generated file, built from Makefile.am.  There
is no tests directory specified in Makefile.am.


- Dick