[arch-dev-public] gcc-4.4.0 toolchain rebuild with query about gcc-gcj and related packages
Allan McRae
allan at archlinux.org
Sat May 2 00:28:08 EDT 2009
Jan de Groot wrote:
> On Sat, 2009-05-02 at 03:17 +1000, Allan McRae wrote:
>
>
>> So, looking into this further, apart from java-gcj-compat and
>> eclipse-ecj, we have two packages that depend on gcc-gcj (gjdoc and
>> jikes) and two that makedepend on java-gcj-compat (bcprov, juint - can
>> probably be changed to openjdk6), but nothing else for eclipse-ecj.
>> The apache-ant and openjdk6 PKGBUILDs both mention java-gcj-compat in a
>> trivial way.
>>
>> So packages that would also need looked at to be removed when gcc-gcj,
>> java-gcj-compat and eclipse-ecj go, are gjdoc and jikes. Jikes is a
>> orphan and dead upstream as far as I can tell. It is also not needed
>> given javac that comes with openjdk6. gjdoc is currently only a dep for
>> java-gcj-compat.
>>
>> The only issue with packages in [community] is that classpath depends in
>> jikes.
>>
>
> The makedepends on gcj or java-gcj-compat can be changed to openjdk6. As
> for classpath in community: classpath is an abandoned project and was
> merged into gcj, which was abandoned when Sun released OpenJDK as GPL. I
> don't think we should care so much about it.
> About eclipse-ecj: it's outdated because of the gcj patch, newer
> versions don't work with gcj. We could keep it and build with openjdk if
> we want, as eclipse-ecj is a faster compiler than javac itself in some
> situations (mainly when used as JSP compiler for Tomcat or any other
> servlet container).
>
I'm happy for for eclipse-ecj to stay around in that format. Do you (or
someone else) want to make this change and maintain the package? My
motivation towards it is minimal... I would like to move the toolchain
around Thursday so I can start with the new glibc release on Friday so
this would need addressed by then.
Allan
More information about the arch-dev-public
mailing list