On 06/18/2015 11:29 PM, Matthias Klose wrote:
> this doesn't look correct. You simply allow the libstdc++ build without these
> symbols. Please could you address this upstream, and ask to create a baseline
> symbols file, and then see if the build is supposed to be done without these
> symbols?
J
On 06/18/2015 10:54 PM, John Paul Adrian Glaubitz wrote:
> On 06/17/2015 11:47 PM, John Paul Adrian Glaubitz wrote:
>>> Send a patch if you feel it is worth it.
>>
>> Currently working on that. Will throw in a patch once I got a working
>> build which I will be uploading to unreleased.
>
> Attache
On 06/17/2015 11:47 PM, John Paul Adrian Glaubitz wrote:
>> Send a patch if you feel it is worth it.
>
> Currently working on that. Will throw in a patch once I got a working
> build which I will be uploading to unreleased.
Attached patch fixes the FTBFS for me on sparc64. I'm about to upload
a f
> Send a patch if you feel it is worth it.
Currently working on that. Will throw in a patch once I got a working
build which I will be uploading to unreleased.
Cheers,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin -
On 02/05/2015 10:05 PM, Helmut Grohne wrote:
> Source: gcc-4.9
> Version: 4.9.1-17
> User: helm...@debian.org
> Usertags: rebootstrap
>
> gcc-4.9 currently FTBFS on sparc64 due to symbol errors. While the last
> two builds on sompek failed due to -ENOSPC the build of 4.9.1-17 shows
> proper symbol
Source: gcc-4.9
Version: 4.9.1-17
User: helm...@debian.org
Usertags: rebootstrap
gcc-4.9 currently FTBFS on sparc64 due to symbol errors. While the last
two builds on sompek failed due to -ENOSPC the build of 4.9.1-17 shows
proper symbol diffs:
http://buildd.debian-ports.org/status/fetch.php?pkg=
6 matches
Mail list logo
