${PTHREAD_CFLAGS} and ${PTHREAD_LIBS} include in the build to kill the
headache of old '_r' and can't run with something like ruby-opengl, ruby-sdl,
ruby-gtk2 and etc on FreeBSD 4.x or older 5.x. With this commit should solve
those issues. It is recommend you to rebuild any apps that depend on
lang/ruby18, so see the UPDATING for detail.
Remove the 'BROKEN' on the other ports that knu has added them few weeks ago.
Some of them have been tested, so if one of them is still broke then please
let us know and one of us will re-add the 'BROKEN'.
This changes was worked by lofi and me. lofi did everything on FreeBSD 4.x
and I did others. lofi, thanks for help!
Tested by: many people
Tested on: i386 (FreeBSD 4.x, 5.x and 6.x), amd64 (FreeBSD 5.x and 6.x),
and sparc64 (FreeBSD 5.x and 6.x)
Not test on: ia64 and alpha
Approved by: portmgr (kris)
the features that people like so much in languages like Python, Ruby and
Smalltalk, making them available to Java developers using a Java-like syntax.
Groovy is designed to help you get things done on the Java 2 Platform in a
quick, concise and fun way. Groovy brings the power of a scripting language
directly into the Java 2 Platform. For example:
- Shell scripting using Groovy allows the full power of the Java Platform to be
brought to bear to the task at hand.
- Groovy can be used (and indeed is already being used) as a replacement for
Java for small and medium sized applications to execute on the Java 2
Platform.
- Groovy can be used as an embedded language for dynamic business rules or
extension points utilizing the agility of Groovy and saving the cost of
redeploying applications for each change of rule (especially when the rules
are stored in a database).
- Groovy makes writing test cases for unit tests very easy.
As well as being a powerful language for scripting Java objects, Groovy can be
used as an alternative compiler to javac to generate standard Java bytecode to
be used by any Java project.
WWW: http://groovy.codehaus.org/
It's worth pointing out that the Tcl project used to
*recommend* that application writers copy this kludge.
These ports work fine with Tcl 8.3, which provided a fake
matherr() even if the OS didn't, but here's what the
Tcl 8.4 changelog has to say:
2002-05-31 (dead code)[474335,555635] removed all use of matherr() (english)
*** POTENTIAL INCOMPATIBILITY ***
The following lines can be safely removed from any application that
has them, unless compatibility with SunOS 4.X is desired.
extern int matherr();
int *tclDummyMathPtr = (int *) matherr;
The build problems were pointed out by Kris, as usual. ;-)
inspection of src/contrib/gnu/crtstuff.c it seems it's the same as
crtbegin.o, so make a symlink for it. At least linking a "Hello World"
program with -static produces a working executable now.
Noticed by: Niklas Sorensson <nik@cs.chalmers.se>
- Install in DATADIR=${JAVASHAREDIR}/${PORTNAME}
- Use %%DATADIR%%
- Add $FreeBSD$ tags
- Tweak COMMENT to calm portlint (and remove redundant port name from it)
- Improve launcher shell script (update to javavmwrapper 2.0) and use SUB_FILES
- Minor cosmetic improvements
environment (like da_DK.ISO_8859-15 as opposed to da_DK.ISO8859-15 on
-CURRENT), perl ports cannot be built. While this condition clearly is
an operator error, it is still no excuse for the build failure.
Fix that by cleaning locale-related variables for configure and build
steps. No plist changes, no portrevision bump.
Reported by: Flemming Jacobsen <fj quite-at batmule maybe-dot dk>
