Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 May 2014 12:00:01 GMT
From:      Andy Ray <evilkidder@gmail.com>
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   Re: ports/189063: lang/ocaml: Add armv6 support
Message-ID:  <201405011200.s41C01nb015142@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/189063; it has been noted by GNATS.

From: Andy Ray <evilkidder@gmail.com>
To: bug-followup@FreeBSD.org, michipili@gmail.com
Cc:  
Subject: Re: ports/189063: lang/ocaml: Add armv6 support
Date: Thu, 1 May 2014 12:55:10 +0100

 https://bitbucket.org/michipili/ports-bsd/pull-request/1/native-code-compilation-on-armv6-raspberry/diff
 
 Summary;
 
 * create 2 new patch files which modify the ocaml arm backend to support freebsd
 * modify the ocaml configure script patch to detect arm+freebsd an a
 platform appropriate for native code compilation
 * modify the ports Makefile to set correct assembler options for ocaml
 and compile the correct backend
 
 The backend is modified in two files; arm.S and arm/arch.ml.  These
 are both based on using the SYS_freebsd define to select an ARM
 compilation strategy appropriate for freebsd - specifically softvfp
 and the use of EABI.
 
 The configure script does the following;
 
 * detect armv6/frebsd as appropriate for natdynlink
 * set the platform triple armv6*-*-freebsd* to arm/armv6/freebsd which
 enables the native code compiler
 * although it is not used in this build process, also sets the
 autodetected cc+as options (if my upstream ocaml patches are accepted,
 this may be in 4.02)
 
 This patch extends to original patch only and should still be
 appropriate for processing with the post-patch target.
 
 The changes to the ports Makefile are
 
 * The 'as' option passed to 'configure' must include -mfpu and -meabi
 options.  There is now a new conditional section to set up 'as' and it
 has been remove from the initial setup of CONFIGURE_ARGS.
 * ARCH=armv6 is mapped to OCAML_ARCH=arm and the configure script
 allowed to set things up appropriately.
 
 This ARCH mapping is the thing I am least confident of as I am a bit
 unsure of what is going on.  Other targets such as powerpc seem to do
 things differently.
 
 -Andy



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405011200.s41C01nb015142>