On Wed, Oct 26, 2016 at 02:04:20PM +0200, Sascha Steinbiss wrote:
>...
> > That's #837445 in the check package, which became fatal with gcc-6 in
> > unstable defaulting to PIE since this week Tuesday.
>
> I can't reproduce this in a current unstable chroot; it looks like
> #837445 has been
Hi Sascha,
On Wed, Oct 26, 2016 at 02:04:20PM +0200, Sascha Steinbiss wrote:
> Regarding the original bug, I have confirmed again with upstream that
> it's fine to disable these tests, which I have done in Git. Builds fine
> for me now.
>
> Does everyone agree? I can make an upload if so. I have
Hi Andreas and Adrian,
>>> since there are no responses so far I wonder how to proceed with the
>>> package.
>>
>> Yes, that's one of the bugs that has been on my list for a while as well...
Regarding the original bug, I have confirmed again with upstream that
it's fine to disable these tests,
On Fri, Oct 21, 2016 at 10:39:13AM +0200, Sascha Steinbiss wrote:
> Hi Andreas,
>
> > since there are no responses so far I wonder how to proceed with the
> > package.
>
> Yes, that's one of the bugs that has been on my list for a while as well...
>
> > I need to admit I get a different error
Hi Andreas,
> since there are no responses so far I wonder how to proceed with the
> package.
Yes, that's one of the bugs that has been on my list for a while as well...
> I need to admit I get a different error when trying to build
> the current state of gubbins packaging Git:
>
> gcc
Hi Sascha,
since there are no responses so far I wonder how to proceed with the
package. I need to admit I get a different error when trying to build
the current state of gubbins packaging Git:
gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../tests
-pthread -g -O2
6 matches
Mail list logo