On 20-07-14 17:16, Yavor Doganov wrote:
> Yes, this is one way of doing it. Something like this
>
> - $(confflags)
> + $(confflags) || (cat config.log; exit 1)
>
> in debian/rules (configure-stamp) ought to work.
Yes, let's do this. I propose to add this to the Debian package as well.
I will create a debdiff to do this in Ubuntu now.
>>> Build killed with signal 15 after 60 minutes of inactivity
>
> This is very similar to Debian #649419. Unfortunately I was not able
> to reproduce it after probably 100 builds of gnustep-base. You have
> to attach gdb to the stuck test program and see what's going on.
Well, a retry succeeded. So it is not something that we need to fix on
short term. I think someone with access to a build server setup should
investigate this.
On 20-07-14 17:16, Yavor Doganov wrote:
> Yes, this is one way of doing it. Something like this
>
> - $(confflags)
> + $(confflags) || (cat config.log; exit 1)
>
> in debian/rules (configure-stamp) ought to work.
Yes, let's do this. I propose to add this to the Debian package as well.
I will create a debdiff to do this in Ubuntu now.
>>> Build killed with signal 15 after 60 minutes of inactivity
>
> This is very similar to Debian #649419. Unfortunately I was not able
> to reproduce it after probably 100 builds of gnustep-base. You have
> to attach gdb to the stuck test program and see what's going on.
Well, a retry succeeded. So it is not something that we need to fix on
short term. I think someone with access to a build server setup should
investigate this.
Paul