Your message dated Tue, 05 Sep 2017 09:34:18 +0000
with message-id <[email protected]>
and subject line Bug#870773: fixed in motif 2.3.7-2
has caused the Debian Bug report #870773,
regarding motif: flex now has yyleng as an int again
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
870773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870773
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: motif
Version: 2.3.4-13
Severity: important
Tags: patch
User: [email protected]
Usertags: sparc64
X-Debbugs-Cc: [email protected]

Hi,
Currently src:motif FTBFS on sparc64 due to wml crashing with SIGBUS (no
build logs available, as libfl-dev was broken on sparc64 until just
recently, masking the issue). This is because wml.c has yyleng defined
as a size_t, which was correct for versions of flex between 2.5.36 and
2.6.1, but this violated POSIX[0] and so yyleng was reverted back to an
int in 2.6.1[1]. When building on sparc64, yyleng just happens to be
aligned to a 4-byte boundary but not an 8-byte boundary, so doing an
8-byte store to it is unaligned and traps, but on other architectures
this will silently zero out the next 4 bytes in memory.

Please apply the attached debdiff to revert wml.c back to defining
yyleng as an external int, and also add a version constraint to
libfl-dev to ensure motif is not accidentally built with an older
version of flex without reinstating the hunk. With it I can successfully
build motif on sparc64.

Regards,
James

[0] http://pubs.opengroup.org/onlinepubs/7908799/xcu/lex.html
[1] 
https://github.com/westes/flex/commit/7a7c3dfe1bcb8230447ba1656f926b4b4cdfc457
diff -Nru motif-2.3.7/debian/control motif-2.3.7/debian/control
--- motif-2.3.7/debian/control  2017-08-03 11:21:00.000000000 +0100
+++ motif-2.3.7/debian/control  2017-08-04 22:36:10.000000000 +0100
@@ -5,7 +5,7 @@
                debhelper (>= 10),
                dh-exec,
                flex (>= 2.5.36),
-               libfl-dev,
+               libfl-dev (>= 2.6.1),
                libfontconfig1-dev,
                libjpeg-dev,
                libpng-dev,
diff -Nru motif-2.3.7/debian/patches/fix-type-inconsistencies.patch 
motif-2.3.7/debian/patches/fix-type-inconsistencies.patch
--- motif-2.3.7/debian/patches/fix-type-inconsistencies.patch   2017-08-03 
10:54:00.000000000 +0100
+++ motif-2.3.7/debian/patches/fix-type-inconsistencies.patch   2017-08-04 
22:36:10.000000000 +0100
@@ -1,12 +1,10 @@
 Description: Fix type inconsistencies
  This patch fixes various type inconsistencies reported by goto-cc
  from the cbmc package.
- .
- The yyleng fix in tools/wml/wml.c requires flex >= 2.5.36.
 Author: Graham Inggs <[email protected]>
 Forwarded: http://bugs.motifzone.net/show_bug.cgi?id=1641
 Bug-Debian: http://bugs.debian.org/749417
-Last-Update: 2017-08-03
+Last-Update: 2017-08-04
 --- a/lib/Xm/EditresComI.h
 +++ b/lib/Xm/EditresComI.h
 @@ -8,7 +8,7 @@
@@ -49,17 +47,6 @@
  extern int _XmTabbedStackListCount _ARGS((XmTabbedStackList));
  
  #ifndef _NO_PROTO
---- a/tools/wml/wml.c
-+++ b/tools/wml/wml.c
-@@ -153,7 +153,7 @@
- /*
-  * External variables
-  */
--extern        int     yyleng;
-+extern        size_t  yyleng;
- extern  int yyparse();
- 
- 
 --- a/demos/lib/Xmd/RegEdit.c
 +++ b/demos/lib/Xmd/RegEdit.c
 @@ -252,7 +252,7 @@

--- End Message ---
--- Begin Message ---
Source: motif
Source-Version: 2.3.7-2

We believe that the bug you reported is fixed in the latest version of
motif, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Graham Inggs <[email protected]> (supplier of updated motif package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 05 Sep 2017 09:09:54 +0000
Source: motif
Binary: libmotif-common libmrm4 libuil4 libxm4 uil libmotif-dev mwm
Architecture: source
Version: 2.3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Graham Inggs <[email protected]>
Changed-By: Graham Inggs <[email protected]>
Description:
 libmotif-common - Motif - common files
 libmotif-dev - Motif - development files
 libmrm4    - Motif - MRM (Motif Resource Manager) shared library
 libuil4    - Motif - UIL (User Interface Language) shared library
 libxm4     - Motif - X/Motif shared library
 mwm        - Motif Window Manager
 uil        - Motif - UIL (User Interface Language) compiler
Closes: 870773
Changes:
 motif (2.3.7-2) unstable; urgency=medium
 .
   * Revert redefining yyleng in fix-type-inconsistencies.patch,
     thanks James Clarke (Closes: #870773)
   * Disable PIE on x32, thanks James Clarke
   * Bump Standards-Version to 4.1.0, no changes needed
Checksums-Sha1:
 8f4e97a1f121c0bcf7861393fd27ed2318bcfce2 2409 motif_2.3.7-2.dsc
 159b804432287df09cd255b8bb290ba40a824d15 51380 motif_2.3.7-2.debian.tar.xz
Checksums-Sha256:
 7c2b1d393384b4271cbcd38ca2220b100fe12997020bc29cf562ec052c58de6d 2409 
motif_2.3.7-2.dsc
 40adec87efb216f2adb5298ff57d5bd45edbeaa50e792de3d7b21c3b53662d71 51380 
motif_2.3.7-2.debian.tar.xz
Files:
 735f993d96dfac8a7368a80c532f0c79 2409 x11 optional motif_2.3.7-2.dsc
 2925dff8e2eeeb3d895077040dbf00d1 51380 x11 optional motif_2.3.7-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJZrmtsAAoJEK/P7I5mnOHCQtoQAIQD4cz8lU61/BWtCjog1wrL
YrggIGdnCJmcfaE2Lpy3QE92KiLq7gF75WHRvoKYiYp6Ji6B4MMptYn/uDj3T8rU
cHhORFM3FrMsrwyG1rEAsRZDQFqLolT8FPfJny4Djn7b7z5lH1A7HDODWwOTaupI
MeZoPGzzpLlLRoPLSVGJBa+X1y8RX7ppr7l4/TwxIWyGvdOfmJUcGcjT2FFFV69y
PZrBz4sGTB9ofAjPpR4qN3bvAbtSIM+p/HmVL5RlvqNNCIWSFoPaeXFePEojragU
6Jg34RpcPz1/gSm4P4zJiY627QEjDfhjiGIaEZgbUv6Hna8s6PDIAC/HIcSoAJ+C
af4gBKPQsxfiD/OWWLPLDAr64f9Oz1kuflsABhCRWwZfQVuDYWolw7x7wJwRZUEP
oixAkbn4EUZr6jdtbrcI8jfPSrfySbEfUVxMdK6U3ZhSs4DFNSGY0lqO64gKgck6
hziOdRt1BJ6f3JcR8hQUwP+FSuUlybcTBJOFuHnhU5Fsoufpr9rNMvG5rlLZpTQD
B/LrPt0tpZM5YwU512xT4Z/AlGnS7y+UJ7uNIRZ6gDtiOrBTRttYT9D0E1leDFTL
/qQsBGoRNNFVJWIITACMZFduYzY7Qehk8E+UBrWLMJv4MPOF2Wu313fXH5E9QhxN
oKbfkovzaXQEAe0EKXK0
=R8p0
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to