* Emanuele Rocca [2024-01-17 16:22]:
as a workaround for this issue, you could disable stack-clash-protection
when building for armhf. The following snippet in debian/rules should do
the trick:
ifeq ($(DEB_TARGET_ARCH),armhf)
DEB_BUILD_MAINT_OPTIONS = hardening=+all,-stackclash
else
Hi Rafael,
as a workaround for this issue, you could disable stack-clash-protection
when building for armhf. The following snippet in debian/rules should do
the trick:
ifeq ($(DEB_TARGET_ARCH),armhf)
DEB_BUILD_MAINT_OPTIONS = hardening=+all,-stackclash
else
DEB_BUILD_MAINT_OPTIONS =
Control: severity -1 important
* Sebastiaan Couwenberg [2024-01-01 20:13]:
plplot got removed from armhf, the severity of this issue could be
lowered to important to not have the package removed from testing.
Thanks, I am doing it hereby.
Best,
Rafael Laboissière
plplot got removed from armhf, the severity of this issue could be
lowered to important to not have the package removed from testing.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
severity 1055750 serious
merge 1055750 1055228
Control: reassign -1 plplot
Control: forwarded 1055228 https://sourceforge.net/p/plplot/bugs/206/
Control: merge -1 1055228
* Emanuele Rocca [2023-11-16 09:30]:
To be honest I think it's safe to close 1055750 (gfortran) and mark
1055228 (plplot) as forwarded upstream though, I don't think we
Hi Rafael,
On 2023-11-16 08:42, Rafael Laboissière wrote:
> Control: forwarded -1 https://sourceforge.net/p/plplot/bugs/206/
>
> * Rafael Laboissière [2023-11-16 07:51]:
>
> > My guess is that the bug is in PLplot and not in gfortran, but this is
> > just a guess. I will eventually inform the
Control: forwarded -1 https://sourceforge.net/p/plplot/bugs/206/
* Rafael Laboissière [2023-11-16 07:51]:
My guess is that the bug is in PLplot and not in gfortran, but this is
just a guess. I will eventually inform the PLplot upstream authors
about the issue.
Done !
R.
* Emanuele Rocca [2023-11-15 20:11]:
On 2023-11-15 06:47, Rafael Laboissière wrote:
Does this mean that the origin of the bug is upstream or that it still may
be a bug in gfortran?
At this point we know for sure that the issue is not armhf-specific, and
also that it is not caused by
Hello Rafael!
On 2023-11-15 06:47, Rafael Laboissière wrote:
> Does this mean that the origin of the bug is upstream or that it still may
> be a bug in gfortran?
At this point we know for sure that the issue is not armhf-specific, and
also that it is not caused by stack-clash-protection. On the
Hi Emanuele,
Our messages crossed.
* Emanuele Rocca [2023-11-15 18:20]:
On 2023-11-09 05:11, Rafael Laboissière wrote:
The Fortran example x09f.f90, which is exercised during the building of
plplot, now fails on armhf, due to the use of the compiler option
-fstack-clash-protection.
The
11 matches
Mail list logo
