Age | Commit message (Collapse) | Author | Files | Lines |
|
Reported by ASau.
|
|
Previously, a non-existing directory in REPLACE_RUBY_DIRS stopped the build
on Solaris.
|
|
Previously, it altered lines that did not start with "#!". This, with
the recent change in misc/rubygems/rubygems 1.39, broke www/rails.
|
|
|
|
Don't leak tmp_dir in pear.conf
Should also fix builk builds (pointed out by joerg@)
Remove evil pear.conf handling
PKGREVISION++
|
|
|
|
Bump PKGREVISION.
|
|
(http://www.ruby-lang.org/en/news/2008/08/23/dos-vulnerability-in-rexml/)
from ruby_1_8 branch.
Bump PKGREVISION.
|
|
compile the sunaudiodev module.
* PLIST fix for SunOS
|
|
compile the sunaudiodev module.
|
|
|
|
|
|
set it to ${DISTNAME}.
|
|
|
|
version and the src version of nawk differ in that. Complained about by
Joachim Koenig, blame on me. Bump revision.
|
|
(I tried patching it for amd64 yesterday; it chunks along for a good
while and then drops into its debugger. So it's important that
ONLY_FOR_PLATFORM be set conservatively.)
|
|
Bugfix release.
|
|
|
|
|
|
JamVM 1.5.1 released on 10th March 2008
=======================================
A summary of changes since 1.5.0:
- Implemented a new internal VM symbol framework. This ensures that
all class, method, field names, etc. are unique thus removing the
need to use strcmp for comparison.
- Implemented a new internal VM exception mechanism for frequent
exceptions thrown within the VM.
- Hand-coded support for AMD64 ABI. Previously AMD64 required libffi
but this is not individually packaged on some Linux distributions.
On a random set of signatures the hand-coded assembler is 4.6 times
faster (and jBYTEmark FP Index is 30% faster).
- Ported to Darwin/ARM (i.e. the iPhone). Built using unofficial
toolchain and tested on jailbroken iPhone (1.1.3 firmware)
- Class initialisation/first active use fixes
- initialise if first active use is object allocation via reflection
(newInstance)
- initialise if first active use is object allocation via JNI
(AllocObject/NewObject)
- The wait in step 2 of the initialisation sequence must be
non-interruptible (not specified in the JVM or Java spec).
- If allocation of the ExceptionInInitializerError fails,
OutOfMemoryError should be thrown not the original exception
- Don't resolve if initialiser throws ExceptionInInitializerError
(subsequent resolution will not see the class is erroneous)
- JNI_OnLoad fixes
- initialise JNI local refs before calling
- if JNI_FindClass is called from JNI_OnLoad, ensure correct class
loader context is used.
- JNI_OnUnload fixes
- initialise JNI local refs before calling
- If a library defines JNI_OnUnload, and the class loader which
loaded it is GCed JNI_OnUnload is called and the library is
unloaded. Previously this was done within the GC. If OnUnload
allocated objects it could corrupt the heap. Dummy unloader
objects are now created, and JNI_OnUnload is called from the
finalize method by the finalizer thread.
- Fix variable argument passing of floats When calling Java methods from
native code
- Rework VM initialisation/start-up sequence
- Fix for JNI_ThrowNew and exceptions loaded by non-bootstrap classloader
- Fix for JNI_GetMethodID and object/class initialiser methods
(do not search class hierarchy)
- During resolution throw IllegalAccessError and not IllegalAccessException
- handle loadClass returning null without throwing exception
- Fix for running Jar files where the main class is package-protected
- Interpeter inlining changes
- Do not inline class initialisers (<clinit>). No performance
improvement as they are only ran once. Reduces memory usage
- Fix for class unloading when inlining disabled (-Xnoinlining)
- Bump java.specification.version to 1.5
- Improve error messages if VM aborts during initialisation
- During configure, do not disable zip/jar file support if zlib library
or header can't be found (now aborts). Users never saw the warning
and they ended up with a build which "didn't work".
- Various compiler warnings.
JamVM 1.5.0 released on 28th October 2007
=========================================
A summary of changes since 1.4.5:
- Substantially modified the interpreter to implement inline-threading
(also known as super-instructions or code-copying). This copies
code sequences together to produce native code that executes without
the normal interpreter dispatch overhead (similar to a simple JIT).
- Supported on i386, AMD64, PowerPC and ARM, with or without stack-
caching. It is enabled by default on i386, AMD64 and PowerPC.
- Performance improvement upto 300% on Pentium 4 (NetBurst), and upto
200% on Athlon 64. Less on Core 2 Duo (upto 70% faster as it has
indirect branch prediction), and PowerPC which was already very
optimised (upto 30% faster).
- Tested on gcc 3.4 (i386, AMD64, PowerPC), 4.0 (i386), 4.1
(i386, AMD64, PowerPC, ARM), 4.2 (i386, AMD64)
- Several new command line options to control inlining:
-Xreplication : determines whether duplicate code sequences
are replicated or shared. Can be set to 'none' (no replication),
'always' (all sequences are copies) or a threshold value (e.g.
10, when sharing of a sequence reaches the threshold the sequence
is replicated).
-Xcodemem : the maximum amount of memory for super-instructions.
Once the maximum is reached no new super-instructions are generated
but existing super-instructions are reused (class unloading will
also free unused sequences). Can be set to a value or 'unlimited'.
This option can be used to limit code memory on systems with little
RAM (i.e. embedded).
-Xshowreloc : debugging option, which shows which opcodes were
determined to be relocatable, and for opcodes which aren't why
they aren't relocatable. When using stack-caching there are
three versions of each opcode (for 3 stack-cache levels).
-Xnoinlining : turns off inlining (equivalent to setting codemem
to zero).
- Opcode relocatability is determined by default at build time, but
this doesn't work when cross-compiling (so inlining is disabled).
Relocatability can be determined at runtime using configure option
--enable-runtime-reloc-checks, but this increases executable size
by approx 30%.
- Command line options -version and -showversion now shows build
information. This includes the execution engine (e.g. inline-
threaded interpreter with stack-caching), the gcc version which
was used to compile JamVM (useful for debugging) and the "built in"
boot library path and classpath.
- Ported to ARM systems using EABI. This is a full port, with hand-
coded assembler to handle the construction of a call-frame for calling
JNI native methods.
- Refactored GC to remove all possible calls which may deadlock
with threads suspended in "unsafe" operations. This includes
use of malloc/realloc/free and pthreads operations.
- In allocClass() check if gcMalloc() returns NULL (i.e. OOM).
- Copy Sun's behaviour when dealing with an empty property key or no
equals after key.
- Add java.util.concurrent.atomic.AtomicLong.VMSupportsCS8.
- In method and field access checks, put back in access check for
class (removed previously because it caused regressions, since
fixed in Classpath).
- Enable suspend on thread creation (parent thread created thread with
suspension disabled). Effects threads which immediately call a long
running native method.
- Fixed race condition in thread creation and compaction (start function
obtains class reference when it is not suspendable, if compaction
occurs, the reference may be threaded, or moved).
- Fix potential deadlock in threadInterrupt under Linuxthreads.
- Protect lock operation in resetPeakThreadsCount().
- In createJavaThread(), re-enable suspension if pthread_create fails.
- Fix race-condition in thread deletion.
- Fix bug in hash table "scavenge". This could lead to entries not being
freed, and exhaustion of Monitors on embedded systems.
- Removed use of malloc/free in thread dump. Removes potential deadlock
with threads suspended in malloc/realloc/free.
- Added symbolic link from lib/rt.jar to Classpath's glibj.zip (fixes
programs such as ecj which locates rt.jar via java.home).
- Bumped Java compatible version to 1.5.0 as Classpath is now the generics
branch (since Classpath 0.95).
|
|
suggestion of bjs@.
|
|
library, and it might build for i386, although x86_64 is still pretty
broken.
|
|
|
|
happens by default on amd64, the build will fail instead of silently
skipping it.
|
|
broken to test fully, so I've left PKG_DESTDIR_SUPPORT commented out.
|
|
|
|
works consistently. Should fix broken bulk builds.
Update PLIST accordingly && PKGREVISION++.
|
|
|
|
|
|
While here, patch a couple 64-bit issues and add destdir support. The
latter involved making some absolute symlinks relative, which changes
the binary package, and someone might have built this revision with a
version of bash accepting the invalid script syntax, so PKGREVISION++.
|
|
thoroughly 32-bit only.
It *might* work if someone rebuilt the boostrap files with a suitable
Scheme compiler capable of generating 64-bit-clean C code. But someone
who knows Scheme better than I do will have to figure that out.
|
|
|
|
are a lot of woolly things going on here, so PKGREVISION++ as a
precaution.
|
|
PKGREVISION++, because I changed some things around.
|
|
|
|
|
|
"HTTP header injection" attacks
|
|
|
|
Noticed by Aleksej Saushev in PR 39403.
|
|
CVE-2008-3144 (this one shouldn't affect platforms supported by pkgsrc)
all taken from Gentoo. Bump package revision.
|
|
patch with a more tolerant version of patch (like netbsd's) gives two
copies of the definitions in the same file, with who knows what
consequences. Applying the patch with a less tolerant version of patch
fails.
So, remove it, and bump PKGREVISION just in case.
|
|
Submitted by Aleksej Saushev in PR pkg/39406.
|
|
than once. Bump revision again.
|
|
Bump revision.
|
|
|
|
DESTDIR support
Fix unbalanced ' in configure.
|
|
|
|
Reported by Aleksej Saushev.
|
|
packages.
|
|
which makes integration with PEAR a little simpler.
PKGREVISION++
|