Bug#211909: acknowledged by developer (these aren't built because they don't build)
On Mon, Sep 22, 2003 at 09:07:06AM +0200, Matthias Klose wrote:
> Adam Majer writes:
> > On Sun, Sep 21, 2003 at 11:15:19PM +0200, Matthias Klose wrote:
> > > Adam Majer writes:
> > > > reopen 211909
> > > > thanks
> > > >
> > > > On Sun, Sep 21, 2003 at 03:03:14PM -0500, Debian Bug Tracking System wrote:
> > > > > The reason gcc doesn't build gcj for some architectures is that they currently
> > > > > do not work. You're welcome to work on fixing it for the archs in question
> > > > > upstream, as these architectures don't build from source (and/or don't work
> > > > > at all), so they can't be built.
> > > >
> > > > This is *NOT* the right way to fix this bug. You have to change the
> > > > Architecture field to list only the supported archs.
> > > >
> > > > http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture
> > > >
> > > > So change all "any" for the java packages, to "i386 sparc m68k " etc...
> > >
> > > changing this to 'all' for the next upload.
> >
> >
> > Uhhm, 'all' implies that the package(s) can be built on all archs and is
> > arch independant.
>
> it is.
Ok, but the arch specific java packages that do not build on hppa, mips, and mipsel
need to have proper Architecture set.
- Adam
Reply to: