<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>91607</bug_id>
          
          <creation_ts>2005-05-05 13:13 0000</creation_ts>
          <short_desc>eclipse-sdk-3.1_pre6.ebuild fails to build against ibm jdk 1.4.2</short_desc>
          <delta_ts>2005-07-30 11:35:01 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>2005.0</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>CANTFIX</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>blocker</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>guardian@planet-d.net</reporter>
          <assigned_to>karltk@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>guardian@planet-d.net</who>
            <bug_when>2005-05-05 13:13:01 0000</bug_when>
            <thetext>Emerging eclipse-sdk-3.1_pre6 fails because of differences between sun and ibm jdks. Details to fix the problem are provided in the additional information field.

Reproducible: Always
Steps to Reproduce:
1. unmask eclipse-sdk against ~x86
2. emerge eclipse-sdk
3.

Actual Results:  
build failed

Expected Results:  
build correctly ;)

Here is the difference between my modified ebuild file and the one provided by
portage:

diff /usr/portage/dev-util/eclipse-sdk/eclipse-sdk-3.1_pre6.ebuild
/usr/local/portage/dev-util/eclipse-sdk/eclipse-sdk-3.1_pre6.ebuild
279c279
&lt;       [ ${ARCH} == &apos;x86&apos; ] &amp;&amp; awt_lib_path=${JAVA_HOME}/jre/lib/i386
---
&gt;       [ ${ARCH} == &apos;x86&apos; ] &amp;&amp; awt_lib_path=${JAVA_HOME}/jre/bin
435c435
&lt;              
ant_extra_opts=&quot;-Dbootclasspath=${bp}/core.jar:${bp}/xml.jar:${bp}/graphics.jar:${bp}/security.jar&quot;
---
&gt;              
ant_extra_opts=&quot;-Dbootclasspath=${bp}/core.jar:${bp}/xml.jar:${bp}/graphics.jar:${bp}/security.jar:${bp}/server.jar&quot;

As you can see, under the ibm 1.4.2 jdk, libjawt.so is located in the jre/bin
directory and I had to append the bootclasspath variable with server.jar because
of the java.rmi.Remote class.

Please note that my version only addresses the ibm 1.4.2 jdk. Since I&apos;m new to
ebuilds, I don&apos;t know how to select the proper paths and options depending of
the installed jdk.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>karltk@gentoo.org</who>
            <bug_when>2005-05-14 07:15:30 0000</bug_when>
            <thetext>Your patch seems to help, but now I die from outofmemory errors. Either the IBM requires more than 768MB (probably when running javadoc), or the -Xmx768m is not getting through for the IBM JDK.

-Xmx is supported by the IBM JDK java command</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>karltk@gentoo.org</who>
            <bug_when>2005-07-30 11:35:01 0000</bug_when>
            <thetext>Didn&apos;t find a good solution to this. </thetext>
          </long_desc>
      
    </bug>

</bugzilla>