Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package gcc-snapshot
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status rep
#
# bts-link upstream status pull for source package gcc-snapshot
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #366939
# * http://gcc.gnu.org/PR27571
# * remote status changed: NEW -> RESOLVED
# * remote resolutio
#
# bts-link upstream status pull for source package gcc-4.1
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #356569
# * http://gcc.gnu.org/PR26757
# * remote status changed: NEW -> REOPENED
usertags 356569 - status-N
> Nikita, still interested in fixing that for 3.4, or should we close
> that as wontfix?
It's not very likely that activity on cross stuff will be restored soon :(.
However, some time ago, Wartan Hachaturov <[EMAIL PROTECTED]> agreed to take
the cross compiler packaging work. So I am readdressin
> Jonas Meyer writes:
>> Package: gcc-4.1-source
>> Severity: normal
>>
>>
>> cross-configure.dpatch doesn't apply when following the instructions in
>> README.cross.
>
>> Indeed building according to README.cross doesn't work, because those
>> patches don't apply. However, when simply skippi
Nikita V. Youshchenko writes:
>
> > Nikita, still interested in fixing that for 3.4, or should we close
> > that as wontfix?
>
> It's not very likely that activity on cross stuff will be restored soon :(.
> However, some time ago, Wartan Hachaturov <[EMAIL PROTECTED]> agreed to take
> the cross
Hi,
Why -m64 enabled by default for x86? This is debian sid.
Both debian gcc3 and gcc4 have -m64 enabled.
Thanks!
--
Coywolf Qi Hunt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
7 matches
Mail list logo