On Mon, 2022-09-12 at 10:05 -0400, Aaron Boxer wrote:
> My codec project uses SIMD code for x86 and AArch64 architectures.
> Also, as there are different versions of SIMD i.e. SSE vs AVX vs
> AVX2, the project uses a library that builds multiple versions of the
> accelerated code and chooses
On Mon, Sep 12, 2022 at 10:37 AM Andrey Rahmatullin wrote:
> On Mon, Sep 12, 2022 at 10:05:36AM -0400, Aaron Boxer wrote:
> > My codec project uses SIMD code for x86 and AArch64 architectures. Also,
> as
> > there are different versions of SIMD i.e. SSE vs AVX vs AVX2, the project
> > uses a
On Mon, Sep 12, 2022 at 10:05:36AM -0400, Aaron Boxer wrote:
> My codec project uses SIMD code for x86 and AArch64 architectures. Also, as
> there are different versions of SIMD i.e. SSE vs AVX vs AVX2, the project
> uses a library that builds multiple versions of the accelerated code and
>
Hello,
My codec project uses SIMD code for x86 and AArch64 architectures. Also, as
there are different versions of SIMD i.e. SSE vs AVX vs AVX2, the project
uses a library that builds multiple versions of the accelerated code and
chooses which version to use at runtime.
On Mon, Sep 12, 2022 at 8:59 AM Andrey Rahmatullin wrote:
> On Mon, Sep 12, 2022 at 08:49:53AM -0400, Aaron Boxer wrote:
> > mips66el is not a target platform
> What do you mean?
>
by that, I mean I don't have access to this platform for my own testing,
and I doubt there are any users currently
On Mon, Sep 12, 2022 at 08:49:53AM -0400, Aaron Boxer wrote:
> mips66el is not a target platform
What do you mean?
--
WBR, wRAR
signature.asc
Description: PGP signature
Thanks, not a big deal then :)
On Mon, Sep 12, 2022 at 8:50 AM David Bürgin wrote:
> Aaron Boxer:
> > Here is the warning report
> >
> > https://udd.debian.org/lintian/?packages=libgrokj2k
> >
> > and explanation of the warning
> >
> >
a, I missed that. mips66el is not a target platform, so I suppose I can
ignore this warning.
On Mon, Sep 12, 2022 at 8:47 AM Andrey Rahmatullin wrote:
> On Mon, Sep 12, 2022 at 08:37:34AM -0400, Aaron Boxer wrote:
> > Here is the warning report
> >
> >
Aaron Boxer:
> Here is the warning report
>
> https://udd.debian.org/lintian/?packages=libgrokj2k
>
> and explanation of the warning
>
> https://lintian.debian.org/tags/executable-stack-in-shared-library
>
> I ran `readelf -l` on the .so, and I noticed that there is no E flag
> on the
On Mon, Sep 12, 2022 at 08:37:34AM -0400, Aaron Boxer wrote:
> Here is the warning report
>
> https://udd.debian.org/lintian/?packages=libgrokj2k
It happens on mips* in other packages too.
> I ran `readelf -l` on the .so, and I noticed that there is no E flag
> on the GNU_STACK entry. So, it
Here is the warning report
https://udd.debian.org/lintian/?packages=libgrokj2k
and explanation of the warning
https://lintian.debian.org/tags/executable-stack-in-shared-library
I ran `readelf -l` on the .so, and I noticed that there is no E flag
on the GNU_STACK entry. So, it looks like this
Your message dated Mon, 12 Sep 2022 11:59:33 +0200
with message-id
and subject line Re: RFS: libfilezilla/0.39.0-1 -- build high-performing
platform-independent programs (runtime lib)
has caused the Debian Bug report #1019562,
regarding RFS: libfilezilla/0.39.0-1 -- build high-performing
12 matches
Mail list logo
