FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Java

 
 
LinkBack Thread Tools
 
Old 02-15-2008, 09:50 PM
Thomas Girard
 
Default Bug#432541: eclipse-cdt FTBFS with gcj-4.2

Hello,

A while ago, I wrote:
> > Using the following pakages:
> > * java-gcj-compat{,-dev} 1.0.69-2
> > * ecj, ecj-gcj, libecj-java and libecj-gcj 3.3.0+0728-1
> > * libgcj-bc, libgcj8{-1,-1-awt,-jar} 4.2.1-3
> > * gcc-4.2-base 4.2.1-3
> > * gcj-4.1-base, gcj-4.1, gij-4.1, libgcj7-1 4.1.2-16
> > * libgcc1 1:4.2.2-3
> > eclipse-cdt compiles.
> >
> > Updating to sid, I reach a point where it no longer compiles:
> > * java-gcj-compat 1.0.76-4 sets gcj-4.2 as the default gcj version
> > * gcj-4.2, gij-4.2 and libgcj8-* are at version 4.2.1-3

On Sat, Jan 26, 2008 at 05:12:44PM +0100, Michael Koch replied:
> I have just tried this with SUN JDK 6, Icedtea, gcj 4.3, jamvm and cacao
> with the following result:
> * SUN JDK 6: Just works.
> * gcj-4.3: No output at all. Returns with exit code 13.
> * icedtea: No output at all. Returns with exit code 13. Exactly the same
> as with gcj.
> * jamvm: Fails but prints quite some output. Main issue is that jamvm has
> no real JAVA_HOME.
> * cacao: Fails but prints some output. Again an issue with an incomplete
> JAVA_HOME provided by cacao.

We made progress on this issue with Michael; it turns out that using
eclipse natively compiled -gcj packages work around the FTBFS, for some
reason.

Michael found out that only eclipse-rcp-gcj is needed, and that deleting
org.eclipse.core.runtime_3.2.0.v20060603.jar.so is enough to make the
compilation fails, while it works when it's there.

So we now have a work-around to compile Eclipse plugins: install
eclipse-rcp-gcj.

What's really weird is that icedtea, even though it does not use -gcj
packages, exhibit the very same behavior.

Any idea on this?

Regards,

Thomas


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-16-2008, 08:56 AM
Andrew Haley
 
Default Bug#432541: eclipse-cdt FTBFS with gcj-4.2

Thomas Girard wrote:

Hello,

A while ago, I wrote:

Using the following pakages:
* java-gcj-compat{,-dev} 1.0.69-2
* ecj, ecj-gcj, libecj-java and libecj-gcj 3.3.0+0728-1
* libgcj-bc, libgcj8{-1,-1-awt,-jar} 4.2.1-3
* gcc-4.2-base 4.2.1-3
* gcj-4.1-base, gcj-4.1, gij-4.1, libgcj7-1 4.1.2-16
* libgcc1 1:4.2.2-3
eclipse-cdt compiles.

Updating to sid, I reach a point where it no longer compiles:
* java-gcj-compat 1.0.76-4 sets gcj-4.2 as the default gcj version
* gcj-4.2, gij-4.2 and libgcj8-* are at version 4.2.1-3


On Sat, Jan 26, 2008 at 05:12:44PM +0100, Michael Koch replied:

I have just tried this with SUN JDK 6, Icedtea, gcj 4.3, jamvm and cacao
with the following result:
* SUN JDK 6: Just works.
* gcj-4.3: No output at all. Returns with exit code 13.
* icedtea: No output at all. Returns with exit code 13. Exactly the same
as with gcj.
* jamvm: Fails but prints quite some output. Main issue is that jamvm has
no real JAVA_HOME.
* cacao: Fails but prints some output. Again an issue with an incomplete
JAVA_HOME provided by cacao.


We made progress on this issue with Michael; it turns out that using
eclipse natively compiled -gcj packages work around the FTBFS, for some
reason.

Michael found out that only eclipse-rcp-gcj is needed, and that deleting
org.eclipse.core.runtime_3.2.0.v20060603.jar.so is enough to make the
compilation fails, while it works when it's there.

So we now have a work-around to compile Eclipse plugins: install
eclipse-rcp-gcj.

What's really weird is that icedtea, even though it does not use -gcj
packages, exhibit the very same behavior.


Has anyone actually attempted to debug this? Which code actually calls
Runtime.exit()?

I'm betting it's a bogus version check.

Andrew.


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-16-2008, 09:33 AM
Andrew Haley
 
Default Bug#432541: eclipse-cdt FTBFS with gcj-4.2

Michael Koch wrote:

On Sat, Feb 16, 2008 at 09:56:18AM +0000, Andrew Haley wrote:

Has anyone actually attempted to debug this? Which code actually calls
Runtime.exit()?


I tried to debug this but I dont found out from where exit is called
with code 13.


What went wrong with the debugging? Do you want me to look?


I'm betting it's a bogus version check.


What kind of version check do you mean?


As far as I'm aware, OSGI bundles are versioned and if an
appropriate OSGI bundle version is not found the program exits.

Andrew.


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-16-2008, 09:37 AM
Michael Koch
 
Default Bug#432541: eclipse-cdt FTBFS with gcj-4.2

On Sat, Feb 16, 2008 at 09:56:18AM +0000, Andrew Haley wrote:
> Has anyone actually attempted to debug this? Which code actually calls
> Runtime.exit()?

I tried to debug this but I dont found out from where exit is called
with code 13.

> I'm betting it's a bogus version check.

What kind of version check do you mean?


Cheers,
Michael


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-16-2008, 11:48 AM
Michael Koch
 
Default Bug#432541: eclipse-cdt FTBFS with gcj-4.2

On Sat, Feb 16, 2008 at 10:33:21AM +0000, Andrew Haley wrote:
> Michael Koch wrote:
> > On Sat, Feb 16, 2008 at 09:56:18AM +0000, Andrew Haley wrote:
> >> Has anyone actually attempted to debug this? Which code actually calls
> >> Runtime.exit()?
> >
> > I tried to debug this but I dont found out from where exit is called
> > with code 13.
>
> What went wrong with the debugging? Do you want me to look?

I was not able top get proper backtraces. All I found was that
exit_group(13) was called.

> >> I'm betting it's a bogus version check.
> >
> > What kind of version check do you mean?
>
> As far as I'm aware, OSGI bundles are versioned and if an
> appropriate OSGI bundle version is not found the program exits.

That doesnt explain why the build always worked with SUN JDK. It should
have failed the same if OSGi versions would be a problem. Wouldn't it?


Cheers,
Michael


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-17-2008, 12:51 PM
Andrew Haley
 
Default Bug#432541: eclipse-cdt FTBFS with gcj-4.2

Michael Koch wrote:

On Sat, Feb 16, 2008 at 10:33:21AM +0000, Andrew Haley wrote:

Michael Koch wrote:

On Sat, Feb 16, 2008 at 09:56:18AM +0000, Andrew Haley wrote:

Has anyone actually attempted to debug this? Which code actually calls
Runtime.exit()?

I tried to debug this but I dont found out from where exit is called
with code 13.

What went wrong with the debugging? Do you want me to look?


I was not able top get proper backtraces. All I found was that
exit_group(13) was called.


So, no-one has actually tried to debug this.


I'm betting it's a bogus version check.

What kind of version check do you mean?

As far as I'm aware, OSGI bundles are versioned and if an
appropriate OSGI bundle version is not found the program exits.


That doesnt explain why the build always worked with SUN JDK. It should
have failed the same if OSGi versions would be a problem. Wouldn't it?


No.
Did you try it with OpenJDK (the Sun version with the binary plugs) ?
This is an important test.

Andrew.


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 10:09 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org