On 10/25/19 2:38 PM, Trevor Woerner wrote:
> On Fri 2019-10-25 @ 01:24:51 PM, Trevor Woerner wrote:
>> On Fri 2019-10-25 @ 07:37:34 AM, akuster808 wrote:
>>> is someone going to send a patch?
>> Yes, I'm working on that now. This looks like something that should be fixed
>> upstream, so that's
On Fri, Oct 25, 2019 at 6:31 AM zangrc wrote:
>
> hello！
>
> We think this problem has something to do with the host environment. We tried
> to reproduce the error on ubuntu16.04 and fedora29, but they all compiled
> successfully. Can you tell us which distributions are having this problem?
I
On Fri 2019-10-25 @ 01:24:51 PM, Trevor Woerner wrote:
> On Fri 2019-10-25 @ 07:37:34 AM, akuster808 wrote:
> > is someone going to send a patch?
>
> Yes, I'm working on that now. This looks like something that should be fixed
> upstream, so that's the approach I'm taking. Please bear with me :-)
On Fri 2019-10-25 @ 07:37:34 AM, akuster808 wrote:
> is someone going to send a patch?
Yes, I'm working on that now. This looks like something that should be fixed
upstream, so that's the approach I'm taking. Please bear with me :-)
--
___
On Fri 2019-10-25 @ 06:01:54 PM, Khem Raj wrote:
> On Fri, Oct 25, 2019 at 2:45 PM Trevor Woerner wrote:
> > Yes, adding the following line fixes it:
> >
> > LDFLAGS_append_class-native = " -lpthread"
> >
> > (unless there's a distro-override way of doing it...?)
> >
> There is no need
On Fri 2019-10-25 @ 11:44:14 AM, Trevor Gamblin wrote:
> On 10/25/19 11:16 AM, Trevor Woerner wrote:
> > Does this break on hosts where it had previously worked?
> Doesn't affect my (successful) Fedora build. Would also be interested to
> know.
Okay, thanks for the report! :-)
--
On Fri, Oct 25, 2019 at 2:45 PM Trevor Woerner wrote:
> On Fri 2019-10-25 @ 09:22:04 AM, Trevor Woerner wrote:
> > On Thu 2019-10-24 @ 04:05:10 PM, Khem Raj wrote:
> > > perhaps you need to add -pthread to LDFLAGS
> >
> > I'll set up a test build.
>
> Yes, adding the following line fixes it:
>
>
On 10/25/19 11:16 AM, Trevor Woerner wrote:
On Fri 2019-10-25 @ 07:37:34 AM, akuster808 wrote:
On 10/25/19 6:44 AM, Trevor Woerner wrote:
On Fri 2019-10-25 @ 09:22:04 AM, Trevor Woerner wrote:
On Thu 2019-10-24 @ 04:05:10 PM, Khem Raj wrote:
perhaps you need to add -pthread to LDFLAGS
On Fri 2019-10-25 @ 07:37:34 AM, akuster808 wrote:
>
>
> On 10/25/19 6:44 AM, Trevor Woerner wrote:
> > On Fri 2019-10-25 @ 09:22:04 AM, Trevor Woerner wrote:
> >> On Thu 2019-10-24 @ 04:05:10 PM, Khem Raj wrote:
> >>> perhaps you need to add -pthread to LDFLAGS
> >> I'll set up a test build.
>
On 10/25/19 6:44 AM, Trevor Woerner wrote:
> On Fri 2019-10-25 @ 09:22:04 AM, Trevor Woerner wrote:
>> On Thu 2019-10-24 @ 04:05:10 PM, Khem Raj wrote:
>>> perhaps you need to add -pthread to LDFLAGS
>> I'll set up a test build.
> Yes, adding the following line fixes it:
>
>
On Fri 2019-10-25 @ 09:22:04 AM, Trevor Woerner wrote:
> On Thu 2019-10-24 @ 04:05:10 PM, Khem Raj wrote:
> > perhaps you need to add -pthread to LDFLAGS
>
> I'll set up a test build.
Yes, adding the following line fixes it:
LDFLAGS_append_class-native = " -lpthread"
(unless there's a
On 10/25/19 9:17 AM, Trevor Woerner wrote:
On Fri 2019-10-25 @ 01:30:32 PM, zangrc wrote:
hello！
We think this problem has something to do with the host environment. We
tried to reproduce the error on ubuntu16.04 and fedora29, but they all
compiled successfully. Can you tell us which
On Thu 2019-10-24 @ 04:05:10 PM, Khem Raj wrote:
> perhaps you need to add -pthread to LDFLAGS
That's what it feels like.
I'll set up a test build.
I'm pretty sure I've stumbled across this in the past, but it seems like
different distros package the crypto things differently, therefore building
On Fri 2019-10-25 @ 01:30:32 PM, zangrc wrote:
> hello！
>
> We think this problem has something to do with the host environment. We
> tried to reproduce the error on ubuntu16.04 and fedora29, but they all
> compiled successfully. Can you tell us which distributions are having this
> problem?
hello！
We think this problem has something to do with the host environment. We
tried to reproduce the error on ubuntu16.04 and fedora29, but they all
compiled successfully. Can you tell us which distributions are having
this problem?
On 10/25/19 8:19 AM, akuster808 wrote:
On 10/24/19
On 10/24/19 6:37 AM, Trevor Gamblin wrote:
>
> On 10/24/19 9:06 AM, Trevor Woerner wrote:
>
>> This upgrade caused my build to fail :-(
>> Is anyone else seeing this?
Me too but only on my older ubunto 16.04.
we should bug this. If no one does by Friday night I will.
- armin
>> 22:47:40
On Thu, Oct 24, 2019 at 09:06:41AM -0400, Trevor Woerner wrote:
> This upgrade caused my build to fail :-(
> Is anyone else seeing this?
>
> 22:47:40 | x86_64-linux-libtool: link: gcc -W -Wall -Wshadow -Wformat
> -Wundef -D_GNU_SOURCE
>
On 10/24/19 9:06 AM, Trevor Woerner wrote:
This upgrade caused my build to fail :-(
Is anyone else seeing this?
22:47:40 | x86_64-linux-libtool: link: gcc -W -Wall -Wshadow -Wformat
-Wundef -D_GNU_SOURCE
This upgrade caused my build to fail :-(
Is anyone else seeing this?
22:47:40 | x86_64-linux-libtool: link: gcc -W -Wall -Wshadow -Wformat
-Wundef -D_GNU_SOURCE
Signed-off-by: Zang Ruochen
---
.../{libcap-ng-python_0.7.9.bb => libcap-ng-python_0.7.10.bb} | 0
meta/recipes-support/libcap-ng/libcap-ng.inc| 6 +++---
.../libcap-ng/{libcap-ng_0.7.9.bb => libcap-ng_0.7.10.bb} | 0
3 files changed, 3 insertions(+), 3
20 matches
Mail list logo
