Re: gentoo ebuild question

"Kevin S. Clarke" <[email protected]>
Newsgroups gmane.comp.java.vm.sablevm.general
Message-ID <[email protected]>
Hi David,

Thanks for your response.

"automake --version" reported 1.8.5; also, "emerge -s automake" showed
that 1.9 was installed.  My problem seemed to be with am-wrapper.pl

There was no mention of 1.9 in the am-wrapper file (or 1.8 for that
matter) so it just fell back to old reliable.  To resolve this, I
modified the file so it looks for 1.9 when it is set through
WANT_AUTOMAKE.  I know this is a gentoo issue (not sablevm), but
thought you might be curious in case you get any other questions.  I'm
not sure what part of gentoo is responsible for updating that file,
but it looks like it wasn't done on my system.

Also, I don't know if it is possible to test for CFLAGS set in
make.conf in an ebuild (I've only copied existing ones), but sablevm
failed to compile with -03 (which is what my make.conf file uses for
default).  When I changed it to -02 it compiled just fine though.

Thanks, again, for your help.  I look foward to experimenting with SableVM.

Kevin



On Tue, 4 Jan 2005 03:04:57 -0500, David Bélanger <[email protected]> wrote:
> 
> On Sun, Jan 02, 2005 at 10:20:05PM -0500, Kevin S. Clarke wrote:
> > Hi,
> >
> > I am interested in trying out SableVM. Since my distro is Gentoo, I
> > found the ebuild for building SableVm from SVN
> > (http://bugs.gentoo.org/show_bug.cgi?id=72988).  However, when I try
> > to build, I get an error that is probably a result of my setup.  I'm
> > wondering what I need to do to get it to work.  I have a ~x86 system.
> > My relevant USE flags are: -debug +gtk
> >
> > The last part of my exception/build output is:
> >
> >  * subversion update start -->
> >  *    update from: svn://svn.sablevm.org/sablevm/branches/staging
> > Skip updating...
> >  *     updated in: /usr/portage/distfiles/svn-src/sablevm/staging
> >  *      copied to: /var/tmp/portage/sablevm-svn-20041129-r1/work
> >
> >  * begin bootstrap -->
> >  *    bootstrap with commands:                  cd
> > /var/tmp/portage/sablevm-svn-20041129-r1/work &&             mv
> > staging sablevm-20041129 &&          cd sablevm-20041129 &&
> >   sed -i s:staging+:staging-sablevm-svn-20041129+: configure.ac &&
> >            ./autogen.sh
> > configure.ac:12: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
> > aclocal.m4:546: AM_CONFIG_HEADER is expanded from...
> > configure.ac:12: the top level
> > configure.ac:413: warning: do not use m4_regexp: use regexp or m4_bregexp
> > aclocal.m4:559: _AM_DIRNAME is expanded from...
> > configure.ac:413: the top level
> > configure.ac:12: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
> > aclocal.m4:546: AM_CONFIG_HEADER is expanded from...
> > configure.ac:12: the top level
> > configure.ac:413: warning: do not use m4_regexp: use regexp or m4_bregexp
> > aclocal.m4:559: _AM_DIRNAME is expanded from...
> > configure.ac:413: the top level
> > automake-1.5: configure.ac: `AM_INIT_AUTOMAKE' must be used
> > automake-1.5: configure.ac: installing `./install-sh'
> > automake-1.5: configure.ac: installing `./mkinstalldirs'
> > automake-1.5: configure.ac: installing `./missing'
> > automake-1.5: configure.ac: installing `./depcomp'
> >
> > !!! ERROR: dev-java/sablevm-svn-20041129-r1 failed.
> > !!! Function subversion_bootstrap, Line 226, Exitcode 1
> > !!! subversion.eclass: can't eval ESVN_BOOTSTRAP.
> > !!! If you need support, post the topmost build error, NOT this status message.
> >
> 
> Hi Kevin,
> 
> I see automake-1.5 and a "AM_INIT_AUTOMAKE must be used" message.  Do:
> automake --version to see which version it is.  On ~x86, I think
> automake should be 1.9.x by default?
> 
> If its not 1.9.x, try:
> WANT_AUTOMAKE=1.9 emerge sablevm-svn
> 
> If not, my most recent ebuilds are here:
> http://www.sable.mcgill.ca/~dbelan2/ebuilds/dev-java/sablevm-svn/
> 
> The sablevm-svn-20041129-r1 should still work and it should be the same
> as the report, I just tried it.  The
> December one applies additional cross-compilation patch and should work
> equally well though requires files in files/ directory.
> 
> If you still encounter problem, report back with the output from "emerge info".
> 
> David
> 
> ---
> 
> David Bélanger
> Web page:   http://www.cs.mcgill.ca/~dbelan2/
> Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.