Here is the warning reportIt happens on mips* in other packages too.
https://udd.debian.org/lintian/?packages=libgrokj2k
I ran `readelf -l` on the .so, and I noticed that there is no E flagOn the .so from mips64el?
on the GNU_STACK entry. So, it looks like this is a false positive.
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 is a false positive.
Is this a fair assumption ?
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 GNU_STACK entry. So, it looks like this is a false positive.
Is this a fair assumption ?
I have noticed this, too, in the packages that I maintain. However, note
that this concerns only the mips* architectures, so you would only find
this on such a machine.
mips66el is not a target platformWhat do you mean?
On Mon, Sep 12, 2022 at 08:37:34AM -0400, Aaron Boxer wrote:
Here is the warning report
https://udd.debian.org/lintian/?packages=libgrokj2kIt happens on mips* in other packages too.
I ran `readelf -l` on the .so, and I noticed that there is no E flagOn the .so from mips64el?
on the GNU_STACK entry. So, it looks like this is a false positive.
--
WBR, wRAR
On Mon, Sep 12, 2022 at 08:49:53AM -0400, Aaron Boxer wrote:
mips66el is not a target platformWhat do you mean?
--
WBR, wRAR
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 299 |
Nodes: | 16 (2 / 14) |
Uptime: | 81:34:11 |
Calls: | 6,696 |
Calls today: | 1 |
Files: | 12,229 |
Messages: | 5,347,841 |