On 05/23/2010 06:26 PM, David Relson wrote:
On Sun, 23 May 2010 11:01:53 -0700
walt wrote:
On 05/23/2010 09:56 AM, David Relson wrote:
Output of "emerge -d ant-junit" is attached, though I don't
understand what the additional info means.
The 'build.log' should contain the actual error message following the
test for the system-vm. The test code will look something like this:
+ java-pkg_switch-vm
+ debug-print-function java-pkg_switch-vm
+ str='java-pkg_switch-vm: entering function'
+ shift
+ debug-print 'java-pkg_switch-vm: entering function, parameters: '
+ '[' '!' -d /media/d/portage/dev-java/ant-junit-1.7.1/temp ']'
+ '[' 'java-pkg_switch-vm: entering function, parameters: ' ']'
+ '[' '' == on ']'
+ '[' -n '' ']'
+ echo 'java-pkg_switch-vm: entering function, parameters: '
+ chmod
g+w /media/d/portage/dev-java/ant-junit-1.7.1/temp/eclass-debug.log
+ shift
+ '[' '' ']'
+ java-pkg_needs-vm
+ debug-print-function java-pkg_needs-vm
<lots of snippage>
There are no error messages in my build.log but I expect there will
be some obvious ones in yours.
Hi Walt,
What build.log file do you mean?
/var/tmp/portage/dev-java/ant-junit-1.7.1/temp/build.log (unless you
changed the default $PORTAGE_TMPDIR in make.conf). The eclass-debug.log
is in the same directory.
Running "emerge -d ant-junit" produces files:
/var/log/portage/dev-java:ant-junit-1.7.1:20100524-010955.log
/var/log/portage/elog/dev-java:ant-junit-1.7.1:20100524-010957.log
Thanks, I never knew about those logs. Maybe they only appear if the
build fails because I don't have them on my machine.
I found java-pkg_needs-vm in /usr/portage/eclass/java-utils-2.eclass.
However "equery belongs /usr/portage/eclass/java-utils-2.eclass"
doesn't find an owning package for this file. Do you have this file?
What package owns it?
As Kenneth said, it doesn't belong to any one package, but eclass files
are useful for storing code that can be shared by several similar packages,
like a group of related java packages.
The ant-junit-1.7.1.ebuild file says "inherit ant-tasks", which means
that the ant-tasks.eclass file is read before beginning the actual build.
You can see the sequence of events in the eclass-debug.log.
