This is a port of Bigloo, a Scheme system which includes a
compiler generating C code and Java classes and an interpreter.
Bigloo is the tool of choice for the construction of small
autonomous applications in Scheme. Bigloo is mostly conformant
to the Revised5 Report on the Algorithmic Language Scheme
with many extensions.
PR: ports/40644
Submitted by: Stanislav Grozev <tacho@factline.com>
Coco/R is a recursive decent compiler generator. This is
a FreeBSD port of the C/C++ version of Coco/R.
PR: ports/36251
Submitted by: Guy Antony Halse <guy@rucus.ru.ac.za>
disabling parallel build on sparc64. The INSTALLS_DEPENDS thing
probably comes from bsd.port.mk, but I wonder why it is regarded as a
target when it is only used as a boolean variable. I think make(1)
has some problem with parallel build (-jN) on that platform.
I could not really reproduce the error on panther, but a submitter [1]
says the build went fine if he commented the -jN option out as I
suggested.
Submitted by: Anders Andersson <anders@hack.org>,
Joao Pedras <jpedras@webvolution.net> [1],
kris
Note:
Object files built with version 6.0 of Intel(R) Compilers may not link
properly with objects built with version 7.0 of Intel(R) Compilers.
Rebuilding of the object files is suggested.
Changes between the submitted version and the committed version:
- update to 078 instead of 075
- treat excessive parameters in function calls as an error instead
of a warning (removed compatibility with a not named MS product, as
suggested by Intel)
- allow to override the INTEL_FLEXLM_LICENSE variable
From the submitter:
- Unbreak usage of signal.h on -current and RELENG_5_0.
(committers note: see below)
- Fix ownership of installed files when built as non-root.
- Fix the patched versions of the icc- and the icpc-script to work with options
containing spaces (e.g. '-DFOOBAR="foo bar"').
- Install 'clicense' and 'csupport' in the docs-dir even if NOPORTDOCS is
defined, the later is not optional but required by 'icid'.
- Move the ld-wrapper to a sub-dir and thus out of what is normally set in
PATH to prevent footshooting (this isn't perfect but simple until someone
reworks this port to provide FreeBSD-compatibility in another way... or
Intel releases a native version).
- Patch the headers to better fit for FreeBSD (hopefully...).
Notes: - Icc7 is more picky about unknow options than the previous versions,
i.e. the gcc-options normally supplied in CFLAGS unless altered in
/etc/make.conf. Therefore compilation of ports with icc likely fail
if the standard CFLAGS are not unset (e.g. `make CC=icc CFLAGS=""`)
or replaced by options valid for icc.
- When compiling multi-threaded C-code make sure to link with icc and
option '-mt' (for ports e.g. via PTHREAD_CFLAGS) otherwise libc_r
won't be linked in correctly.
Submitted by: marius@alchemy.franken.de
Additional information:
- rev 1.20 of src/sys/i386/include/signal.h introduced __aligned which
isn't handled in sys/cdefs.h for non GCC compilers (at least not in
publically available sources)
- the FreeBSD stdarg.h is missing a macro for va_copy() in the non GCC case,
we handle it in the port, but be prepared to get problems when the base
system gets fixed
- we don't use the icc-buildin of alignof()
- Intel provides a float.h which has different floatingpoint values
(e.g. MAX_FLOAT) than we have in the base system, in the port we use the
FreeBSD header (Warner knows about the issue... at least he got a mail
from me and Marius)
- we replace __wchar_t with __ct_rune_t because icc has a build-in type
for it, this affects "typedef __ct_rune_t __wchar_t;" in sys/_types.h.
It isn't known if this may be evil...
- icc doesn't need the option "-mt" anymore to generate thread safe code,
but our FreeBSD version still needs it to be able to choose libc_r
instead of libc
If a src-committer wants to address any of the above mentioned issues he
should first contact me, I may have already some fixes in my local tree.
which now supports FreeBSD/sparc64.
Set ONLY_FOR_ARCHS to i386, alpha and sparc64. Ruby does not support
IA64 yet. It does not even build or install correctly. We need some
clue to the IA64 stack structure and handling of the IA64 register
windows.
Ruby does not support IA64 yet. It does not even build or install
correctly. We need some clue to the IA64 stack structure and handling
of the IA64 register windows.
