Re: gentoo ebuild question

On Tue, Jan 04, 2005 at 01:20:18PM -0500, Kevin S. Clarke wrote:
> 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.
> 

Hi,

I do my development mostly on a PowerPC but I am pretty sure I got 1.9
also on my x86.  Before modifying the am-wrapper, did you try
re-emerging: automake-wrapper 
I have version 1 and it is in the script.

Note also that the wrapper script is in the portage tree:
/usr/portage/sys-devel/automake-wrapper/files/am-wrapper-1.sh
Check to see if the installed one and that one corresponds.

> 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.

yes, it is possible to remove -O3 in the ebuilds, some package does it.
I am not sure what is Gentoo policy about this, since -O3 might be
considered an agressive optimization flag?  I will have to inform myself
on that side.

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

Thank you for trying out my sablevm-svn ebuild, its good to know that
people are using it, and hence, testing it on their system.

David

---

David Bélanger
Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt