2018-05-12 12:14 GMT+02:00 Alberto Garcia :
> fixed 895969 2.20.2-1
> thanks
>
>> >I think that the patch proposed by Aurelien is probably the best way:
>> >
>> >set(THREADS_PREFER_PTHREAD_FLAG ON)
>>
>> This was fixed in 2.20.2-1, but it was missing Closes, perhaps
>> intentionally:
>
> Yes, we ca
2018-04-26 20:04 Alberto Garcia:
On Wed, Apr 25, 2018 at 11:47:39PM +0200, Manuel A. Fernandez Montecelo wrote:
I was able to build with the simple patch/debdiff attached (and uploaded
to "unreleased").
I am now sure, though, which knobs need to be modified to make this
happen in the upstream p
On Wed, Apr 25, 2018 at 11:47:39PM +0200, Manuel A. Fernandez Montecelo wrote:
> I was able to build with the simple patch/debdiff attached (and uploaded
> to "unreleased").
>
> I am now sure, though, which knobs need to be modified to make this
> happen in the upstream part in the cleanest way.
Hi,
2018-04-23 10:22 Alberto Garcia:
On Sun, Apr 22, 2018 at 08:48:19PM +0200, Aurelien Jarno wrote:
The correct way to link with -pthread instead of -lpthread is to
use define THREADS_PREFER_PTHREAD_FLAG before importing the Thread
package:
Oh, great, I'll give it a try.
I haven't tried t
On Tue, Apr 24, 2018 at 09:18:13PM +0200, Aurelien Jarno wrote:
> > > The correct way to link with -pthread instead of -lpthread is
> > > to use define THREADS_PREFER_PTHREAD_FLAG before importing the
> > > Thread package:
> >
> > Oh, great, I'll give it a try.
That didn't fix the problem for me,
On 2018-04-23 10:22, Alberto Garcia wrote:
> On Sun, Apr 22, 2018 at 08:48:19PM +0200, Aurelien Jarno wrote:
>
> > The correct way to link with -pthread instead of -lpthread is to
> > use define THREADS_PREFER_PTHREAD_FLAG before importing the Thread
> > package:
>
> Oh, great, I'll give it a try
On Sun, Apr 22, 2018 at 08:48:19PM +0200, Aurelien Jarno wrote:
> The correct way to link with -pthread instead of -lpthread is to
> use define THREADS_PREFER_PTHREAD_FLAG before importing the Thread
> package:
Oh, great, I'll give it a try.
> I haven't tried the patch for webkit2gtk, but it wor
On 2018-04-18 11:36, Alberto Garcia wrote:
> On Wed, Apr 18, 2018 at 08:36:29AM +0200, Karsten Merker wrote:
> > Source: webkit2gtk
> > Version: 2.20.1-1
> > X-Debbugs-CC: debian-ri...@lists.debian.org
> > User: debian-ri...@lists.debian.org
> > Usertags: riscv64
> >
> > Hello,
> >
> > webkit2gtk
On Wed, Apr 18, 2018 at 08:00:50PM +0200, Karsten Merker wrote:
> > Is there any way that I can have access to / set up a riscv64
> > build environment in order to debug this problem?
>
> we don't yet have a "regular" porterbox for riscv64, but you can run
> a local qemu-based riscv64 virtual mac
On Wed, Apr 18, 2018 at 11:36:16AM +0200, Alberto Garcia wrote:
> On Wed, Apr 18, 2018 at 08:36:29AM +0200, Karsten Merker wrote:
> > Source: webkit2gtk
> > Version: 2.20.1-1
> > X-Debbugs-CC: debian-ri...@lists.debian.org
> > User: debian-ri...@lists.debian.org
> > Usertags: riscv64
> >
> > Hello
On Wed, Apr 18, 2018 at 08:36:29AM +0200, Karsten Merker wrote:
> Source: webkit2gtk
> Version: 2.20.1-1
> X-Debbugs-CC: debian-ri...@lists.debian.org
> User: debian-ri...@lists.debian.org
> Usertags: riscv64
>
> Hello,
>
> webkit2gtk 2.20.1-1 FTBFS on the riscv64 architecture with "undefined
> r
11 matches
Mail list logo
