Benjamin Mesing wrote:
> I fail to see the reason why the results should be the same.
Because otherwise we will get interesting FTBFS bugs at random times, that
someone will have to fix.
> Using /usr/bin/javac might as well lead to the usage of different Java
> compilers
Which is why we don't us
On Fri, Mar 16, 2007 at 07:26:39AM +1100, Sam Couter wrote:
> Michael Koch <[EMAIL PROTECTED]> wrote:
> > Who says the results are the same? Who says the results are the same
> > with different JDK 5 implementations?
>
> The Java bytecode spec says so. Most differences will indicate bugs in
> one
On Thu, Mar 15, 2007 at 09:13:16PM +0100, Benjamin Mesing wrote:
> [Please CC, I am not subscribed]
>
> > > >>> How do I ensure, that the correct compiler is used.
> > > >>> Is the only way, to explicitly set the java
> > > >>> compiler path (i.e. /usr/lib/jvm/java-1.5.0/bin/javac
> > >
> > > >>
[Please CC, I am not subscribed]
> > >>> How do I ensure, that the correct compiler is used.
> > >>> Is the only way, to explicitly set the java
> > >>> compiler path (i.e. /usr/lib/jvm/java-1.5.0/bin/javac
> >
> > >> Yes, that is the only correct way. We must be sure that the package
> > >> bui
Michael Koch <[EMAIL PROTECTED]> wrote:
> Who says the results are the same? Who says the results are the same
> with different JDK 5 implementations?
The Java bytecode spec says so. Most differences will indicate bugs in
one implementation or another, which need to be found and fixed.
--
Sam Cou
On Thu, Mar 15, 2007 at 01:55:35PM +0100, Benjamin Mesing wrote:
> [Please CC, I am not subscribed]
>
> >>> How do I ensure, that the correct compiler is used.
> >>> Is the only way, to explicitly set the java
> >>> compiler path (i.e. /usr/lib/jvm/java-1.5.0/bin/javac
>
> >> Yes, that is the onl
[Please CC, I am not subscribed]
>>> How do I ensure, that the correct compiler is used.
>>> Is the only way, to explicitly set the java
>>> compiler path (i.e. /usr/lib/jvm/java-1.5.0/bin/javac
>> Yes, that is the only correct way. We must be sure that the package
>> builds with identical result
* Marcus Better:
> Yes, that is the only correct way. We must be sure that the package
> builds with identical results on different systems,
It's not so much that we need identical results, but the result must
use the same ABI, which isn't true across major Java versions.
--
To UNSUBSCRIBE, em
Benjamin Mesing wrote:
> I want to build a package which requires Java 5. Therefore I
> build-depend on (sun-java5-jdk | sun-java6-jdk).
Please don't do this, just select one of them.
> How do I ensure, that the correct compiler is used.
> Is the only way, to explicitly set the java
> compiler p
On Sat, Mar 10, 2007 at 12:59:53PM +0100, Eric Lavarde wrote:
> Hi,
>
> you might use the cdbs system and add the variable as follows:
> JAVA_HOME_DIRS := /usr/lib/jvm/java-1.5.0 /usr/lib/jvm/java-1.6.0
> (in order of preference)
>
> Note: some sponsors refuse the CDBS system, but I don't t
Hi,
you might use the cdbs system and add the variable as follows:
JAVA_HOME_DIRS := /usr/lib/jvm/java-1.5.0 /usr/lib/jvm/java-1.6.0
(in order of preference)
Note: some sponsors refuse the CDBS system, but I don't think this is
the case within the Debian-Java community.
Hope this helps,
[Please CC, I am not subscribed]
Hello,
I want to build a package which requires Java 5. Therefore I
build-depend on (sun-java5-jdk | sun-java6-jdk). How do I ensure, that
the correct compiler is used. E.g. if a free java compiler is
installed, /usr/bin/javac might point to the free compiler whi
12 matches
Mail list logo
