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

Bug#788497: marked as done (cross-gcc: also use gcc-5-base for libraries)

Your message dated Thu, 18 Jun 2015 19:47:41 +0800
with message-id <CAKcpw6VKoc8HUU-ACtMcz5m-OMWxudH=j7n5ZbqB6HRe+SV9fw@mail.gmail.com>
and subject line Re: cross-gcc: also use gcc-5-base for libraries
has caused the Debian Bug report #788497,
regarding cross-gcc: also use gcc-5-base for libraries
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
788497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788497
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:cross-gcc
Version: 35

Please also don't include TS in BASELDEP and SOFTBASELDEP.
They are used for libraries, such as libgcc1 etc.

cross-gcc-<arch> don't ship libraries, it is not matter for it,
while when bootstrap for a new architecture[1],
it will matter.

[1]: https://wiki.debian.org/MultiarchCrossToolchainBootstrap



-- 
YunQiang Su

Attachment: 0010-gcc-.-base-dependencies-reverted-to-gcc-VER-base-whe.patch
Description: Binary data


--- End Message ---
--- Begin Message --- 
On Fri, 12 Jun 2015 05:09:04 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
> Package: src:cross-gcc
> Version: 35
>
> Please also don't include TS in BASELDEP and SOFTBASELDEP.
> They are used for libraries, such as libgcc1 etc.
>
> cross-gcc-<arch> don't ship libraries, it is not matter for it,
> while when bootstrap for a new architecture[1],
> it will matter.
>
> [1]: https://wiki.debian.org/MultiarchCrossToolchainBootstrap
>

This problem has been solved in version 37.

>
>
> --
> YunQiang Su

--- End Message ---
Reply to: