Simply copying the 1.1.10 ebuild to 1.11 works. Tested on ppc, should work on others. Note: Version numbering scheme changed from x.y.z to x.y upstream, 1.11 is the next version after 1.1.10 :)
Note: There has just been a minor bug fix release: 1.11.1 I will test it later.
Just to confirm that 1.11.1 works fine on ~ppc, should fine on others too. cp sablevm-{1.1.10,1.11.1}.ebuild
i get two access violations: first one during configure: ------------------------------------ ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib --with-jikes --enable-gtk-peer configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. ACCESS DENIED mkdir: /root/.subversion svn: '.' is not a working copy checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-pc-linux-gnu second one during install: ------------------------------------ make[3]: Entering directory `/var/tmp/portage/sablevm-1.11.1/work/sablevm-1.11.1/src' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/var/tmp/portage/sablevm-1.11.1/work/sablevm-1.11.1/src' make[2]: Leaving directory `/var/tmp/portage/sablevm-1.11.1/work/sablevm-1.11.1/src' make[2]: Entering directory `/var/tmp/portage/sablevm-1.11.1/work/sablevm-1.11.1' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/var/tmp/portage/sablevm-1.11.1/work/sablevm-1.11.1' make[1]: Leaving directory `/var/tmp/portage/sablevm-1.11.1/work/sablevm-1.11.1' --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-dev-java_-_sablevm-1.11.1-12464.log" mkdir: /root/.subversion mkdir: /root/.subversion --------------------------------------------------------------------------------
ok. I did not get it in the first place since /root/.subversion existed on my system. I will discuss with other SableVM devs. Seems that svn is executed in a "safety check" and it probably should not be there in final releases...
This ebuild and associated files for FILESDIR patches configure.ac to fix the violation and regenerated configure and associated files. See attachment.
Created attachment 54260 [details] suggested ebuild
Created attachment 54261 [details, diff] sablevm configure.ac patch
Created attachment 54262 [details, diff] sablevm-classpath configure.ac patch
Created attachment 54263 [details] sablevm autogen
Created attachment 54264 [details] sablevm-classpath autogen
to avoid heavy patching, we should maybe wait for a new imho. by doing this we can keep the amount of files in the tree as small as possible. have you send your patches upstream, or does the project now about this issue?
Releases used to be far apart so I was not sure but the two core devs that make the releases have just done a 1.11.3 release with my sandbox bug fix as well as several other fixes. To summarize, simply copying the 1.1.10 release to 1.11.3 should work. I tested it on ~ppc but should work fine on other archs.
ok, thanks again for your effort. version bumped, in cvs.
