-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 2017-02-01 at 14:42 -0500, Breno Leitao wrote:
> Currently bpfcc does not build on ppc64el (and aaarch64) due to missing
> luajit package.
>
> The luajit upstream situation for the new architecture is not clear
> , so, Debian have a luajit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2017-02-09 at 09:22 -0200, Breno Leitao wrote:
> Yes, you can check the following bug:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813831
That bug is an year old with no closure.
Anyways, for bpfcc, this is still an experimental
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
On Thu, 2017-02-09 at 09:22 -0200, Breno Leitao wrote:
> On Wed, Feb 08, 2017 at 12:56:21PM +0530, Ritesh Raj Sarraf wrote:
> > @Breno: Is this the version you are talking about ? 2.1.0~beta2+dfsg-3
> > bpfcc is not targeted for Stretch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 2017-02-08 at 12:56 +0530, Ritesh Raj Sarraf wrote:
> No. I don't want to do that. Packages should be consistent across
> architectures.
> Either we fix it, or let it FTBFS on these architectures.
>
> @Breno: Is this the version you are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 2017-02-08 at 01:15 +0530, Naveen N. Rao wrote:
> > That doesn't help Debian but the changes are almost the same to what I was
> > attempting. But I'm still curious to see how those changes fix the actual
> > bug I
> > encountered. Because
On 2017/02/08 12:08AM, Ritesh Raj Sarraf wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hello Naveen,
>
> On Tue, 2017-02-07 at 23:18 +0530, Naveen N. Rao wrote:
> > I'm not familiar with lua/luajit, but can it be made optional for
> > ppc64el and aarch64?
> >
> > Upstream has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Naveen,
On Tue, 2017-02-07 at 23:18 +0530, Naveen N. Rao wrote:
> I'm not familiar with lua/luajit, but can it be made optional for
> ppc64el and aarch64?
>
> Upstream has a similar fix for rpm distros:
>
I'm not familiar with lua/luajit, but can it be made optional for
ppc64el and aarch64?
Upstream has a similar fix for rpm distros:
https://github.com/iovisor/bcc/commit/ef91b6ed64d022baec977a8415581cd1a4a218c5
Thanks,
Naveen
On Sun, 2017-02-05 at 21:31 +0530, Ritesh Raj Sarraf wrote:
> On Sun, 2017-02-05 at 21:18 +0530, Ritesh Raj Sarraf wrote:
> > I am willing to extend the build to lua, but I need help here. My knowledge
> > of
> > Lua is limited and it'd help if, someone more knowledgeable on the topic,
> > takes
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 2017-02-05 at 21:18 +0530, Ritesh Raj Sarraf wrote:
> I am willing to extend the build to lua, but I need help here. My knowledge of
> Lua is limited and it'd help if, someone more knowledgeable on the topic,
> takes
> the task of extending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thank you for reminding me about experimental. I had completely forgotten about
that.
So, I enabled build dependency on lua5.3.
Request: It'd be nice to have a meta package instead.
By the way, all these packages provide the dependency. I just
Hi,
If you submit a build to experimental, I'd be happy to
test it on aarch64 and armhf.
Riku
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Breno,
On Wed, 2017-02-01 at 14:42 -0500, Breno Leitao wrote:
> Currently bpfcc does not build on ppc64el (and aaarch64) due to missing
> luajit package.
>
> The luajit upstream situation for the new architecture is not clear
> , so, Debian
Source: bpfcc
Version: 0.2.0
Severity: normal
Currently bpfcc does not build on ppc64el (and aaarch64) due to missing
luajit package.
The luajit upstream situation for the new architecture is not clear
, so, Debian have a luajit package in the experimental archive that
contains the ppc64el patch
14 matches
Mail list logo