On Thu, Jun 08, 2006 at 05:16:38PM +1000, Ben Burton wrote:
>
> > IMO its now the best time to get rid of this package totally.
>
> FWIW, I'd forgotten that java-gcj-compat-dev even existed until your
> mailout to d-d-announce last month ("GCJ 4.1 transition"). In this
> mailout you ask maintain
> IMO its now the best time to get rid of this package totally.
FWIW, I'd forgotten that java-gcj-compat-dev even existed until your
mailout to d-d-announce last month ("GCJ 4.1 transition"). In this
mailout you ask maintainers of JNI packages to use
-I/usr/lib/jvm/java-gcj/include, which relies
On Thu, Jun 08, 2006 at 08:48:01AM +1000, Ben Burton wrote:
>
> Hi,
>
> > Probably a solution would be including libgcj7-dev.
>
> It does. It build-depends on libgcj-dev (>= 4:4.1.0), which brings in
> libgcj7-dev.
>
> >From the amd64 build log (which failed in this way):
>
> Unpacking libg
3 matches
Mail list logo
