Le 16/06/2016 à 16:39, Gianfranco Costamagna a écrit :
> Hi,
>
>
>> # CC=gcc-6 \> #CPP=cpp-6
>> #
>> # RICHARD, IS IT CORRECT ?
>
> nope :)
>
> anyway, I did
> create a chroot with the build dependencies
> check if the library was not installed (the one you didn't like)
> git
Le 16/06/2016 à 16:39, Gianfranco Costamagna a écrit :
> Hi,
>
>
>> # CC=gcc-6 \> #CPP=cpp-6
>> #
>> # RICHARD, IS IT CORRECT ?
>
> nope :)
>
> anyway, I did
> create a chroot with the build dependencies
> check if the library was not installed (the one you didn't like)
> git
> # Edit debian debian/rules,
> # in the override_dh_auto_configure target,
> # add CC= to dh_auto_configure :
> #
> #dh_auto_configure -- \
> # ac_cv_lib_kvm_kvm_getenvv=no \
> #--disable-bfd \
> # CC=gcc-6 \
> #CPP=cpp-6
> #
> # RICHARD, IS IT CORRECT ?
Le 16/06/2016 à 10:37, Gianfranco Costamagna a écrit :
> Hi,
>
>> As far as I know, the plan is to switch to gcc-6 by default for stretch:
>> https://lists.debian.org/debian-gcc/2016/01/msg00100.html
>> so while identifying and backporting the fix to gcc-5 would be nice, I'd
>> recommend not
Hi,
>As far as I know, the plan is to switch to gcc-6 by default for stretch:
>https://lists.debian.org/debian-gcc/2016/01/msg00100.html
>so while identifying and backporting the fix to gcc-5 would be nice, I'd
>recommend not putting too much effort there.
fully agree, this is why I didn't
Le 16/06/2016 à 10:37, Gianfranco Costamagna a écrit :
> Hi,
>
>> As far as I know, the plan is to switch to gcc-6 by default for stretch:
>> https://lists.debian.org/debian-gcc/2016/01/msg00100.html
>> so while identifying and backporting the fix to gcc-5 would be nice, I'd
>> recommend not
On Wed, Jun 15, 2016 at 12:16:05PM +, Gianfranco Costamagna wrote:
> >It appears that some tests fail for one of my package (gmp-ecm) on one
> >architecture (s390x):
> >after some investigation, it appears that it is a compiler issue: building
> >with gcc-6 (instead of gcc-5)
> >causes no
On 15/06/16 23:20, Eric Heintzmann wrote:
>
>
> Le 15/06/2016 à 23:20, Jerome BENOIT a écrit :
>>
>> On 15/06/16 20:54, Eric Heintzmann wrote:
>>> How can we debug with upstream, without any access to a 390x machine ?
>>
>> You can ask for an access to Debian Porter machine:
>>
Le 15/06/2016 à 23:20, Jerome BENOIT a écrit :
>
> On 15/06/16 20:54, Eric Heintzmann wrote:
>> How can we debug with upstream, without any access to a 390x machine ?
>
> You can ask for an access to Debian Porter machine:
> https://db.debian.org/machines.cgi
>
On 15/06/16 20:54, Eric Heintzmann wrote:
> How can we debug with upstream, without any access to a 390x machine ?
You can ask for an access to Debian Porter machine:
https://db.debian.org/machines.cgi
https://dsa.debian.org/doc/schroot/
But I am afraid that the hard part is to isolate the
Le 15/06/2016 à 14:16, Gianfranco Costamagna a écrit :
> Hi,
>
>> It appears that some tests fail for one of my package (gmp-ecm) on one
>> architecture (s390x):
>> after some investigation, it appears that it is a compiler issue: building
>> with gcc-6 (instead of gcc-5)
>> causes no issue.
Hi,
>It appears that some tests fail for one of my package (gmp-ecm) on one
>architecture (s390x):
>after some investigation, it appears that it is a compiler issue: building
>with gcc-6 (instead of gcc-5)
>causes no issue. So now I want to impose the gcc-6 to d/rules ? What is the
>best way
Dear Forum:
It appears that some tests fail for one of my package (gmp-ecm) on one
architecture (s390x):
after some investigation, it appears that it is a compiler issue: building with
gcc-6 (instead of gcc-5)
causes no issue. So now I want to impose the gcc-6 to d/rules ? What is the
best way
13 matches
Mail list logo
