[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#722542: gcc-spu went away but is still being used

Am 12.09.2013 18:06, schrieb Geoff Levand:
> Hi,
> On Thu, 2013-09-12 at 14:37 +0200, Matthias Klose wrote:
>> Control: reassign -1 newlib
>> Am 12.09.2013 08:31, schrieb Niels Thykier:
>>> Package: gcc-defaults,newlib
>>> Severity: important
>>> Dear maintainers of gcc-defaults and newlib,
>>> I noticed that gcc-defaults have removed the "gnu-spu" package in sid,
>>> but newlib still build-depends on it.  Since there was no bug against
>>> either package, I am assuming no one has noticed this so far.  As it
>>> is, this is one (of several) things blocking gcc-defaults migration to
>>> testing.
>>> This bug can be fixed either by re-introducing gcc-spu (possibly as a
>>> transitional package, if gcc-spu is no longer needed) or by newlib no
>>> longer Build-Depending on gcc-spu (since it is the last package using
>>> it).  I will leave it to you to decide how this will be solved; please
>>> reassign this bug to the proper package.
>> I don't maintain the spu cross toolchain anymore, as previously written to the
>> gcc and powerpc ML. So newlib maybe shouldn't build the spu packages anymore.
> I guess this means users will also need to build newlib (in addition to
> the gnu-spu) if they want to do spu programming for cell.


> Matthias, please let us know in general what a user needs to do for
> this.

well, the spu cross toolchain needs packaging from a separate source package,
like done for the mingw64 packages.  I suppose newlib needs an update too,
Arthur Loiret is MIA, so the package maybe should be orphaned or taken over as well.


Reply to: