Suspending multithreaded programs built with ghc (including ghc
itself) should just work[tm] now. (Except for the bootstrapping
compiler which of course still uses the old code)
- fix conflict with speech-dispatcher
- fix gen-versions target
- i386 ethread compat
update to R14B04 from dlg@, rest by piotr sikora and me
tested with rabbitmq and ejabberd on amd64; sparc64 is still happy too
maintainer timed-out
Also include the compiler standard libraries under compiler-libs/, as this
is the convention adopted by other packaging (Debian, FreeBSD), and is used
by various utility software such as the Lwt interactive toplevel and some
of the graphical IDEs.
CoffeeScript is a little language that compiles into JavaScript.
Underneath all those awkward braces and semicolons, JavaScript has
always had a gorgeous object model at its heart. CoffeeScript is an
attempt to expose the good parts of JavaScript in a simple way.
The golden rule of CoffeeScript is: "It's just JavaScript". The code
compiles one-to-one into the equivalent JS, and there is no
interpretation at runtime. You can use any existing JavaScript library
seamlessly from CoffeeScript (and vice-versa). The compiled output is
readable and pretty-printed, passes through JavaScript Lint without
warnings, will work in every JavaScript implementation, and tends to run
as fast or faster than the equivalent handwritten JavaScript.
Feedback and OK jasper@
without any modifications to PATH. To run an ruby program that is
installed in jruby's bin directory (which no longer needs to be in the
PATH), use jruby -S program.
I don't know why it doesn't find it, but it looks like the tmp inst
is supposed to get it...
so work around until eventually robert fixes this mess for real...
builtins.c:
Allow MD backend to prevent the optimization of a bcopy() or memmove() of
size 1 (the size being known at compile-time) into an inline mempcpy()
expansion, which will in turn expand into a byte load and store operation.
This expansion loses precious address alignment information at some point
(because everybody knows that you can read a byte from any address, right?),
and this loses bigtime on strict alignment platforms which lack the ability
to accesse bytes directly, such as alpha (unless compiling with -mbwx and
runnning on a BWX-capable cpu).
config/alpha:
Require alignment of local arrays on word boundaries, and enable
the builtins.c `one-byte memcpy' workaround.
ok espie@
is not set, but only for gem, extconf, and setup based ports. Other
ports could be using the lang/ruby module and still have a standard
make-based regression test suite.
anywhere else. The only thing not supported yet is tracing using ptrace(2).
- clean up Makefile and restructure a bit
- VMEM_WARNING when -java is built
- some minor PLIST tweaks
ok espie@
rspec 1 using rspec and rspec 2 using rspec2. Additionally, add
support for ruby and testrb, calling the appropriate binary for the
ruby implementation.
Start checking sanity of MODRUBY_REGRESS entry, using a fatal error
if it is defined and doesn't contain a recognized word.
Instead of RAKE_REGRESS_TARGET and RSPEC_REGRESS_TARGET, just use
MODRUBY_REGRESS_TARGET for all cases. On ruby 1.9, modifying the
environment to always look in the current directory for libraries
(the ruby 1.8 behavior), since many ports depend on that for regress.
Allow ports to set their own regress environment and current directory
using MODRUBY_REGRESS_ENV and MODRUBY_REGRESS_DIR.
which should allow building on arches without enough memory to
generate the ri files. Also, set PKG_ARCH=* for the ri_docs
subpackage, so that such arches can still use the documentation,
idea from sthen@. Original idea for PSUEDO_FLAVOR from phessler@.
OK sthen@
The spec task requires network access via git, which is not allowed.
Since git isn't needed anymore for regress, remove it from
REGRESS_DEPENDS. The spec task is just commented out in case somone
wants to run it manually.
Set JAVA_HOME and PATH and disable forking so java doesn't crash when
running the test and spec tasks. Don't install the jruby-launcher gem
when running the test and spec tasks, as it fails.
Regress depend on git when running the specs, as it needs to download
current rubyspecs for the spec task.
Delete the jruby-complete.jar file and just use the jruby.jar file
when running the specs, as otherwise you get additional test failures
and warnings.
Switch to SUBST_CMD while here now that has been fixed. Also, bump
the memory limits by 50M as 384M doesn't seem to be enough in all
cases.
Verilator is the fastest free Verilog HDL simulator, and beats most
commercial simulators. It compiles synthesizable Verilog (not test-bench
code!), plus some PSL, SystemVerilog and Synthesis assertions into C++
or SystemC code. It is designed for large projects where fast simulation
performance is of primary concern, and is especially well suited to
generate executable models of CPUs for embedded software design teams.
ok aja@
upstream decided to move to separate modules instead
of one monolithic jar file. packaging all these standalone modules is not going
to work, so please use devel/leiningen instead to fetch individual modules.
that no longer create .require_paths files. No RUN_DEPENDS
are being added as older ruby versions can use gems without
.require_paths files (we never had a ruby 1.9.1 package).
This is being done to avoid errors by porters who are creating/updating
gem ports without installing new ruby versions.
Make jruby binary not segfault if PATH isn't set correctly.
Remove rubygems hacks, since they are no longer necessary now
that the versions of rubygems for the other ruby interpreters
are > 1.3.7.
No longer ship the ri documentation files with JRuby. JRuby
ships with a broken ri binary anyway (requires the rdoc gem to
work), and almost all users of JRuby have MRI ruby installed
and can use its ri binary.
Make jruby binary not segfault if PATH isn't set correctly.
Remove rubygems hacks, since they are no longer necessary now
that the versions of rubygems for the other ruby interpreters
are > 1.3.7.
No longer ship the ri documentation files with JRuby. JRuby
ships with a broken ri binary anyway (requires the rdoc gem to
work), and almost all users of JRuby have MRI ruby installed
and can use its ri binary.
a few new features. A few of our patches were accepted upstream.
Add an -ri_docs multipackage to hold the ri documentation files. These
aren't used very often, slow down installation significantly, and bloat
the package.
This also fixes the conflict marker for the -tk multipackage.
