Bug#929682: libqt5qml5: QQmlEngine segfaults on ia64

[Jason Duerstock]

Investigating now.

On Wed, Jun 19, 2019 at 1:56 PM Dmitry Shachnev  wrote:

> Hi Jason!
>
> On Tue, May 28, 2019 at 11:58:38AM -0400, Jason Duerstock wrote:
> > As reported in bug #894726, qtdeclarative-opensource-src has a bug on
> > systems that use 64-bit pointers with any bits from 63-50 set.  The
> > attached patch addresses this issue on ia64 by shifting bits 63-61
> > (which are the "virtual region number" on ia64) into bits 49-47.  Please
> > include it in the next release.
>
> I have applied the patch (the version that was merged upstream), but
> unfortunately most of the tests are still failing.
>
> In the build log, I can count 149 FAIL!s and 42 Segmentation faults.
>
> It is much more than 57 failures you mentioned in the upstream bug [1].
> Looking at the log, *most* of the tests are failing. Passing ones are
> mostly the qmlMinify ones, which do not use the QML engine at all.
>
> Can you please look what happened there?
>
> [1]:
> https://bugreports.qt.io/browse/QTBUG-56264?focusedCommentId=462440#comment-462440
>
> --
> Dmitry Shachnev
>

Bug#930742: parted: fix MacOS boot support

[Jason Duerstock]

Source: parted
Severity: normal
Tags: patch

Dear Maintainer,

parted does not properly handle MacOS partitions.  The attached (from upstream) 
fixes this.

See 
http://git.savannah.gnu.org/cgit/parted.git/commit/?id=43b061e90dcdab799ecd1e822852de110673bf7e
for more detail.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable'), (1, 'experimental')
Architecture: ia64

Kernel: Linux 5.0.0-trunk-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/libparted/labels/mac.c b/libparted/labels/mac.c
index d8da941..fa4e43f 100644
--- a/libparted/labels/mac.c
+++ b/libparted/labels/mac.c
@@ -411,14 +411,14 @@ _rawpart_has_driver (const MacRawPartition* raw_part, 
MacDiskData* mac_disk_data
 {
MacDeviceDriver *driverlist;
uint16_t i;
-   uint32_t driver_bs, driver_be, part_be;
+   uint32_t start_block, block_count;
 
+   start_block = PED_BE32_TO_CPU(raw_part->start_block);
+   block_count = PED_BE32_TO_CPU(raw_part->block_count);
driverlist = _disk_data->driverlist[0];
for (i = 0; i < mac_disk_data->driver_count; i++) {
-   driver_bs = driverlist->block;
-   driver_be = driver_bs + driverlist->size;
-   part_be = raw_part->start_block + raw_part->block_count;
-   if (driver_bs >= raw_part->start_block && driver_be <= part_be)
+   if (start_block == PED_BE32_TO_CPU(driverlist->block) &&
+block_count == PED_BE16_TO_CPU(driverlist->size))
return 1;
driverlist++;
}
@@ -751,11 +751,12 @@ mac_read (PedDisk* disk)
if (!ped_disk_delete_all (disk))
goto error;
 
-   if (raw_disk->driver_count && raw_disk->driver_count < 62) {
+   if (PED_BE16_TO_CPU(raw_disk->driver_count) &&
+PED_BE16_TO_CPU(raw_disk->driver_count) < 62) {
memcpy(_disk_data->driverlist[0], _disk->driverlist[0],
sizeof(mac_disk_data->driverlist));
-   mac_disk_data->driver_count = raw_disk->driver_count;
-   mac_disk_data->block_size = raw_disk->block_size;
+   mac_disk_data->driver_count = 
PED_BE16_TO_CPU(raw_disk->driver_count);
+   mac_disk_data->block_size = 
PED_BE16_TO_CPU(raw_disk->block_size);
}
 
/* If _disk_analyse_block_size has increased the sector_size,
@@ -877,17 +878,16 @@ static void
 _update_driver_count (MacRawPartition* part_map_entry,
  MacDiskData *mac_driverdata, const MacDiskData* 
mac_disk_data)
 {
-   uint16_ti, count_orig, count_cur;
-   uint32_tdriver_bs, driver_be, part_be;
-
-   count_cur = mac_driverdata->driver_count;
-   count_orig = mac_disk_data->driver_count;
-   for (i = 0; i < count_orig; i++) {
-   driver_bs = mac_disk_data->driverlist[i].block;
-   driver_be = driver_bs + mac_disk_data->driverlist[i].size;
-   part_be = part_map_entry->start_block + 
part_map_entry->block_count;
-   if (driver_bs >= part_map_entry->start_block
-   && driver_be <= part_be) {
+   uint16_ti;
+   uint32_tstart_block, block_count;
+
+   start_block = PED_BE32_TO_CPU(part_map_entry->start_block);
+   block_count = PED_BE32_TO_CPU(part_map_entry->block_count);
+
+   for (i = 0; i < mac_disk_data->driver_count; i++) {
+   if (start_block == 
PED_BE32_TO_CPU(mac_disk_data->driverlist[i].block) &&
+   block_count == 
PED_BE16_TO_CPU(mac_disk_data->driverlist[i].size)) {
+   uint16_t count_cur = mac_driverdata->driver_count;
mac_driverdata->driverlist[count_cur].block
= mac_disk_data->driverlist[i].block;
mac_driverdata->driverlist[count_cur].size
@@ -934,7 +934,6 @@ _generate_raw_part (PedDisk* disk, PedPartition* part,
strncpy (part_map_entry->type, mac_part_data->system_name, 32);
 
if (mac_part_data->is_driver) {
-   mac_part_data->boot_region_length = part->geom.length;
if (mac_part_data->has_driver)
_update_driver_count(part_map_entry, mac_driverdata,
mac_disk_data);
@@ -1042,7 +1041,7 @@ write_block_zero (PedDisk* disk, MacDiskData* 
mac_driverdata)
raw_disk->block_size = PED_CPU_TO_BE16 (dev->sector_size);
raw_disk->block_count = PED_CPU_TO_BE32 (dev->length);
 
-   raw_disk->driver_count = mac_driverdata->driver_count;
+   raw_disk->driver_count = PED_CPU_TO_BE16(mac_driverdata->driver_count);
memcpy(_disk->driverlist[0], 

Bug#930119: gcc-8: __dso_handle place in wrong segment on ia64

[Jason Duerstock]

Package: gcc-8
Version: 8.3.0-7
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

On ia64, __dso_handle is placed in .data/.bss rather than .sdata/.sbss,
causing a link failure on at least one package (libphonenumber).  The
patch has been added to trunk here:

https://gcc.gnu.org/viewcvs/gcc?view=revision=271977

A PR has also been opened but for some reason does not reflect the trunk
change.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90714

Thank you.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 5.0.0-trunk-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-8 depends on:
ii  binutils  2.31.1-16
ii  cpp-8 8.3.0-7
ii  gcc-8-base8.3.0-7
ii  libc6.1   2.28-2
ii  libcc1-0  9-20190428-1
ii  libgcc-8-dev  8.3.0-7
ii  libgcc1   1:9-20190428-1
ii  libgmp10  2:6.1.2+dfsg-4
ii  libisl19  0.20-2
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.2-1
ii  libstdc++69-20190428-1
ii  libunwind81.2.1-9
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages gcc-8 recommends:
ii  libc6.1-dev  2.28-2

Versions of packages gcc-8 suggests:
pn  gcc-8-doc 
pn  gcc-8-locales 
pn  libasan5-dbg  
pn  libatomic1-dbg
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan1-dbg 

-- no debconf information

Bug#930082: gmt: FTBFS on ia64

[Jason Duerstock]

Source: gmt
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

gmt fails to build from source on ia64.  A patch has been submitted
upstream:

https://github.com/GenericMappingTools/gmt/pull/849

Please include it in your next release.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 5.0.0-trunk-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/src/common_sighandler.c b/src/common_sighandler.c
index f1825595d..42ca21c98 100644
--- a/src/common_sighandler.c
+++ b/src/common_sighandler.c
@@ -106,6 +106,8 @@ void backtrace_symbols_fd(void *const *buffer, int size, 
int fd) {
 #  define UC_IP(uc) ((void *) (uc)->uc_mcontext.arm_pc)
 # elif defined(__powerpc__) || defined(__powerpc64__)
 #  define UC_IP(uc) ((void *) (uc)->uc_mcontext.regs->nip)
+# elif defined(__ia64__)
+#  define UC_IP(uc) ((void *) (uc)->uc_mcontext.sc_ip)
 # else
 #  define UC_IP(uc) ((void *) (uc)->uc_mcontext.eip)
 # endif

Bug#929975: python-numpy: move python3-matplotlib dependency to depend-indep

[Jason Duerstock]

Package: python-numpy
Version: 1:1.16.2-1
Severity: normal
Tags: patch

Dear Maintainer,

The build dependency on python3-matplotlib creates an unnecessary build
dependency loop.  I believe the attached patch fixes the packaging so
that python3-matplotlib is only required when building the
documentation.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 5.0.0-trunk-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python-numpy depends on:
ii  libblas3 [libblas.so.3]  3.8.0-2
ii  libc6.1  2.28-2
ii  liblapack3 [liblapack.so.3]  3.8.0-2
ii  libunwind8   1.2.1-9
ii  python   2.7.15-4
ii  python-pkg-resources 40.8.0-1
ii  python2.72.7.16-2

python-numpy recommends no packages.

Versions of packages python-numpy suggests:
ii  gcc   4:8.3.0-1
ii  gfortran  4:8.3.0-1
ii  python-dev2.7.15-4
ii  python-numpy-dbg  1:1.16.2-1
pn  python-numpy-doc  
ii  python-pytest 3.10.1-2

-- no debconf information
--- a/debian/control2019-03-02 11:30:12.0 -0500
+++ b/debian/control2019-06-04 00:44:33.681266367 -0400
@@ -3,6 +3,7 @@
 Priority: optional
 Maintainer: Sandro Tosi 
 Uploaders: Debian Python Modules Team 

+Build-Depends-Indep: python3-matplotlib
 Build-Depends: cython (>= 0.26-2.1),
debhelper (>= 11),
dh-python,
@@ -15,7 +16,6 @@
python-all-dev,
python3-all-dev,
python-docutils,
-   python3-matplotlib,
python-pytest,
python3-pytest,
python-setuptools,
--- a/debian/rules  2019-03-02 11:30:12.0 -0500
+++ b/debian/rules  2019-06-04 00:39:11.123434195 -0400
@@ -25,6 +25,7 @@
python$$v-dbg setup.py build; \
done
 
+override_dh_auto_build-indep:
# build doc only for default python version
(export MPLCONFIGDIR=. ; make -C doc html PYTHON=python3 
PYTHONPATH=../$(PY3LIBPATH))
 

Bug#929682: libqt5qml5: QQmlEngine segfaults on ia64

[Jason Duerstock]

Source: qtdeclarative-opensource-src
Severity: important
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

As reported in bug #894726, qtdeclarative-opensource-src has a bug on
systems that use 64-bit pointers with any bits from 63-50 set.  The
attached patch addresses this issue on ia64 by shifting bits 63-61
(which are the "virtual region number" on ia64) into bits 49-47.  Please
include it in the next release.

Thank you.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 5.0.0-trunk-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- a/src/qml/jsruntime/qv4value_p.h2019-05-24 21:55:24.436238822 -0400
+++ b/src/qml/jsruntime/qv4value_p.h2019-05-24 22:08:26.832635233 -0400
@@ -146,12 +146,24 @@
 QML_NEARLY_ALWAYS_INLINE Heap::Base *m() const
 {
 Heap::Base *b;
-memcpy(, &_val, 8);
+#ifdef __ia64
+   quint64 _tmp;
+
+   _tmp = _val & 0x0001c000;
+   _tmp = (_tmp << 14) | (_val ^ _tmp);
+   memcpy(, &_tmp, 8);
+#else
+   memcpy(, &_val, 8);
+#endif
 return b;
 }
 QML_NEARLY_ALWAYS_INLINE void setM(Heap::Base *b)
 {
 memcpy(&_val, , 8);
+#ifdef __ia64
+   _val |= ((_val & 0xa000) >> 14);
+   _val &= 0x0001;
+#endif
 }
 #elif QT_POINTER_SIZE == 4
 QML_NEARLY_ALWAYS_INLINE Heap::Base *m() const

Bug#929326: subversion: please add pkg.subversion.nokde build profile

[Jason Duerstock]

Source: subversion
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

Subversion currently depends on KDE in order to build, which creates an
excessive build dependency chain.  Please accept the following patch
which adds a pkg.subversion.nokde build profile that removes the KDE
dependency requirement.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.19.0-5-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- debian/control  2019-05-21 14:32:14.938904862 -0400
+++ debian/control  2019-05-21 14:32:25.070975575 -0400
@@ -17,9 +17,9 @@
libdb5.3-dev,
libdbus-1-dev,
liblz4-dev (>= 0.0~r129),
-   libkf5coreaddons-dev,
-   libkf5i18n-dev,
-   libkf5wallet-dev,
+   libkf5coreaddons-dev ,
+   libkf5i18n-dev ,
+   libkf5wallet-dev ,
libperl-dev,
libsasl2-dev,
libsecret-1-dev,
--- debian/rules2019-05-21 14:32:09.770868795 -0400
+++ debian/rules2019-05-21 14:32:20.826945955 -0400
@@ -89,7 +89,6 @@
--with-editor=/usr/bin/editor \
--with-ruby-sitedir=/usr/lib/ruby \
--with-swig=/usr/bin/swig \
-   --with-kwallet=/usr/include:$(libdir) \
--with-lz4 \
--with-utf8proc \
CFLAGS="$(CFLAGS)" \
@@ -102,6 +101,10 @@
   confflags+= --enable-debug
 endif
 
+ifeq ($(filter pkg.subversion.nokde,$(DEB_BUILD_PROFILES)),)
+  confflags+= --with-kwallet=/usr/include:$(libdir)
+endif
+
 export DH_OPTIONS
 ifdef DEB_OPT_WITH_JAVAHL
   # jikes 1.22 cannot compile javahl.

Bug#929311: gcc-9: please include fix for pr87338

[Jason Duerstock]

Package: gcc-9
Version: 9-20190428-1
Severity: normal
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

Please include the fix for pr87338 that was previously included in
gcc-8.  This patch is required for gcc-9 to build under ia64.

Thank you.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.19.0-5-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-9 depends on:
ii  binutils  2.31.1-16
ii  cpp-9 9-20190428-1
ii  gcc-9-base9-20190428-1
ii  libc6.1   2.28-2
ii  libcc1-0  9-20190428-1
ii  libgcc-9-dev  9-20190428-1
ii  libgmp10  2:6.1.2+dfsg-4
ii  libisl19  0.20-2
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.2-1
ii  libstdc++69-20190428-1
ii  libunwind81.2.1-9
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages gcc-9 recommends:
ii  libc6.1-dev  2.28-2

Versions of packages gcc-9 suggests:
pn  gcc-9-doc 
pn  gcc-9-locales 
pn  libasan5-dbg  
pn  libatomic1-dbg
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan1-dbg 

-- no debconf information

Bug#929244: mozjs60: FTBFS on ia64

[Jason Duerstock]

Package: mozjs60
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

The attached patch fixes the build problems for mozjs60 on ia64.  Please
apply.  Thank you.


-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.19.0-5-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- a/js/src/jit/AtomicOperations.h 2019-05-16 23:15:54.589637251 -0400
+++ b/js/src/jit/AtomicOperations.h 2019-05-16 23:16:37.545944927 -0400
@@ -387,6 +387,8 @@
 # include "jit/none/AtomicOperations-feeling-lucky.h"
 #elif defined(__s390__) || defined(__s390x__)
 # include "jit/none/AtomicOperations-feeling-lucky.h"
+#elif defined(__ia64__)
+# include "jit/none/AtomicOperations-feeling-lucky.h"
 #else
 # error "No AtomicOperations support provided for this platform"
 #endif
--- a/js/src/jit/none/AtomicOperations-feeling-lucky.h  2018-10-04 
20:47:07.0 -0400
+++ b/js/src/jit/none/AtomicOperations-feeling-lucky.h  2019-05-16 
23:42:47.269079252 -0400
@@ -79,6 +79,12 @@
 #  define GNUC_COMPATIBLE
 #endif
 
+#ifdef __ia64__
+#  define HAS_64BIT_ATOMICS
+#  define HAS_64BIT_LOCKFREE
+#  define GNUC_COMPATIBLE
+#endif
+
 // The default implementation tactic for gcc/clang is to use the newer
 // __atomic intrinsics added for use in C++11 .  Where that
 // isn't available, we use GCC's older __sync functions instead.
--- a/js/src/tests/jstests.list 2019-05-17 10:49:25.666015230 -0400
+++ b/js/src/tests/jstests.list 2019-05-17 10:52:19.211281661 -0400
@@ -473,6 +473,11 @@
 # Crashes
 skip-if(xulRuntime.debian.DEB_HOST_ARCH.match(/^s390x$/)) script 
non262/extensions/clone-errors.js
 
+# Fails on ia64, possibly due to ia64 glibc bugs
+skip-if(xulRuntime.debian.DEB_HOST_ARCH.match(/^ia64$/)) script 
non262/Math/fround.js
+skip-if(xulRuntime.debian.DEB_HOST_ARCH.match(/^ia64$/)) script 
non262/Math/log2-approx.js
+
+
 ###
 # Tests disabled due to issues in test262 importer script #
 ###

Bug#890279: gzip (i386) uses TEXTRELs

[Jason Duerstock]

As I believe this would fix
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688958, I say go
ahead.

Jason
On Thu, Sep 27, 2018 at 6:37 AM Andreas Henriksson  wrote:
>
> Hello,
>
> I've just built gzip in a i386 chroot with the previously supplied
> debdiff applied and checked with scanelf (from pax-utils) that the
> textrel goes away.
>
> # scanelf -t noasm/bin/* /bin/gzip
> TYPE   TEXTREL FILE
>  ET_DYN-noasm/bin/gzip
>  ET_DYN TEXTREL /bin/gzip
>
> Andreas Pommer: It would be great if you could verify that
> gzip built with the patch you find at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=890279;filename=gzip-no-asm.debdiff;msg=21
> (ie. attached to #890279 ) makes it possible for you to reenable the
> protection in the logrotate service file that Christian had to drop
> for you. (Either by downgrading to previous logrotate version or
> just systemctl edit and put the service changes back in again.)
>
> m68k and ia64 porters: Please note that gzip seems to have asm code for
> your architectures as well which gets disabled by the proposed patch.
> Please speak up now if you think the asm for your architecture is better
> and should be preferred over the C code.
> Previous discussion quoted below to give you some background. See
> #890279 for entire discussion.
>
> Given the lack of feedback on this issue, I assume NMU will be the next
> step here unless I get any feedback soon after this message.
>
> Regards,
> Andreas Henriksson
>
>
> On Wed, Aug 29, 2018 at 12:11:20PM +0200, Andreas Henriksson wrote:
> > Hi,
> >
> > There are some useful info in the discussion at:
> > https://launchpad.net/ubuntu/+source/gzip/+bug/49067
> >
> > Apparently fedora (et.al.) has nowadays abandoned their patch in favour
> > of using 'export DEFS="NO_ASM"' in the spec file, see
> > https://src.fedoraproject.org/rpms/gzip/tree/master
> >
> > Their changelog also comes with this interesting claim:
> > "- don't use the asm code again as it's slower than the gcc compiled one"
> >
> > Googling "gzip DEFS NO_ASM" gives a number of matches including
> > openembedded, coreos, etc.
> > It seems it's pretty common to disable the (i386) assembler code
> > and given the benefits it seems to have, I think it would be
> > useful for debian to also do that.
> >
> > For potential convenience I'm attaching an untested debdiff which I
> > hope someone can help test and verify on i386.
> >
> > Regards,
> > Andreas Henriksson
> >
> > PS. Please also note fedora seems to be carrying a patch for glibc 2.28
> > which might be useful in debian soon as well.
> > https://src.fedoraproject.org/rpms/gzip/blob/master/f/gnulib.patch
>
> > diff -Nru gzip-1.9/debian/changelog gzip-1.9/debian/changelog
> > --- gzip-1.9/debian/changelog 2018-08-05 02:30:09.0 +0200
> > +++ gzip-1.9/debian/changelog 2018-08-29 11:40:01.0 +0200
> > @@ -1,3 +1,11 @@
> > +gzip (1.9-2.1) UNRELEASED; urgency=medium
> > +
> > +  * Non-maintainer upload.
> > +  * Disable usage of assembler code (Closes: #890279)
> > +- fedora claims gcc generates more optimized code anyway.
> > +
> > + -- Andreas Henriksson   Wed, 29 Aug 2018 11:40:01 +0200
> > +
> >  gzip (1.9-2) unstable; urgency=medium
> >
> >* move to upstream's less-ugly fix for mingw compilation failure
> > diff -Nru gzip-1.9/debian/rules gzip-1.9/debian/rules
> > --- gzip-1.9/debian/rules 2018-08-05 02:30:09.0 +0200
> > +++ gzip-1.9/debian/rules 2018-08-29 11:40:01.0 +0200
> > @@ -24,6 +24,7 @@
> >  endif
> >  endif
> >
> > +export DEFS=NO_ASM # Avoid TEXTRELs on i386
> >  EXTRA_CFLAGS=-Wall
> >  EXTRA_CPPFLAGS=
> >
>

Bug#906822: Acknowledgement (gdb: gdb FTBFS on ia64)

[Jason Duerstock]

Sorry, I included the wrong patch.  This is the correct one:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=5a6c3296a7a90694ad4042f6256f3da6d4fa4ee8
On Tue, Aug 21, 2018 at 11:36 AM Debian Bug Tracking System
 wrote:
>
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 906822: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906822.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   debian-i...@lists.debian.org
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Héctor Orón Martínez 
>
> If you wish to submit further information on this problem, please
> send it to 906...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 906822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906822
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#908519: linux: asciidoctor dependency blocks ia64 build

[Jason Duerstock]

Source: linux
Severity: normal
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

Due to some ruby issues, asciidoctor is currently blocking the linux
package from building on ia64.  Since asciidoctor is only used to build
the linux-perf documentation, does it make more sense to:
1) move asciidoctor into the Build-Depends-Indep: section in the control
file, or
2) flag asciidoctor as [!ia64]?

I think #1 is the correct answer, but it's entirely possible my
understanding of build dependencies is incomplete.

Thanks,

Jason


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.18.0-1-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#906822: gdb: gdb FTBFS on ia64

[Jason Duerstock]

Package: gdb
Version: 7.12-6+ia64.1
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

gdb 8.1 FTBFS on ia64 because an internal API change was not fully
propagated across all callers.  This is fixed in upstream git commit
5d691c8829d0e5c4c4b9cfb147c8a873ce18085b, which is included here for
your convenience.

Jason


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.17.0-3-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gdb depends on:
ii  libc6.1   2.27-5
ii  libexpat1 2.2.6-1
ii  liblzma5  5.2.2-1.3+b1
ii  libncurses5   6.1+20180714-1
ii  libpython3.6  3.6.6-2
ii  libreadline7  7.0-5
ii  libtinfo5 6.1+20180714-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages gdb recommends:
ii  libc6.1-dbg [libc-dbg]  2.27-5

Versions of packages gdb suggests:
pn  gdb-doc
pn  gdbserver  

-- no debconf information
diff --git a/gdb/ia64-tdep.c b/gdb/ia64-tdep.c
index 0df62e26ab..2fab60c1d0 100644
--- a/gdb/ia64-tdep.c
+++ b/gdb/ia64-tdep.c
@@ -69,6 +69,7 @@ struct ia64_table_entry
   };
 
 static struct ia64_table_entry *ktab = NULL;
+static gdb::optional ktab_buf;
 
 #endif
 
@@ -2647,11 +2648,9 @@ ia64_access_mem (unw_addr_space_t as,
 }
 
 /* Call low-level function to access the kernel unwind table.  */
-static LONGEST
-getunwind_table (gdb_byte **buf_p)
+static gdb::optional
+getunwind_table ()
 {
-  LONGEST x;
-
   /* FIXME drow/2005-09-10: This code used to call
  ia64_linux_xfer_unwind_table directly to fetch the unwind table
  for the currently running ia64-linux kernel.  That data should
@@ -2660,10 +2659,8 @@ getunwind_table (gdb_byte **buf_p)
  we should find a way to override the corefile layer's
  xfer_partial method.  */
 
-  x = target_read_alloc (current_top_target (), TARGET_OBJECT_UNWIND_TABLE,
-NULL, buf_p);
-
-  return x;
+  return target_read_alloc (current_top_target (), TARGET_OBJECT_UNWIND_TABLE,
+   NULL);
 }
 
 /* Get the kernel unwind table.  */ 
@@ -2674,15 +2671,12 @@ get_kernel_table (unw_word_t ip, unw_dyn_info_t *di)
 
   if (!ktab) 
 {
-  gdb_byte *ktab_buf;
-  LONGEST size;
-
-  size = getunwind_table (_buf);
-  if (size <= 0)
+  ktab_buf = getunwind_table ();
+  if (!ktab_buf)
return -UNW_ENOINFO;
 
-  ktab = (struct ia64_table_entry *) ktab_buf;
-  ktab_size = size;
+  ktab = (struct ia64_table_entry *) ktab_buf->data ();
+  ktab_size = ktab_buf->size ();
 
   for (etab = ktab; etab->start_offset; ++etab)
 etab->info_offset += KERNEL_START;

Bug#905536: closed by Matthias Klose (Bug#905536: fixed in python3.7 3.7.0-5)

[Jason Duerstock]

The patch appears to not have actually been applied in 3.7.0-5.  Can you
double check this please?

Thanks,

Jason

On Mon, Aug 20, 2018 at 3:51 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the src:python3.7 package:
>
> #905536: python3.7: disable -O3 on ia64 due to compiler bug
>
> It has been closed by Matthias Klose .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Matthias Klose <
> d...@debian.org> by
> replying to this email.
>
>
> --
> 905536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905536
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Matthias Klose 
> To: 905536-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 20 Aug 2018 19:49:55 +
> Subject: Bug#905536: fixed in python3.7 3.7.0-5
> Source: python3.7
> Source-Version: 3.7.0-5
>
> We believe that the bug you reported is fixed in the latest version of
> python3.7, 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 905...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Matthias Klose  (supplier of updated python3.7 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 ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Mon, 20 Aug 2018 19:52:20 +0200
> Source: python3.7
> Binary: python3.7 python3.7-venv libpython3.7-stdlib python3.7-minimal
> libpython3.7-minimal libpython3.7 python3.7-examples python3.7-dev
> libpython3.7-dev libpython3.7-testsuite idle-python3.7 python3.7-doc
> python3.7-dbg libpython3.7-dbg
> Architecture: source
> Version: 3.7.0-5
> Distribution: unstable
> Urgency: medium
> Maintainer: Matthias Klose 
> Changed-By: Matthias Klose 
> Description:
>  idle-python3.7 - IDE for Python (v3.7) using Tkinter
>  libpython3.7 - Shared Python runtime library (version 3.7)
>  libpython3.7-dbg - Debug Build of the Python Interpreter (version 3.7)
>  libpython3.7-dev - Header files and a static library for Python (v3.7)
>  libpython3.7-minimal - Minimal subset of the Python language (version 3.7)
>  libpython3.7-stdlib - Interactive high-level object-oriented language
> (standard library
>  libpython3.7-testsuite - Testsuite for the Python standard library (v3.7)
>  python3.7  - Interactive high-level object-oriented language (version 3.7)
>  python3.7-dbg - Debug Build of the Python Interpreter (version 3.7)
>  python3.7-dev - Header files and a static library for Python (v3.7)
>  python3.7-doc - Documentation for the high-level object-oriented language
> Python
>  python3.7-examples - Examples for the Python language (v3.7)
>  python3.7-minimal - Minimal subset of the Python language (version 3.7)
>  python3.7-venv - Interactive high-level object-oriented language (pyvenv
> binary, v
> Closes: 902788 905536
> Changes:
>  python3.7 (3.7.0-5) unstable; urgency=medium
>  .
>* Update to 20180820 from the 3.7 branch.
>* Avoid usage of distutils in the platform module. See issue #26544.
>* Fix some issues on architectures from the computer museum (Jason
> Duerstock).
>  Closes: #905536.
>  - Disable -O3 on ia64 (see PR rtl-optimization/85412).
>  - Remove the -O2 override on m68k (see Debian #326903).
>  - Remove the -mieee and -O2 overrides for DEC Alpha (see Debian
> #212912).
>* Add more breaks for packages not compatible with Python 3.7:
>  - python3-aiomeasures. See #906159.
>  - python3-motor (updated). See #903527.
>* Again close the RC issue about the syntax errors triggered by Python
> 3.7.
>  Closes: #902788.
>* Update symbols files.
> Checksums-Sha1:
>  c1b685de02b97c3540a94b97bd0f8d1dff89e30f 3424 python3.7_3.7.0-5.dsc
>  8da303b6e87587d4d7e234436f5f8e0c36eada0b 370660
> python3.7_3.7.0-5.debian.tar.xz
>  3b45fb308d1fffa315e84f88fdc4822a5f55a005 9404
> python3.7_3.7.0-5_source.buildinfo
> Checksums-Sha256:
>  90eff7180a5d8c71023bd10d9d429a96da6b3fdcf30146e769f49341c88e63b0 3424
> python3.7_3.7.0-5.dsc
>  88f392b012

Bug#906675: gcc-8: remove obsolete ia64 gcc bug workaround

[Jason Duerstock]

Package: gcc-8
Version: 8.1.0-9
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

The debian/rules2 file has an obsolete compiler bug workaround that can
now be removed.  The attached patch removes it.  Please include it in
the next release.

Thank you.


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.17.0-3-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-8 depends on:
ii  binutils  2.31.1-4
ii  cpp-8 8.1.0-9
ii  gcc-8-base8.1.0-9
ii  libc6.1   2.27-5
ii  libcc1-0  8.1.0-9
ii  libgcc-8-dev  8.1.0-9
ii  libgcc1   1:8.1.0-9
ii  libgmp10  2:6.1.2+dfsg-3
ii  libisl19  0.20-2
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.1-1
ii  libstdc++68.1.0-9
ii  libunwind81.2.1-8
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages gcc-8 recommends:
ii  libc6.1-dev  2.27-5

Versions of packages gcc-8 suggests:
pn  gcc-8-doc 
pn  gcc-8-locales 
pn  libasan5-dbg  
pn  libatomic1-dbg
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan1-dbg 

-- no debconf information
--- debian/rules2.orig  2018-08-19 09:56:05.076926333 -0400
+++ debian/rules2   2018-08-19 09:56:16.232982161 -0400
@@ -120,11 +120,6 @@
   endif
 endif
 
-# work around PR 57689
-ifeq ($(DEB_TARGET_ARCH),ia64)
-  BOOT_CFLAGS  = -g -O1
-endif
-
 ifeq ($(with_ssp_default),yes)
   STAGE1_CFLAGS= -g
   ifeq (,$(BOOT_CFLAGS))

Bug#906531: qtdeclarative-opensource-src: libqt5qml5.symbols and libqt5quick5.symbols need update for ia64

[Jason Duerstock]

Source: qtdeclarative-opensource-src
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

The source currently fails to build because of some symbol
inconsistencies.  The attached patch should fix them.


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.17.0-3-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- qtdeclarative-opensource-src-5.11.1/debian/libqt5quick5.symbols 
2018-07-26 21:08:31.0 -0400
+++ qtdeclarative-opensource-src-5.11.1.new/debian/libqt5quick5.symbols 
2018-08-17 16:30:51.207202160 -0400
@@ -3296,7 +3296,7 @@
  
_ZN36QQuickDesignerSupportPropertyChanges15detachFromStateEP7QObject@Qt_5_PRIVATE_API
 5.6.0~beta 1
  
_ZN36QQuickDesignerSupportPropertyChanges16changeExpressionEP7QObjectRK10QByteArrayRK7QString@Qt_5_PRIVATE_API
 5.6.0~beta 1
  
_ZN36QQuickDesignerSupportPropertyChanges16isNormalPropertyERK10QByteArray@Qt_5_PRIVATE_API
 5.6.0~beta 1
- (optional=templinst|arch=alpha mips64el riscv64 
sparc64)_ZN3QV45Value2asINS_6ObjectEEEPT_v@Qt_5 5.9.1
+ (optional=templinst)_ZN3QV45Value2asINS_6ObjectEEEPT_v@Qt_5 5.9.1
  _ZN40QSGDistanceFieldShiftedStyleTextMaterialC1Ev@Qt_5_PRIVATE_API 5.0.2 1
  _ZN40QSGDistanceFieldShiftedStyleTextMaterialC2Ev@Qt_5_PRIVATE_API 5.0.2 1
  _ZN40QSGDistanceFieldShiftedStyleTextMaterialD0Ev@Qt_5_PRIVATE_API 5.0.2 1
--- qtdeclarative-opensource-src-5.11.1/debian/libqt5qml5.symbols   
2018-07-26 21:08:17.0 -0400
+++ qtdeclarative-opensource-src-5.11.1.new/debian/libqt5qml5.symbols   
2018-08-17 20:29:36.086200229 -0400
@@ -2631,7 +2631,7 @@
  _ZNK3QV45Value16toQStringNoThrowEv@Qt_5_PRIVATE_API 5.2.0~beta1 1
  _ZNK3QV45Value8toUInt16Ev@Qt_5_PRIVATE_API 5.2.0~beta1 1
  _ZNK3QV45Value9sameValueES0_@Qt_5_PRIVATE_API 5.2.0~beta1 1
- (arch=!amd64 !arm64 !mips64el !ppc64el 
!sparc64)_ZNK3QV45Value9toIntegerEv@Qt_5_PRIVATE_API 5.11.1 1
+ (arch=!amd64 !arm64 !ia64 !mips64el !ppc64el 
!sparc64)_ZNK3QV45Value9toIntegerEv@Qt_5_PRIVATE_API 5.11.1 1
  _ZNK3QV45Value9toQStringEv@Qt_5_PRIVATE_API 5.2.0~beta1 1
  
_ZNK3QV46Object11getPropertyEjPNS_8PropertyEPNS_18PropertyAttributesE@Qt_5_PRIVATE_API
 5.6.0~beta 1
  _ZNK3QV46Object11hasPropertyEPNS_6StringE@Qt_5_PRIVATE_API 5.4.0 1

Bug#905536: python3.7: disable -O3 on ia64 due to compiler bug

[Jason Duerstock]

Source: python3.7
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

The attached patch includes a number of fixes to python3.7's
debian/rules:
1) Due to a gcc bug[1], -O3 needs to be disabled on ia64.
2) The -O2 override for m68k added for Debian bug #326903 is
no longer needed, and was removed
3) The -mieee and -O2 overrides for DEC Alpha added for Debian
bug #212912 are no longer needed, and were removed

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85412

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.17.0-1-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- debian/rules.orig   2018-08-05 13:09:54.027342191 -0400
+++ debian/rules2018-08-05 13:12:50.900361875 -0400
@@ -160,14 +160,9 @@
 OPT_CFLAGS   := $(filter-out -O%,$(DPKG_CFLAGS)) # default is -O3
 DEBUG_CFLAGS := $(patsubst -O%,-Og,$(DPKG_CFLAGS))
 
-# on alpha, use -O2 only, use -mieee
-ifeq ($(DEB_HOST_ARCH),alpha)
-OPT_CFLAGS += -mieee
-DEBUG_CFLAGS += -mieee
-EXTRA_OPT_FLAGS += -O2
-endif
-ifeq ($(DEB_HOST_ARCH),m68k)
-EXTRA_OPT_FLAGS += -O2
+# on ia64, disable -O3 until gcc bug #85412 is fixed
+ifeq ($(DEB_HOST_ARCH),ia64)
+EXTRA_OPT_CFLAGS += -O2
 endif
 ifneq (,$(filter $(DEB_HOST_ARCH), ppc64 ppc64el))
 OPT_CFLAGS += -fexceptions

Bug#905461: ia64: architecture is incompatible with CONFIG_SCHED_STACK_END_CHECK

[Jason Duerstock]

Source: linux
Severity: normal

On ia64, enabling the CONFIG_SCHED_STACK_END_CHECK kernel option renders the 
kernel unbootable.
The "stack end" magic number that is set to enable this feature is overwritten 
by the ia64 processor backing store.
Is it possible to override a global kernel setting in the arch config file?

Thanks,

Jason

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 4.17.0-1-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#902961: mozjs52: FTBFS in recent unstable: ReserveProcessExecutableMemory() fails during tests

[Jason Duerstock]

I suspect the "right" solution to this is to define the "base" and
"mask" variables in ComputeRandomAllocationAddress() based on what
works for each architecture, but my enthusiasm for gathering that
information was pretty low at the time I ran into this, and hasn't
gone up much since then.
On Tue, Jul 3, 2018 at 7:54 PM Simon McVittie  wrote:
>
> Source: mozjs52
> Version: 52.3.1-8
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> (X-Debbugs-Cc to contributors to #897178, to which this seems related,
> and #902197)
>
> After fixing #902197, the mozjs52 build-time tests failed on the amd64
> Debian porterbox barriere. Specifically, the smoke-test in debian/test.sh
> that's run before trying the actual test suite:
>
> "$SRCDIR/js/src/js" -e 'print("Hello, world")'
>
> fails, with js exiting 1.
>
> Running it under gdb reveals that this is because
> ReserveProcessExecutableMemory() in js/src/jit/ProcessExecutableMemory.cpp
> fails during startup, causing JS_Init() to fail. js helpfully has no
> diagnostics at all for this, it just silently exits with EXIT_FAILURE.
> (Ignore the first implementation of ReserveProcessExecutableMemory(),
> which is for Windows; the Unix implementation is around line 300.)
>
> That function gets a random address, and passes it as the first argument
> of mmap(., 1 gigabyte, PROT_NONE, MAP_PRIVATE | MAP_ANON, -1, 0) on
> 64-bit machines, or the same but with 128M instead of 1G on 32-bit.
> This now seems to be failing and returning NULL.
>
> I was surprised to find that on the same machine, if I install gjs (a
> GNOME wrapper around mozjs) and the slightly older mozjs 52.3.1-7 that it
> depends on, gjs-console -c 'print("hello")' works OK. (We don't package
> mozjs' own command-line tool 'js' any more, so no precompiled copy is
> available.) The changes between 52.3.1-7 and what I'm compiling all seem
> to be specific to non-amd64 architectures, so maybe this is about the
> environment in which mozjs was built, rather than the source code used?
>
> A hack that works to avoid this is to retry the mmap() without the address
> hint, like in Jason Duerstock's debian/patches/ia64-support.patch,
> but for non-IA64 architectures as well; see attached. I suspect this
> might be the wrong solution, but perhaps it points someone who knows
> this better than I do in the direction of a better solution...
>
> This also makes me wonder whether the failure addressed by
> ia64-support.patch was in fact a generic issue with newer $something
> (kernel? compiler? dpkg-buildflags?), which happened to only be seen
> by ia64 porters because everyone else was compiling and testing mozjs52
> with an older $something?
>
> smcv

Bug#897178: mozjs52: more fixes for ia64

[Jason Duerstock]

Source: mozjs52
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

Attached please find patches to let mozjs52 build on ia64, and (mostly) pass 
the test suite.
ia64 currently requires -G0 for linking, but crashes if the current 
*MAINT_APPEND strings are
used.  Also, the memory allocation fails because the address space randomizer 
does not
take into account ia64 memory allocation.


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- debian/test.sh.orig 2018-04-29 08:55:47.958055376 -0400
+++ debian/test.sh  2018-04-29 08:59:29.181143034 -0400
@@ -28,6 +28,9 @@
(s390x|ppc64)
echo "Ignoring test failure, 
https://bugs.debian.org/878286;
;;
+   (ia64)
+   echo "Ignoring test failure, 
https://bugs.debian.org/897117;
+   ;;
(*)
echo "Test failure is considered serious, causing FTBFS"
exit 1
--- debian/rules.orig   2018-04-29 09:00:41.632848488 -0400
+++ debian/rules2018-04-29 09:02:53.504307305 -0400
@@ -17,8 +17,15 @@
 SRCDIR = $(CURDIR)/js/src
 CONFIGURE_FLAGS =
 
-DEB_CFLAGS_MAINT_APPEND += -fno-schedule-insns2 -fno-lifetime-dse 
-fno-delete-null-pointer-checks
-DEB_CXXFLAGS_MAINT_APPEND += -fno-schedule-insns2 -fno-lifetime-dse 
-fno-delete-null-pointer-checks
+# ia64 currently has toolchain issues, so relax the link optimization
+# -fno-schedule-insns2 breaks gcc on ia64, so leave it enabled
+ifneq (,$(findstring $(DEB_BUILD_ARCH),ia64))
+   DEB_CFLAGS_MAINT_APPEND += -G0
+   DEB_CXXFLAGS_MAINT_APPEND += -G0
+else
+   DEB_CFLAGS_MAINT_APPEND += -fno-schedule-insns2 -fno-lifetime-dse 
-fno-delete-null-pointer-checks
+   DEB_CXXFLAGS_MAINT_APPEND += -fno-schedule-insns2 -fno-lifetime-dse 
-fno-delete-null-pointer-checks
+endif
 ifneq (,$(findstring $(DEB_BUILD_ARCH),armel armhf))
 DEB_CFLAGS_MAINT_APPEND += -fno-schedule-insns
 DEB_CXXFLAGS_MAINT_APPEND += -fno-schedule-insns
--- mozjs52-52.3.1/js/src/jit/ProcessExecutableMemory.cpp   2017-08-08 
06:25:50.0 -0400
+++ mozjs52.fixed/js/src/jit/ProcessExecutableMemory.cpp2018-04-27 
09:30:47.390494330 -0400
@@ -290,8 +290,13 @@
 void* randomAddr = ComputeRandomAllocationAddress();
 void* p = MozTaggedAnonymousMmap(randomAddr, bytes, PROT_NONE, MAP_PRIVATE 
| MAP_ANON,
  -1, 0, "js-executable-memory");
-if (p == MAP_FAILED)
-return nullptr;
+if (p == MAP_FAILED) {
+// the comment above appears to be incorrect, so retry without the hint
+p = MozTaggedAnonymousMmap(NULL, bytes, PROT_NONE, MAP_PRIVATE | 
MAP_ANON,
+ -1, 0, "js-executable-memory");
+if (p == MAP_FAILED) 
+return nullptr;
+}
 return p;
 }
 

Bug#897117: mozjs52: tests fail on ia64: memory and math

[Jason Duerstock]

Source: mozjs52
Severity: normal
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

The following tests fail on ia64:

## ecma_6/Math/log2-approx.js: rc = 3, run time = 0.109967
ecma_6/Math/shell.js:7:19 Error: got -Infinity, expected a number near -1074
Stack:
  fail@ecma_6/Math/shell.js:7:19
  assertNear@ecma_6/Math/shell.js:61:17
  @ecma_6/Math/log2-approx.js:2:5
TEST-UNEXPECTED-FAIL | ecma_6/Math/log2-approx.js | (args: "")

## ecma_6/Math/fround.js: rc = 3, run time = 0.111898
ecma_6/Math/fround.js:65:1 Error: Assertion failed: got 0, expected 5e-324
Stack:
  @ecma_6/Math/fround.js:65:1
TEST-UNEXPECTED-FAIL | ecma_6/Math/fround.js | (args: "")

## js1_5/Regress/regress-422348.js: rc = 0, run time = 0.101824
BUGNUMBER: 422348
STATUS: Proper overflow error reporting
 FAILED! [reported from test()] Proper overflow error reporting : Expected 
value 'InternalError: allocation size overflow', Actual v
alue 'out of memory'
TEST-UNEXPECTED-FAIL | js1_5/Regress/regress-422348.js | (args: "")

## js1_5/Array/regress-157652.js: rc = 0, run time = 0.110511
BUGNUMBER: 157652
STATUS: Testing that Array.sort() doesn't crash on very large arrays
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 0 ---
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 5 ---
 FAILED! [reported from top level script] Testing that Array.sort() doesn't 
crash on very large arrays : Expected value 'InternalErr
or: allocation size overflow', Actual value 'out of memory'
TEST-UNEXPECTED-FAIL | js1_5/Array/regress-157652.js | (args: "")

The rest of the test suite passes or fails as expected.


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#731983: runtime warnings: in:imuxsock: unaligned access to 0x0000000043765a09

[Jason Duerstock]

This appears to be fixed in 8.34.0-1, at least on ia64.  Helge, can
you check if it is fixed HPPA as well?

On Thu, Apr 5, 2018 at 8:28 PM, Jason Duerstock
<jason.duerst...@gmail.com> wrote:
> Package: rsyslog
> Version: 8.33.1-1
> Followup-For: Bug #731983
> User: debian-i...@lists.debian.org
> Usertags: ia64
>
> Dear Maintainer,
>
> This bug has been fixed upstream in this commit:
> https://github.com/rsyslog/rsyslog/commit/64b6f5f7b924aa62a800c2e02e68cb498ed50acc
>
> Please add this patch to the package until 8.34 is released.
>
> Thanks!
>
> Jason
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unreleased
>   APT policy: (500, 'unreleased'), (500, 'unstable')
> Architecture: ia64
>
> Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages rsyslog depends on:
> ii  init-system-helpers  1.51
> ii  libc6.1  2.27-2
> ii  libestr0 0.1.10-2.1
> ii  libfastjson4 0.99.8-2
> ii  liblogging-stdlog0   1.0.6-3
> ii  liblognorm5  2.0.3-1
> ii  libsystemd0  238-4
> ii  libuuid1 2.31.1-0.5
> ii  lsb-base 9.20170808
> ii  zlib1g   1:1.2.8.dfsg-5+b1
>
> Versions of packages rsyslog recommends:
> ii  logrotate  3.11.0-0.1
>
> Versions of packages rsyslog suggests:
> pn  rsyslog-doc
> pn  rsyslog-gnutls 
> pn  rsyslog-gssapi 
> pn  rsyslog-mongodb
> pn  rsyslog-mysql | rsyslog-pgsql  
> pn  rsyslog-relp   
>
> -- no debconf information
>

Bug#731983: runtime warnings: in:imuxsock: unaligned access to 0x0000000043765a09

[Jason Duerstock]

Package: rsyslog
Version: 8.33.1-1
Followup-For: Bug #731983
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

This bug has been fixed upstream in this commit:
https://github.com/rsyslog/rsyslog/commit/64b6f5f7b924aa62a800c2e02e68cb498ed50acc

Please add this patch to the package until 8.34 is released.

Thanks!

Jason

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsyslog depends on:
ii  init-system-helpers  1.51
ii  libc6.1  2.27-2
ii  libestr0 0.1.10-2.1
ii  libfastjson4 0.99.8-2
ii  liblogging-stdlog0   1.0.6-3
ii  liblognorm5  2.0.3-1
ii  libsystemd0  238-4
ii  libuuid1 2.31.1-0.5
ii  lsb-base 9.20170808
ii  zlib1g   1:1.2.8.dfsg-5+b1

Versions of packages rsyslog recommends:
ii  logrotate  3.11.0-0.1

Versions of packages rsyslog suggests:
pn  rsyslog-doc
pn  rsyslog-gnutls 
pn  rsyslog-gssapi 
pn  rsyslog-mongodb
pn  rsyslog-mysql | rsyslog-pgsql  
pn  rsyslog-relp   

-- no debconf information

Bug#892200: qdbm: FTBFS on arches without openjdk

[Jason Duerstock]

Source: qdbm
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

As currently configured, gcc-7 does not know where to find the Java jni.h 
headers if the arch is
using gcj rather than openjdk. [1]  The attached patch should clean up the Java 
detection and set
the relevant environment variables correctly.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=qdbm=ia64=1.8.78-6.2=1518046955=0


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- qdbm-1.8.78/debian/rules2018-02-06 10:12:44.0 -0500
+++ qdbm-1.8.78-new/debian/rules2018-03-06 11:19:25.125571799 -0500
@@ -43,13 +43,12 @@
--includedir=\$${prefix}/include/qdbm \
--enable-pthread --enable-zlib --enable-iconv
 
-DEFAULT_JAVA ?= $(shell readlink /etc/alternatives/java | sed 
s@/jre/bin/java@@)
-ifneq (,$(findstring /usr/bin/gij,$(DEFAULT_JAVA)))
+JAVA_HOME = /usr/lib/jvm/default-java
+CONFIGURE_VARS += JAVA_HOME="$(JAVA_HOME)"
+DEFAULT_JAVA ?= $(shell readlink -f $(JAVA_HOME)/bin/java)
+ifneq (,$(filter /usr/bin/%gij%, $(DEFAULT_JAVA)))
 CONFIGURE_VARS += JAVAC="gcj-wrapper" JAR="fastjar"
 CONFIGURE_SWITCHES += --with-gcj
-else
-JAVA_HOME = $(DEFAULT_JAVA)
-CONFIGURE_VARS += JAVA_HOME="$(JAVA_HOME)"
 endif
 
 build: build-arch build-indep

Bug#887525: poppler FTBFS with gtk-doc-tools 1.27-1

[Jason Duerstock]

Source: poppler
Followup-For: Bug #887525

This appears to be fixed upstream:

https://cgit.freedesktop.org/poppler/poppler/commit/gtkdoc.py?id=791e024656212c65d798cb69a134cdd3e30cc79e

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#890432: suricata: FTBFS on ia64

[Jason Duerstock]

Source: suricata
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

>From 
>https://buildd.debian.org/status/fetch.php?pkg=suricata=ia64=1%3A4.0.4-1=1518609275=0

gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/lib/ia64-linux-gnu/htp/include -I/usr/include/nspr -I/usr/include/nspr 
-I/usr/include/nss -I/usr/include/nspr -I/usr/include/nss -I/usr/include  
-Wextra -Werror-implicit-function-declaration  -fstack-protector 
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -I/usr/include 
-DLOCAL_STATE_DIR=\"/var\" -std=gnu99 -Wall -Wno-unused-parameter 
-Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wwrite-strings 
-Wbad-function-cast -Wformat-security -Wno-format-nonliteral 
-Wmissing-format-attribute -funsigned-char  -g -O2 
-fdebug-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs 
-Wformat -Werror=format-security -c -o conf-yaml-loader.o conf-yaml-loader.c
cc1: warning: -fstack-protector not supported for this target
In file included from /usr/include/ia64-linux-gnu/bits/siginfo-consts.h:184:0,
 from /usr/include/signal.h:58,
 from suricata-common.h:152,
 from conf-yaml-loader.c:27:
/usr/include/ia64-linux-gnu/bits/siginfo-consts-arch.h:39:17: error: 
'TRAP_TRACE' undeclared here (not in a function); did you mean '_SC_TRACE'?
   TRAP_BRANCH = TRAP_TRACE + 1,
 ^~
 _SC_TRACE
Makefile:1687: recipe for target 'conf-yaml-loader.o' failed
make[4]: *** [conf-yaml-loader.o] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/src'
Makefile:1131: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/<>/src'
Makefile:494: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:422: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j2 returned exit code 2
debian/rules:57: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Patch attached.

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- src/suricata-common.h.orig  2018-02-14 12:27:29.727546789 -0500
+++ src/suricata-common.h   2018-02-14 12:27:43.135478812 -0500
@@ -34,7 +34,6 @@
 #define FALSE  0
 
 #define _GNU_SOURCE
-#define __USE_GNU
 
 #if HAVE_CONFIG_H
 #include 

Bug#890185: seqan2: FTBFS on ia64

[Jason Duerstock]

Apologies.  I should have said forwarded.

On Sun, Feb 11, 2018 at 12:17 PM, John Paul Adrian Glaubitz
<glaub...@physik.fu-berlin.de> wrote:
> On 02/11/2018 06:12 PM, Jason Duerstock wrote:
>> This has been pushed upstream as https://github.com/seqan/seqan/issues/2281
>
> Be careful, "pushed" is misleading here. It's not been pushed yet as in
> it has been merged. You merely filed an issue unless I missed the commit.
>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#890185: seqan2: FTBFS on ia64

[Jason Duerstock]

Source: seqan2
Severity: normal
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

seqan fails to build on ia64 due to some apparently gratuitous assembly calls 
from gcc.

>From include/seqan/parallel/parallel_lock.h:

#else  // everything else.
asm volatile ("nop" ::: "memory");  // default operation - does nothing => 
Might lead to passive spinning.
#endif

This is invalid on ia64, as nop requires an operand.

This has been pushed upstream as https://github.com/seqan/seqan/issues/2281


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#889796: ltrace: FTBFS on ia64

[Jason Duerstock]

Package: ltrace
Version: 0.5.3-2.1
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

Due to some outdated glibc headers, ltrace does not build for ia64.  The 
attached patch corrects this.

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ltrace depends on:
ii  libc6.1   2.26-1
ii  libelfg0  0.8.13-3

ltrace recommends no packages.

ltrace suggests no packages.

-- no debconf information
--- sysdeps/linux-gnu/ia64/breakpoint.c 2012-11-10 07:43:55.0 -0500
+++ sysdeps/linux-gnu/ia64/breakpoint.c 2018-02-05 13:26:00.229259936 -0500
@@ -24,6 +24,7 @@
  */
 
 #include 
+#include 
 #include 
 #include 
 
--- sysdeps/linux-gnu/ia64/fetch.c  2012-11-10 07:43:55.0 -0500
+++ sysdeps/linux-gnu/ia64/fetch.c  2018-02-06 20:24:31.888749905 -0500
@@ -36,7 +37,7 @@
 
 struct fetch_context {
arch_addr_t stack_pointer;
-   struct pt_all_user_regs regs;
+   struct __pt_all_user_regs regs;
enum param_pack_flavor ppflavor;
 
/* Return values larger than 256 bits (except HFAs of up to 8
@@ -206,7 +207,7 @@
the GPL
(http://www.gelato.unsw.edu.au/archives/linux-ia64/0104/1405.html) */
 static inline double
-fpreg_to_double (struct ia64_fpreg *fp) {
+fpreg_to_double (struct __ia64_fpreg *fp) {
double result;
asm ("ldf.fill %0=%1" : "=f"(result) : "m"(*fp));
return result;

Bug#889645: architecture baseline violation on ia64

[Jason Duerstock]

Additionally, the inclusion of ia64 is wrong here:

https://sources.debian.org/src/pd-moonlib/0.3.6-2/Makefile.pdlibbuilder/#L424

as is evidenced in this build log:

https://buildd.debian.org/status/fetch.php?pkg=pd-moonlib=ia64=0.3.6-2=1517784204=0

Bug#711135: Re: compiling a bootable kernel for ia64 (itanium2, mckinley, rx2620)

[Jason Duerstock]

Does the kernel from here work for you?:

https://people.debian.org/~jrtc27/wheezy-backports-ia64/

Specifically 
https://people.debian.org/~jrtc27/wheezy-backports-ia64/linux-image-3.16.0-0.bpo.4-mckinley_3.16.39-1+deb8u1~bpo70+1+gcc4.4_ia64.deb

Jason

On Sun, Feb 4, 2018 at 7:56 PM, Ivan Zakharyaschev  wrote:
> On Mon, 5 Feb 2018, Ivan Zakharyaschev wrote:
>
>> On Sun, 4 Feb 2018, Frank Scheiner wrote:
>>
>>>  just a quick pointer:
>>>
>>>  I had Debian Wheezy with Linux v3.2.x (vmlinuz-3.2.0-4-mckinley, i.e.
>>>  [this one]) running w/o issues on my rx2620 with two Itanium 2 9040
>>>  (Montecito) both from an on-disk installation and a NFS root FS, but I
>>> ran
>>>  it on bare-metal, not in a VM.
>>
>>
>> Yes, [this one] doesn't boot on our system. It might even be in our case a
>> strange/buggy behavior caused by old firmware for an otherwise correct
>> kernel binary code (or, of course, the code might be not correct). Perhaps,
>> there is a difference between yours and ours machines:
>>
>> root@rx2620:~# cat /proc/cpuinfo
>> processor  : 0
>> vendor : GenuineIntel
>> arch   : IA-64
>> family : 31
>> model  : 2
>> model name : Madison up to 9M cache
>> revision   : 1
>> archrev: 0
>> features   : branchlong
>> cpu number : 0
>> cpu regs   : 4
>> cpu MHz: 1600.021
>> itc MHz: 1600.021752
>> BogoMIPS   : 2390.01
>> siblings   : 1
>> physical id: 0
>>
>> processor  : 1
>> vendor : GenuineIntel
>> arch   : IA-64
>> family : 31
>> model  : 2
>> model name : Madison up to 9M cache
>> revision   : 1
>> archrev: 0
>> features   : branchlong
>> cpu number : 0
>> cpu regs   : 4
>> cpu MHz: 1600.021
>> itc MHz: 1600.021752
>> BogoMIPS   : 2390.01
>> siblings   : 1
>> physical id: 1
>>
>> root@rx2620:~#
>>
>> It looks like ours has 2 Madison CPUs (if we are to trust this cpuinfo),
>> which are older than your Montecito ones.
>
>
>>>  [this one]:
>>>  https://packages.debian.org/wheezy/linux-image-3.2.0-4-mckinley
>>
>>
>> As for gathering information, I can't think of some useful information
>> from a working system so far. The same applies to testing. We are able to
>> test it here. Anyway, thanks for your messages, Frank and Daniel! The
>> remaining useful tasks which I see are:
>>
>> 1) learn how to compile a bootable kernel for this machine and apply this
>> knowledge to compile a fresh current kernel;
>>
>> 2) understand what goes wrong (by bisecting gcc), suggest a fix. (Before
>> we understand it, we can't be sure what should be fixed: it's not
>> necessarily abug in gcc).
>>
>> So far, we've done a number of attempts to compile and boot a kernel (I'm
>> going to post the details and the kernels soon), and my conclusion so far is
>> that the only affecting factor is the version of gcc (even not -O1 vs
>> -Os/-O2).
>>
>> gcc <= 4.5.3 produces a bootable kernel (as for
>> linux-image-3.2.0-4-mckinley, gcc 4.4.7 from wheezy and gcc 4.5.3 from
>> snapshots produced a bootable one in my experiments);
>> gcc > = 4.6.3 produces a non-bootable kernel.
>>
>> So this already gives an initial hypothesis about the solution to 1):
>>
>> To compile a bootable kernel for this machine, use gcc <= 4.5.3.
>
>
> Now that we know how to build a bootable kernel for such machines as ours
> (rx2620 with Madison CPU) and probably Daniel Kasza's rx2600, can such an
> update be published for wheezy?
>
> Perhaps, an additional variant of linux-image-mckinley built with gcc-4.4
> (4.4.7) present in wheezy? As a workaround for this bug.
>
> And what about an updated installation image? So that people trying to
> install Debian on such a machine would succeed not only of they take the
> Debian 6 (squeeze) image (which is definitely not the first thing they would
> try when searching for an installation image), but so that Debian 7 (wheezy)
> images (more likely to be found by them) would work for them, too.
>

Bug#889057: gdbm: please remove dependency on dietlibc for ia64

[Jason Duerstock]

Source: gdbm
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

As dietlibc does not currently build for ia64, please remove the dependency on 
it.

Patch attached.



-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- debian/control.orig 2018-02-01 07:55:07.603676109 -0500
+++ debian/control  2018-02-01 07:55:34.359575320 -0500
@@ -5,7 +5,7 @@
 Build-Depends: texinfo,
debhelper (>= 10),
dh-exec,
-   dietlibc-dev (>= 0.34~cvs20160606-3) [alpha amd64 arm arm64 
armeb armel armhf hppa i386 ia64 mips mipsel mips64el powerpc powerpcspe ppc64 
ppc64el s390 s390x sparc sparc64 x32],
+   dietlibc-dev (>= 0.34~cvs20160606-3) [alpha amd64 arm arm64 
armeb armel armhf hppa i386 mips mipsel mips64el powerpc powerpcspe ppc64 
ppc64el s390 s390x sparc sparc64 x32],
libreadline-dev
 Standards-Version: 4.1.3
 Homepage: https://gnu.org/software/gdbm

Bug#887898: Proper fix for #887898

[Jason Duerstock]

It appears that Red Hat has run into the same thing, and they have a
clearer fix for it:
https://bugzilla.redhat.com/show_bug.cgi?id=1384016

Bug#886175: cross-toolchain-base-ports: Please add support for ia64

[Jason Duerstock]

Maybe it needs a stage1 with --disable-libunwind-exceptions?

On Thu, Jan 25, 2018 at 11:00 AM, John Paul Adrian Glaubitz
 wrote:
> On 01/25/2018 04:54 PM, James Clarke wrote:
>>>
>>> I *think* this is because libunwind-dev has to be [ia64] as well in
>>> debian/control.source.in, but I am not 100% sure yet. Testing now.
>>
>>
>> Well, if it didn’t work without [ia64], it won’t work with.
>
>
> It currently has [amd64 i386 x32]. My original patch didn't have this
> limitation. But it still doesn't work anyway which drives me nuts, it
> did work here and I still have the build log and packages built.
>
> I might have used the internal libunwind for gcc.
>
>> The problem is you need the target’s libunwind-dev, so
>> cross-toolchain-base-ports needs to build it itself, I assume, if the target
>> is ia64.
>
>
> No, I most certainly didn't do it that way.
>
>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>

Bug#888061: libraw: FTBFS on ia64: symbols discrepancy

[Jason Duerstock]

Source: libraw
Followup-For: Bug #888061

Dear Maintainer,

Attached is a patch that will fix the symbols discrepancy problem.


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- /root/libraw16.symbols  2018-01-24 06:25:09.655201651 -0500
+++ debian/libraw16.symbols 2018-01-24 06:56:03.790456828 -0500
@@ -58,7 +58,7 @@
  (c++)"LibRaw::bad_pixels(char const*)@Base" 0.16.0
  (c++)"LibRaw::blend_highlights()@Base" 0.16.0
  (c++)"LibRaw::border_interpolate(int)@Base" 0.16.0
- (c++|arch=alpha amd64 arm64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::calloc(unsigned long, unsigned long)@Base" 0.16.0
+ (c++|arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::calloc(unsigned long, unsigned long)@Base" 0.16.0
 #MISSING: 0.17.0-1# (c++)"LibRaw::cam_xyz_coeff(double (*) [3])@Base" 0.16.0
  (c++)"LibRaw::cameraCount()@Base" 0.16.0
  (c++)"LibRaw::cameraList()@Base" 0.16.0
@@ -173,7 +173,7 @@
  (c++)"LibRaw::lossy_dng_load_raw()@Base" 0.16.0
  (c++)"LibRaw::make_decoder(unsigned char const*)@Base" 0.16.0
  (c++)"LibRaw::make_decoder_ref(unsigned char const**)@Base" 0.16.0
- (c++|arch=alpha amd64 arm64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::malloc(unsigned long)@Base" 0.16.0
+ (c++|arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::malloc(unsigned long)@Base" 0.16.0
  (c++)"LibRaw::median4(int*)@Base" 0.16.0
  (c++)"LibRaw::median_filter()@Base" 0.16.0
  (c++)"LibRaw::median_filter_new()@Base" 0.16.0
@@ -186,7 +186,7 @@
  (c++)"LibRaw::nikon_load_raw()@Base" 0.16.0
  (c++)"LibRaw::nokia_load_raw()@Base" 0.16.0
  (c++)"LibRaw::olympus_load_raw()@Base" 0.16.0
- (c++|arch=alpha amd64 arm64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::open_buffer(void*, unsigned long)@Base" 0.16.0
+ (c++|arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::open_buffer(void*, unsigned long)@Base" 0.16.0
  (c++)"LibRaw::open_datastream(LibRaw_abstract_datastream*)@Base" 0.16.0
  (c++)"LibRaw::open_file(char const*, long long)@Base" 0.16.0
  (c++)"LibRaw::packed_dng_load_raw()@Base" 0.16.0
@@ -234,7 +234,7 @@
  (c++)"LibRaw::raw2image_ex(int)@Base" 0.16.0
  (c++)"LibRaw::raw2image_start()@Base" 0.16.0
  (c++)"LibRaw::read_shorts(unsigned short*, int)@Base" 0.16.0
- (c++|arch=alpha amd64 arm64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::realloc(void*, unsigned long)@Base" 0.16.0
+ (c++|arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw::realloc(void*, unsigned long)@Base" 0.16.0
  (c++)"LibRaw::recover_highlights()@Base" 0.16.0
  (c++)"LibRaw::recycle()@Base" 0.16.0
  (c++)"LibRaw::recycle_datastream()@Base" 0.16.0
@@ -294,7 +294,7 @@
  (c++)"LibRaw_abstract_datastream::subfile_close()@Base" 0.16.0
  (c++)"LibRaw_abstract_datastream::subfile_open(char const*)@Base" 0.16.0
  (c++)"LibRaw_abstract_datastream::tempbuffer_close()@Base" 0.16.0
- (c++|arch=alpha amd64 arm64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw_abstract_datastream::tempbuffer_open(void*, unsigned 
long)@Base" 0.16.0
+ (c++|arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw_abstract_datastream::tempbuffer_open(void*, unsigned 
long)@Base" 0.16.0
 #MISSING: 0.18.6-1# 
(c++|optional=gcc-4.8)"LibRaw_abstract_datastream::~LibRaw_abstract_datastream()@Base"
 0.16.0
  (c++)"LibRaw_bigfile_datastream::LibRaw_bigfile_datastream(char const*)@Base" 
0.16.0
  (c++)"LibRaw_bigfile_datastream::eof()@Base" 0.16.0
@@ -303,7 +303,7 @@
  (c++)"LibRaw_bigfile_datastream::gets(char*, int)@Base" 0.16.0
  (c++)"LibRaw_bigfile_datastream::jpeg_src(void*)@Base" 0.16.0
  (c++)"LibRaw_bigfile_datastream::make_jas_stream()@Base" 0.16.0
- (c++|arch=alpha amd64 arm64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw_bigfile_datastream::read(void*, unsigned long, unsigned 
long)@Base" 0.16.0
+ (c++|arch=alpha amd64 arm64 ia64 kfreebsd-amd64 mips64 mips64el ppc64 ppc64el 
s390x sparc64)"LibRaw_bigfile_datastream::read(void*, unsigned long, unsigned 
long)@Base" 0.16.0
  (c++)"LibRaw_bigfile_datastream::scanf_one(char const*, void*)@Base" 0.16.0
  (c++)"LibRaw_bigfile_datastream::seek(long long, int)@Base" 0.16.0
  (c++)"LibRaw_bigfile_datastream::size()@Base" 0.16.0
@@ -312,13 +312,13 @@
  (c++)"LibRaw_bigfile_datastream::tell()@Base" 0.16.0
  (c++)"LibRaw_bigfile_datastream::valid()@Base" 0.16.0
  (c++)"LibRaw_bigfile_datastream::~LibRaw_bigfile_datastream()@Base" 0.16.0
- (c++|arch=alpha amd64 arm64 kfreebsd-amd64 

Bug#887868: libgnomecanvas FTBFS with gtk-doc-tools 1.27-1

[Jason Duerstock]

I am neither -- my interest in getting it to build is solely in making
sure that graphviz can install so it can stop blocking all the
packages that depend on it.  graphviz was in the top 10 list of build
dependencies for ia64.

Hopefully graphviz will stop depending on it soon. :)


On Tue, Jan 23, 2018 at 1:58 PM, Simon McVittie <s...@debian.org> wrote:
> On Tue, 23 Jan 2018 at 07:50:30 -0500, Jason Duerstock wrote:
>> The attached patch lets the package finish building.
>
> Thanks, but as I said in a previous reply to the bug, this package is
> already marked for removal from testing before Debian 10: it's been
> unmaintained upstream since 2011, and the packages that still depend on
> it already have RC bugs filed.
>
> (Or are you a maintainer of something that depends on libgnomecanvas,
> intending to adopt it as its new Debian and upstream maintainer?)
>
> smcv

Bug#887868: libgnomecanvas FTBFS with gtk-doc-tools 1.27-1

[Jason Duerstock]

Source: libgnomecanvas
Followup-For: Bug #887868

Dear Maintainer,

The attached patch lets the package finish building.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- ./libgnomecanvas/gnome-canvas-text.c.orig	2018-01-23 07:39:44.316583249 -0500
+++ ./libgnomecanvas/gnome-canvas-text.c	2018-01-23 07:43:09.277812515 -0500
@@ -32,7 +32,7 @@
  *
  *
  * Author: Federico Mena 
- * Port to Pango co-done by Gergõ Érdi 
+ * Port to Pango co-done by Gergõ Érdi 
  */
 
 #include 

Bug#887453: libunwind: please disable lzma on ia64

[Jason Duerstock]

After some consideration, we've determined that this bug is better
filed against gcc.  See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83971


On Tue, Jan 16, 2018 at 1:07 PM, Jason Duerstock
<jason.duerst...@gmail.com> wrote:
> Source: libunwind
> Severity: normal
> Tags: patch
> User: debian-i...@lists.debian.org
> Usertags: ia64
>
> Dear Maintainer,
>
> For the ia64 port, we would like to disable lzma support for ia64, as it has 
> caused several packages
> to fail building when static linking is used.  (gcc doesn't know to include 
> liblzma.a when it tries to
> include libunwind.a).
>
> The attached patch should accomplish this.
>
> We will re-enable it once we've determined a good way to work through this 
> problem.
>
> Thanks,
>
> Jason
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: ia64
>
> Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)

Bug#887738: nspr FTBFS with glibc 2.26

[Jason Duerstock]

Source: nspr
Followup-For: Bug #887738

Dear Maintainer,

The attached patch fixes this bug.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- nspr/pr/tests/prfz.c.orig   2018-01-20 13:38:48.877027452 +
+++ nspr/pr/tests/prfz.c2018-01-20 13:23:00.495279463 +
@@ -10,6 +10,7 @@
 #include 
 #include 
 #include 
+#include 
 
 int
 main(int argc, char **argv)

Bug#884105: Acknowledgement (gdb: bump libunwind version dependency for ia64)

[Jason Duerstock]

After some discussion on #debian-ports, I believe this should be
changed from libunwind7-dev to libunwind-dev.

Jason

On Mon, Dec 11, 2017 at 8:30 AM, Debian Bug Tracking System
 wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 884105: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884105.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Héctor Orón Martínez 
>
> If you wish to submit further information on this problem, please
> send it to 884...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 884105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884105
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#887453: libunwind: please disable lzma on ia64

[Jason Duerstock]

Source: libunwind
Severity: normal
Tags: patch
User: debian-i...@lists.debian.org
Usertags: ia64

Dear Maintainer,

For the ia64 port, we would like to disable lzma support for ia64, as it has 
caused several packages
to fail building when static linking is used.  (gcc doesn't know to include 
liblzma.a when it tries to
include libunwind.a).

The attached patch should accomplish this.

We will re-enable it once we've determined a good way to work through this 
problem.

Thanks,

Jason


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- debian/control.orig 2018-01-16 10:06:58.752562266 -0500
+++ debian/control  2018-01-16 10:07:19.420483094 -0500
@@ -2,8 +2,8 @@
 Priority: optional
 Section: libs
 Maintainer: Adrian Bunk 
-Build-Depends: debhelper (>= 10), liblzma-dev , 
texlive-extra-utils
-Build-Conflicts: liblzma-dev 
+Build-Depends: debhelper (>= 10), liblzma-dev [!ia64] , 
texlive-extra-utils
+Build-Conflicts: liblzma-dev [ia64] 
 Standards-Version: 4.1.1
 Homepage: http://www.nongnu.org/libunwind
 

Bug#884356: mesa FTBFS on ia64

[Jason Duerstock]

So I got it to build, but I'm pretty sure the way I did it is less
than Right.  In src/gallium/drivers/radeonsi/Automake.inc, I moved the
following bit out of the "if" statement:

TARGET_COMPILER_LIB_DEPS = \
$(top_builddir)/src/compiler/nir/libnir.la

Also, I used ./configure with LIBS="-lpthread".

I think you might be right about the gc-sections link warning, but I'm
not quite sure what it will take to get that working for ia64 any time
soon.  Are you able to understand what is going on here, or should I
push this upstream?

Thanks,

Jason

On Mon, Dec 18, 2017 at 7:48 AM, Jason Duerstock
<jason.duerst...@gmail.com> wrote:
> I attached the full build log.
>
> I don't think the warning is related.  My understanding is that that
> option just removes unused sections on linking.  But I will dig in
> further to be sure.
>
> Thanks,
>
> Jason
>
>
> On Fri, Dec 15, 2017 at 1:50 PM, Andreas Boll
> <andreas.boll@gmail.com> wrote:
>> On Thu, Dec 14, 2017 at 08:29:25AM -0500, Jason Duerstock wrote:
>>> Source: mesa
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> On ia64, mesa appears to FTBFS due to a missing link to libpthread by 
>>> libgbm:
>>>
>>> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -I../../../include 
>>> -I../../../src -I../../../src/loader -I../../../src/gbm/main
>>>  -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
>>> -D_GNU_SOURCE -DUSE_GCC_ATOMIC_BUILTINS -DNDEBUG -DTEXTURE_FL
>>> OAT_ENABLED -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF 
>>> -DHAVE_MKOSTEMP -DHAVE_STRTOD_L -DHAVE_DL_ITERATE_PHDR 
>>> -DHAVE_POSIX_MEMALIGN -DHAVE_GALLIUM_EXTRA_HUD=1 -DHAVE_LIBSENSORS=1 
>>> -DUSE_LIBGLVND=1 -DHAVE_LIBDRM -DGLX_USE_DRM -DGLX_INDIRECT_RENDERING 
>>> -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_X11_PLATFORM 
>>> -DHAVE_SURFACELESS_PLATFORM -DHAVE_WAYLAND_PLATFORM -DWL_HIDE_DEPRECATED 
>>> -DHAVE_DRM_PLATFORM -DHAVE_DRI3 -DENABLE_SHADER_CACHE -DHAVE_MINCORE 
>>> -DHAVE_ST_VDPAU -fvisibility=hidden  
>>> -DDEFAULT_DRIVER_DIR='"/usr/lib/ia64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri"'
>>>  -I/usr/include/libdrm  -g -O2 -fdebug-prefix-map=/mnt/a/sid/mesa-17.3.0=. 
>>> -Wformat -Werror=format-security -Wall -Wall 
>>> -Werror=implicit-function-declaration -Werror=missing-prototypes 
>>> -Wmissing-prototypes -fno-math-errno -fno-trapping-math -std=c99  
>>> -no-undefined -version-info 1:0 -Wl,--gc-sections -Wl,--no-undefined  -o 
>>> libgbm.la -rpath /usr/lib/ia64-linux-gnu main/backend.lo main/gbm.lo 
>>> backends/dri/gbm_dri.lo!
>>>   ../../sr
>>>  c/loader/libloader.la ../../src/util/libmesautil.la 
>>> ../../src/util/libxmlconfig.la -ldl 
>>> ../../src/egl/wayland/wayland-drm/libwayland-drm.la -lwayland-server -ldrm
>>> libtool: link: gcc -shared  -fPIC -DPIC  main/.libs/backend.o 
>>> main/.libs/gbm.o backends/dri/.libs/gbm_dri.o  -Wl,--whole-archive 
>>> ../../src/loader/.libs/libloader.a ../../src/util/.libs/libmesautil.a 
>>> ../../src/util/.libs/libxmlconfig.a 
>>> ../../src/egl/wayland/wayland-drm/.libs/libwayland-drm.a 
>>> -Wl,--no-whole-archive  -lz -lexpat -lm -ldl -lwayland-server -ldrm  -g -O2 
>>> -Wl,--gc-sections -Wl,--no-undefined   -Wl,-soname -Wl,libgbm.so.1 -o 
>>> .libs/libgbm.so.1.0.0
>>> /usr/bin/ld: Warning: gc-sections option ignored
>>
>> Maybe it's related to this warning.
>>
>>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>>> `u_thread_setname':
>>> ./build/src/util/../../../src/util/u_thread.h:66: undefined reference to 
>>> `pthread_setname_np'
>>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>>> `thrd_join':
>>> ./build/src/util/../../../include/c11/threads_posix.h:336: undefined 
>>> reference to `pthread_join'
>>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>>> `u_thread_create':
>>> ./build/src/util/../../../src/util/u_thread.h:48: undefined reference to 
>>> `pthread_sigmask'
>>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>>> `thrd_create':
>>> ./build/src/util/../../../include/c11/threads_posix.h:296: undefined 
>>> reference to `pthread_create'
>>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>>> `u_thread_create':
>>> ./build/src/util/../../../src/util/u_thread.h:50: undefined reference to 
>>> `pthread_sigmask'
&g

Bug#887066: gcc-7: RTL combine pass yields wrong rotate result

[Jason Duerstock]

Package: gcc-7
Version: 7.2.0-17
Severity: normal
Tags: patch

Dear Maintainer,

A gcc bug introduced between 6.4.0 and 7.2.0 makes openssl compile incorrectly. 
 The bug has been filed with
gcc upstream and corrected:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83565

The patch can be found here:

https://gcc.gnu.org/viewcvs/gcc?view=revision=256573

Please include this in the next release.

Thanks,

Jason


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gcc-7 depends on:
ii  binutils  2.29.1-8
ii  cpp-7 7.2.0-17
ii  gcc-7-base7.2.0-17
ii  libc6.1   2.25-3
ii  libcc1-0  7.2.0-17
ii  libgcc-7-dev  7.2.0-17
ii  libgcc1   1:7.2.0-17
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-17
ii  libunwind81.1-5
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6.1-dev  2.25-3

Versions of packages gcc-7 suggests:
ii  gcc-7-doc 7.2.0-1
pn  gcc-7-locales 
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- no debconf information

Bug#853502: libpam-chroot: ftbfs with GCC-7

[Jason Duerstock]

Package: libpam-chroot
Followup-For: Bug #853502

Dear Maintainer,

Attached please find a patch that fixes this bug.  It also addresses #754322.

Thanks,

Jason


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- libpam-chroot-0.9/pam_chroot.c  2018-01-10 14:20:17.0 +
+++ libpam-chroot-0.9-fixed/pam_chroot.c2018-01-10 14:05:39.275066056 
+
@@ -187,7 +187,7 @@
char **uptr;
 
if(NULL == user || NULL == ngrps) { return -1; }
-   if(0 > *ngrps || 0 > gid) { return -1; }
+   if(0 > *ngrps) { return -1; }
 
if(gcount < *ngrps) {
if(NULL != grps) { grps[gcount] = gid; }
@@ -870,7 +870,7 @@
break;
 
default:
-   if(opts.flags * _PAM_OPTS_DEBUG) {
+   if(opts.flags & _PAM_OPTS_DEBUG) {
_pam_log(LOG_NOTICE, "%s: returning failure", 
opts.module);
}
err = PAM_SESSION_ERR;

Bug#886840: glibc ia64 memchr bug causes testsuite failures in m4 and diffutils

[Jason Duerstock]

Source: glibc
Severity: normal
Tags: patch

Dear Maintainer,

glibc 2.26 has an ia64 bug as detailed here:
https://sourceware.org/bugzilla/show_bug.cgi?id=22603

The patch as scheduled to be merged into the next version of glibc is available 
here:
https://sourceware.org/git/?p=glibc.git;a=commit;h=3bb1ef58b989012f8199b82af6ec136da2f9fda3

Please include it in the next src:glibc release.

Thank you,

Jason


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#886693: linux: please reinstate ia64 for the linux kernel package

[Jason Duerstock]

Source: linux
Severity: normal
Tags: patch

Dear Maintainer,

As you may be aware, the ia64 architecture has recently been added back to 
Debian, but now resides in Debian ports.
The attached patch should enable the linux package to build the ia64 kernel 
again.

Thanks for your time!


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- debian/config/defines.orig  2018-01-07 16:56:29.168437643 -0500
+++ debian/config/defines   2018-01-07 16:56:39.660502403 -0500
@@ -74,6 +74,7 @@
  armhf
  hppa
  i386
+ ia64
  m68k
  mips
  mips64
diff -u -r -N debian/installer/ia64/kernel-versions 
debian/installer/ia64/kernel-versions
--- debian/installer/ia64/kernel-versions   1969-12-31 19:00:00.0 
-0500
+++ debian/installer/ia64/kernel-versions   2017-12-11 14:50:41.204852404 
-0500
@@ -0,0 +1,2 @@
+# arch version flavour installedname suffix build-depends
+ia64   -   itanium - -  -
diff -u -r -N debian/installer/ia64/modules/ia64/ata-modules 
debian/installer/ia64/modules/ia64/ata-modules
--- debian/installer/ia64/modules/ia64/ata-modules  1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/ata-modules  2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1 @@
+#include 
diff -u -r -N debian/installer/ia64/modules/ia64/btrfs-modules 
debian/installer/ia64/modules/ia64/btrfs-modules
--- debian/installer/ia64/modules/ia64/btrfs-modules1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/btrfs-modules2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1 @@
+#include 
diff -u -r -N debian/installer/ia64/modules/ia64/cdrom-core-modules 
debian/installer/ia64/modules/ia64/cdrom-core-modules
--- debian/installer/ia64/modules/ia64/cdrom-core-modules   1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/cdrom-core-modules   2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1,2 @@
+#include 
+ide-cd_mod
diff -u -r -N debian/installer/ia64/modules/ia64/crc-modules 
debian/installer/ia64/modules/ia64/crc-modules
--- debian/installer/ia64/modules/ia64/crc-modules  1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/crc-modules  2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1,2 @@
+#include 
+
diff -u -r -N debian/installer/ia64/modules/ia64/crypto-dm-modules 
debian/installer/ia64/modules/ia64/crypto-dm-modules
--- debian/installer/ia64/modules/ia64/crypto-dm-modules1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/crypto-dm-modules2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1 @@
+#include 
diff -u -r -N debian/installer/ia64/modules/ia64/crypto-modules 
debian/installer/ia64/modules/ia64/crypto-modules
--- debian/installer/ia64/modules/ia64/crypto-modules   1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/crypto-modules   2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1 @@
+#include 
diff -u -r -N debian/installer/ia64/modules/ia64/event-modules 
debian/installer/ia64/modules/ia64/event-modules
--- debian/installer/ia64/modules/ia64/event-modules1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/event-modules2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1 @@
+#include 
diff -u -r -N debian/installer/ia64/modules/ia64/ext4-modules 
debian/installer/ia64/modules/ia64/ext4-modules
--- debian/installer/ia64/modules/ia64/ext4-modules 1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/ext4-modules 2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1 @@
+#include 
diff -u -r -N debian/installer/ia64/modules/ia64/fat-modules 
debian/installer/ia64/modules/ia64/fat-modules
--- debian/installer/ia64/modules/ia64/fat-modules  1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/fat-modules  2017-12-11 
14:51:56.429450985 -0500
@@ -0,0 +1 @@
+#include 
diff -u -r -N debian/installer/ia64/modules/ia64/fb-modules 
debian/installer/ia64/modules/ia64/fb-modules
--- debian/installer/ia64/modules/ia64/fb-modules   1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/fb-modules   2017-12-11 
14:51:56.433451017 -0500
@@ -0,0 +1,2 @@
+fbcon ?
+vgastate
diff -u -r -N debian/installer/ia64/modules/ia64/firewire-core-modules 
debian/installer/ia64/modules/ia64/firewire-core-modules
--- debian/installer/ia64/modules/ia64/firewire-core-modules1969-12-31 
19:00:00.0 -0500
+++ debian/installer/ia64/modules/ia64/firewire-core-modules2017-12-11 
14:51:56.433451017 -0500
@@ -0,0 +1,2 @@
+#include 
+
diff -u -r -N debian/installer/ia64/modules/ia64/fuse-modules 
debian/installer/ia64/modules/ia64/fuse-modules

Bug#884007: systemtap FTBFS on ia64

[Jason Duerstock]

Yes, we are working toward getting ia64 into Debian ports, and
systemtap is one of the ones with problems we've run into along the
way.  It should be ready in the next month or two.

On Wed, Dec 27, 2017 at 1:02 AM, Ritesh Raj Sarraf <r...@debian.org> wrote:
> Control: tag -1 +pending
>
> On Sun, 2017-12-10 at 06:59 -0500, Jason Duerstock wrote:
>> Source: systemtap
>> Severity: normal
>> Tags: patch
>>
>> Dear Maintainer,
>>
>> systemtap fails to build from source on ia64.  The attached patch
>> should correct the problem spots.
>
> Thanks. I've applied the patch and it'll be part of the next upload.
> I do not see ia64 in the list of build machines. Are you doing an
> external build elsewhere ?
>
>
> --
> Ritesh Raj Sarraf | http://people.debian.org/~rrs
> Debian - The Universal Operating System

Bug#884356: mesa FTBFS on ia64

[Jason Duerstock]

I attached the full build log.

I don't think the warning is related.  My understanding is that that
option just removes unused sections on linking.  But I will dig in
further to be sure.

Thanks,

Jason


On Fri, Dec 15, 2017 at 1:50 PM, Andreas Boll
<andreas.boll@gmail.com> wrote:
> On Thu, Dec 14, 2017 at 08:29:25AM -0500, Jason Duerstock wrote:
>> Source: mesa
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> On ia64, mesa appears to FTBFS due to a missing link to libpthread by libgbm:
>>
>> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -I../../../include 
>> -I../../../src -I../../../src/loader -I../../../src/gbm/main
>>  -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
>> -D_GNU_SOURCE -DUSE_GCC_ATOMIC_BUILTINS -DNDEBUG -DTEXTURE_FL
>> OAT_ENABLED -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF 
>> -DHAVE_MKOSTEMP -DHAVE_STRTOD_L -DHAVE_DL_ITERATE_PHDR -DHAVE_POSIX_MEMALIGN 
>> -DHAVE_GALLIUM_EXTRA_HUD=1 -DHAVE_LIBSENSORS=1 -DUSE_LIBGLVND=1 
>> -DHAVE_LIBDRM -DGLX_USE_DRM -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING 
>> -DGLX_USE_TLS -DHAVE_X11_PLATFORM -DHAVE_SURFACELESS_PLATFORM 
>> -DHAVE_WAYLAND_PLATFORM -DWL_HIDE_DEPRECATED -DHAVE_DRM_PLATFORM -DHAVE_DRI3 
>> -DENABLE_SHADER_CACHE -DHAVE_MINCORE -DHAVE_ST_VDPAU -fvisibility=hidden  
>> -DDEFAULT_DRIVER_DIR='"/usr/lib/ia64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri"'
>>  -I/usr/include/libdrm  -g -O2 -fdebug-prefix-map=/mnt/a/sid/mesa-17.3.0=. 
>> -Wformat -Werror=format-security -Wall -Wall 
>> -Werror=implicit-function-declaration -Werror=missing-prototypes 
>> -Wmissing-prototypes -fno-math-errno -fno-trapping-math -std=c99  
>> -no-undefined -version-info 1:0 -Wl,--gc-sections -Wl,--no-undefined  -o 
>> libgbm.la -rpath /usr/lib/ia64-linux-gnu main/backend.lo main/gbm.lo 
>> backends/dri/gbm_dri.lo!
>>   ../../sr
>>  c/loader/libloader.la ../../src/util/libmesautil.la 
>> ../../src/util/libxmlconfig.la -ldl 
>> ../../src/egl/wayland/wayland-drm/libwayland-drm.la -lwayland-server -ldrm
>> libtool: link: gcc -shared  -fPIC -DPIC  main/.libs/backend.o 
>> main/.libs/gbm.o backends/dri/.libs/gbm_dri.o  -Wl,--whole-archive 
>> ../../src/loader/.libs/libloader.a ../../src/util/.libs/libmesautil.a 
>> ../../src/util/.libs/libxmlconfig.a 
>> ../../src/egl/wayland/wayland-drm/.libs/libwayland-drm.a 
>> -Wl,--no-whole-archive  -lz -lexpat -lm -ldl -lwayland-server -ldrm  -g -O2 
>> -Wl,--gc-sections -Wl,--no-undefined   -Wl,-soname -Wl,libgbm.so.1 -o 
>> .libs/libgbm.so.1.0.0
>> /usr/bin/ld: Warning: gc-sections option ignored
>
> Maybe it's related to this warning.
>
>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>> `u_thread_setname':
>> ./build/src/util/../../../src/util/u_thread.h:66: undefined reference to 
>> `pthread_setname_np'
>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>> `thrd_join':
>> ./build/src/util/../../../include/c11/threads_posix.h:336: undefined 
>> reference to `pthread_join'
>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>> `u_thread_create':
>> ./build/src/util/../../../src/util/u_thread.h:48: undefined reference to 
>> `pthread_sigmask'
>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>> `thrd_create':
>> ./build/src/util/../../../include/c11/threads_posix.h:296: undefined 
>> reference to `pthread_create'
>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>> `u_thread_create':
>> ./build/src/util/../../../src/util/u_thread.h:50: undefined reference to 
>> `pthread_sigmask'
>> ./build/src/util/../../../src/util/u_thread.h:50: undefined reference to 
>> `pthread_sigmask'
>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>> `call_once':
>> ./build/src/util/../../../include/c11/threads_posix.h:96: undefined 
>> reference to `pthread_once'
>> ./build/src/util/../../../include/c11/threads_posix.h:96: undefined 
>> reference to `pthread_once'
>> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
>> `u_thread_get_time_nano':
>> ./build/src/util/../../../src/util/u_thread.h:84: undefined reference to 
>> `pthread_getcpuclockid'
>>
>> I have attached the last 50 lines of the build log, but the full log is 
>> available if you need it.
>
> Yes, the full log would be nice, especially the part from configure
> would be interesting.
>
> Thanks,
> Andreas


mesa.build.log.xz
Description: Binary data

Bug#884356: mesa FTBFS on ia64

[Jason Duerstock]

Source: mesa
Severity: normal

Dear Maintainer,

On ia64, mesa appears to FTBFS due to a missing link to libpthread by libgbm:

/bin/bash ../../libtool  --tag=CC   --mode=link gcc -I../../../include 
-I../../../src -I../../../src/loader -I../../../src/gbm/main
 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-D_GNU_SOURCE -DUSE_GCC_ATOMIC_BUILTINS -DNDEBUG -DTEXTURE_FL
OAT_ENABLED -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP 
-DHAVE_STRTOD_L -DHAVE_DL_ITERATE_PHDR -DHAVE_POSIX_MEMALIGN 
-DHAVE_GALLIUM_EXTRA_HUD=1 -DHAVE_LIBSENSORS=1 -DUSE_LIBGLVND=1 -DHAVE_LIBDRM 
-DGLX_USE_DRM -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS 
-DHAVE_X11_PLATFORM -DHAVE_SURFACELESS_PLATFORM -DHAVE_WAYLAND_PLATFORM 
-DWL_HIDE_DEPRECATED -DHAVE_DRM_PLATFORM -DHAVE_DRI3 -DENABLE_SHADER_CACHE 
-DHAVE_MINCORE -DHAVE_ST_VDPAU -fvisibility=hidden  
-DDEFAULT_DRIVER_DIR='"/usr/lib/ia64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri"'
 -I/usr/include/libdrm  -g -O2 -fdebug-prefix-map=/mnt/a/sid/mesa-17.3.0=. 
-Wformat -Werror=format-security -Wall -Wall 
-Werror=implicit-function-declaration -Werror=missing-prototypes 
-Wmissing-prototypes -fno-math-errno -fno-trapping-math -std=c99  -no-undefined 
-version-info 1:0 -Wl,--gc-sections -Wl,--no-undefined  -o libgbm.la -rpath 
/usr/lib/ia64-linux-gnu main/backend.lo main/gbm.lo backends/dri/gbm_dri.lo!
  ../../sr
 c/loader/libloader.la ../../src/util/libmesautil.la 
../../src/util/libxmlconfig.la -ldl 
../../src/egl/wayland/wayland-drm/libwayland-drm.la -lwayland-server -ldrm
libtool: link: gcc -shared  -fPIC -DPIC  main/.libs/backend.o main/.libs/gbm.o 
backends/dri/.libs/gbm_dri.o  -Wl,--whole-archive 
../../src/loader/.libs/libloader.a ../../src/util/.libs/libmesautil.a 
../../src/util/.libs/libxmlconfig.a 
../../src/egl/wayland/wayland-drm/.libs/libwayland-drm.a -Wl,--no-whole-archive 
 -lz -lexpat -lm -ldl -lwayland-server -ldrm  -g -O2 -Wl,--gc-sections 
-Wl,--no-undefined   -Wl,-soname -Wl,libgbm.so.1 -o .libs/libgbm.so.1.0.0
/usr/bin/ld: Warning: gc-sections option ignored
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
`u_thread_setname':
./build/src/util/../../../src/util/u_thread.h:66: undefined reference to 
`pthread_setname_np'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
`thrd_join':
./build/src/util/../../../include/c11/threads_posix.h:336: undefined reference 
to `pthread_join'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
`u_thread_create':
./build/src/util/../../../src/util/u_thread.h:48: undefined reference to 
`pthread_sigmask'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
`thrd_create':
./build/src/util/../../../include/c11/threads_posix.h:296: undefined reference 
to `pthread_create'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
`u_thread_create':
./build/src/util/../../../src/util/u_thread.h:50: undefined reference to 
`pthread_sigmask'
./build/src/util/../../../src/util/u_thread.h:50: undefined reference to 
`pthread_sigmask'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
`call_once':
./build/src/util/../../../include/c11/threads_posix.h:96: undefined reference 
to `pthread_once'
./build/src/util/../../../include/c11/threads_posix.h:96: undefined reference 
to `pthread_once'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
`u_thread_get_time_nano':
./build/src/util/../../../src/util/u_thread.h:84: undefined reference to 
`pthread_getcpuclockid'

I have attached the last 50 lines of the build log, but the full log is 
available if you need it.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Making all in gbm
make[4]: Entering directory '/mnt/a/sid/mesa-17.3.0/build/src/gbm'
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"Mesa\" 
-DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"17.3.0\" 
-DPACKAGE_STRING=\"Mesa\ 17.3.0\" 
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
 -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"17.3.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1 
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1 
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1 
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1 

Bug#883858: closed by Adrian Bunk <b...@debian.org> (Bug#883858: fixed in libunwind 1.2.1-4)

[Jason Duerstock]

One tiny mishap: src/ia64/mk_cursor_i needs to be chmod 755.

Sorry for the oversight.

On Wed, Dec 13, 2017 at 4:09 PM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the src:libunwind package:
>
> #883858: libunwind FTBFS on ia64
>
> It has been closed by Adrian Bunk <b...@debian.org>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Adrian Bunk <
> b...@debian.org> by
> replying to this email.
>
>
> --
> 883858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883858
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Adrian Bunk <b...@debian.org>
> To: 883858-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Wed, 13 Dec 2017 21:06:50 +
> Subject: Bug#883858: fixed in libunwind 1.2.1-4
> Source: libunwind
> Source-Version: 1.2.1-4
>
> We believe that the bug you reported is fixed in the latest version of
> libunwind, 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 883...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Adrian Bunk <b...@debian.org> (supplier of updated libunwind 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 ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Wed, 13 Dec 2017 20:24:14 +0200
> Source: libunwind
> Binary: libunwind-dev libunwind8 libunwind-setjmp0-dev libunwind-setjmp0
> Architecture: source
> Version: 1.2.1-4
> Distribution: unstable
> Urgency: low
> Maintainer: Adrian Bunk <b...@debian.org>
> Changed-By: Adrian Bunk <b...@debian.org>
> Description:
>  libunwind-dev - library to determine the call-chain of a program -
> development
>  libunwind-setjmp0 - libunwind-based non local goto - runtime
>  libunwind-setjmp0-dev - libunwind-based non local goto - development
>  libunwind8 - library to determine the call-chain of a program - runtime
> Closes: 883858 883861
> Changes:
>  libunwind (1.2.1-4) unstable; urgency=low
>  .
>* Add upstream fix for FTBFS with glibc 2.26. (Closes: #883861)
>* Add ia64 fixes from Jason Duerstock. (Closes: #883858)
> Checksums-Sha1:
>  48fb29a5657cd6711b24012295f68cd57409f196 2527 libunwind_1.2.1-4.dsc
>  a1306ae056db2a1ee856e663af6923aaede489f7 16924
> libunwind_1.2.1-4.debian.tar.xz
> Checksums-Sha256:
>  186344c9e538799d02ae70d11dff092c3816670047e055b1669a2efcfa99cf3f 2527
> libunwind_1.2.1-4.dsc
>  c815d14740ed8bc82bbfc1b36cc81686fa2ee46af137da74b91fd49d177b47f6 16924
> libunwind_1.2.1-4.debian.tar.xz
> Files:
>  5a288e9e0f1915b25606475c5ba360f2 2527 libs optional libunwind_1.2.1-4.dsc
>  e374e961cefde4ff2abb927765d8b95d 16924 libs optional
> libunwind_1.2.1-4.debian.tar.xz
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAloxggwACgkQiNJCh6LY
> mLE6hw/+JyDiuEONqauhYdleV9/ckD893smBEV3H4bq+ZE28x7PpLHcB3xuVUZvu
> cP8U9vgv7J5tniBuT+ypB2u7ylTGW5qclot6Ka6XRHNVpQ+DsfO/FNTen2dfUHwK
> M6baQ+F57AIRQUaMy0pqHLlFHJIoaluszfYl1/lUmaJTq/jLkqwqSV4yViKnYGeA
> o1KjEpxaAWWWlCzKsPaOpbjQIdcEcW6CjZUkM8ujQ7SSAEiZ37z6uVr94itplO/T
> oNfRdyH/e8av0EpwE1A9fX8WpN7rXwHVBGAMTZpnz938aQGG/0TwlN5OnXNEie4o
> 7a1LNplxdWiOUZNWBkne+BhWWEKw0Lff2yZ9GifoOcMaYcSrcLESSmytpYKeyDBm
> bya1DzjrpOOzLyjSTjBxZS7jWj+3pO5CpdXt5Dk9OZyPgNXY9HEEY+T8y+FHI+KT
> OX6HaZ1uvo6cFZ2qPSNwx9IGL0b0LAflktVqWgiHIiaJvw/3HjAi3mtFa3dqs4VB
> 22pvQmtKyceDdTX7ZYRok0VKpanYivkDEbWZD7z/Zsva/HObHCrTFUC53wvRbhy8
> 6CFansCbLgTeX8GEn+hkpoowUV9JTb59bFYWjBl0AKUSPjEWd3EcfIx7dyFiwVH6
> 5NltwnjYTVeZkyoU4of6QiRrAkremGliZZp6WdWx1didwWeaRYQ=
> =Pznf
> -END PGP SIGNATURE-
>
> -- Forwarded message --
> From: Jason Duerstock <jason.duerst...@gmail.com>
> To: Debian Bug Tracking System <sub...@bugs.debian.org>
> Cc:
> Bcc:
> Date: Fri, 08 Dec 2017 06:56:05 -0500
> Subject: libunwind FTBFS on ia64
> Source: libunwind
> Severity: normal
>
> Dear Maintainer,
>
> It appears as though some files went missing from libunwind between 1.1
> and 1.2.  It now fails to build 

Bug#884194: glibc 2.25 breaks sysv ipc on ia64

[Jason Duerstock]

Source: glibc
Severity: normal
Tags: patch

Dear Maintainer,

sysv ipc always runs in 64-bit mode on ia64, but this is not reflected by the 
glibc 2.25 headers.
glibc upstream master has a patch to correct this.  please include this in the 
next glibc release.

See: 
https://sourceware.org/git/?p=glibc.git;a=commit;h=89bd8016b30e504829bea48c4cd556769abfcf3a

Thanks!


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#884105: gdb: bump libunwind version dependency for ia64

[Jason Duerstock]

Package: gdb
Version: 7.12-6
Severity: normal
Tags: patch

Dear Maintainer,

gdb currently references libunwind7-dev as a build dependency for ia64.  As 
Debian is now using libunwind8,
this needs to be updated.  Patch included.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gdb depends on:
ii  libc6.1   2.25-3
ii  libexpat1 2.2.3-2
ii  liblzma5  5.2.2-1.3
ii  libncurses5   5.9-10
pn  libpython3.2  
ii  libreadline6  6.2+dfsg-0.1
ii  libtinfo5 6.0+20171125-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gdb recommends:
ii  libc6.1-dbg [libc-dbg]  2.25-3

Versions of packages gdb suggests:
pn  gdb-doc
ii  gdbserver  7.4.1+dfsg-0.1

-- no debconf information
--- debian/control.in.orig  2017-12-11 08:19:48.452235677 -0500
+++ debian/control.in   2017-12-11 08:19:56.800285880 -0500
@@ -39,7 +39,7 @@
 # Python3 build
python3-dev,
libkvm-dev [kfreebsd-any],
-   libunwind7-dev [ia64],
+   libunwind8-dev [ia64],
 Vcs-Git: git://anonscm.debian.org/pkg-gdb/gdb.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-gdb/gdb.git
 Homepage: http://www.gnu.org/s/gdb/

Bug#884007: systemtap FTBFS on ia64

[Jason Duerstock]

Source: systemtap
Severity: normal
Tags: patch

Dear Maintainer,

systemtap fails to build from source on ia64.  The attached patch should 
correct the problem spots.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- systemtap-3.1/includes/sys/sdt.h2017-12-10 06:50:27.0 -0500
+++ systemtap-3.1.orig/includes/sys/sdt.h   2017-12-10 06:32:44.722028094 
-0500
@@ -84,8 +84,12 @@
 # define _SDT_ARGFMT(no)   %n[_SDT_S##no]@_SDT_ARGTMPL(_SDT_A##no)
 
 # ifndef STAP_SDT_ARG_CONSTRAINT
+# ifdef __ia64__
+# define STAP_SDT_ARG_CONSTRAINTnr
+# else
 # define STAP_SDT_ARG_CONSTRAINTnor
 # endif
+# endif
 
 # define _SDT_STRINGIFY(x)  #x
 # define _SDT_ARG_CONSTRAINT_STRING(x)  _SDT_STRINGIFY(x)
--- systemtap-3.1/python/HelperSDT/_HelperSDT.c 2017-02-17 12:37:01.0 
-0500
+++ systemtap-3.1.orig/python/HelperSDT/_HelperSDT.c2017-12-10 
06:31:28.625516044 -0500
@@ -154,7 +154,11 @@
// it with the asm() statement. Otherwise we get a @GOTPCREL
// reference which stap can't parse.
void *fptr = _GenericGetAttr;
+#ifdef __ia64__
+   asm ("nop 0" : "=r"(fptr) : "r"(fptr));
+#else
asm ("nop" : "=r"(fptr) : "r"(fptr));
+#endif
STAP_PROBE2(HelperSDT, Init, stap_module, fptr);
 }
 return module;

Bug#883858: libunwind FTBFS on ia64

[Jason Duerstock]

Source: libunwind
Followup-For: Bug #883858

Dear Maintainer,

The Gentoo guys seem to have beaten me to the punch.  Their patches are 
available here:
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-libs/libunwind/files

I have included them along with this report for your convenience.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
https://bugs.gentoo.org/586092

this might not be correct, but at least it builds, and doesn't crash

--- a/src/coredump/_UCD_access_reg_linux.c
+++ b/src/coredump/_UCD_access_reg_linux.c
@@ -51,6 +51,9 @@ _UCD_access_reg (unw_addr_space_t as,
 #elif defined(UNW_TARGET_TILEGX)
   if (regnum < 0 || regnum > UNW_TILEGX_CFA)
 goto badreg;
+#elif defined(UNW_TARGET_IA64) || defined(UNW_TARGET_HPPA) || 
defined(UNW_TARGET_PPC32) || defined(UNW_TARGET_PPC64)
+  if (regnum < 0 || regnum >= ARRAY_SIZE(ui->prstatus->pr_reg))
+goto badreg;
 #else
 #if defined(UNW_TARGET_MIPS)
   static const uint8_t remap_regs[] =
Original libunwind release is missing a few ia64-specific files in tarball.
diff --git a/src/ia64/mk_Gcursor_i.c b/src/ia64/mk_Gcursor_i.c
new file mode 100644
index 000..67b14d5
--- /dev/null
+++ b/src/ia64/mk_Gcursor_i.c
@@ -0,0 +1,65 @@
+/* libunwind - a platform-independent unwind library
+   Copyright (C) 2003 Hewlett-Packard Co
+Contributed by David Mosberger-Tang 
+
+This file is part of libunwind.
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.  */
+
+/* Utility to generate cursor_i.h.  */
+
+#include "libunwind_i.h"
+
+#ifdef offsetof
+# undef offsetof
+#endif
+
+#define offsetof(type,field)((char *) &((type *) 0)->field - (char *) 0)
+
+#define OFFSET(sym, offset) \
+asm volatile("\n->" #sym " %0" : : "i" (offset))
+
+int
+main (void)
+{
+  OFFSET("IP_OFF",   offsetof (struct cursor, ip));
+  OFFSET("PR_OFF",   offsetof (struct cursor, pr));
+  OFFSET("BSP_OFF",  offsetof (struct cursor, bsp));
+  OFFSET("PSP_OFF",  offsetof (struct cursor, psp));
+  OFFSET("PFS_LOC_OFF",  offsetof (struct cursor, loc[IA64_REG_PFS]));
+  OFFSET("RNAT_LOC_OFF", offsetof (struct cursor, loc[IA64_REG_RNAT]));
+  OFFSET("UNAT_LOC_OFF", offsetof (struct cursor, loc[IA64_REG_UNAT]));
+  OFFSET("LC_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_LC]));
+  OFFSET("FPSR_LOC_OFF", offsetof (struct cursor, loc[IA64_REG_FPSR]));
+  OFFSET("B1_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_B1]));
+  OFFSET("B2_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_B2]));
+  OFFSET("B3_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_B3]));
+  OFFSET("B4_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_B4]));
+  OFFSET("B5_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_B5]));
+  OFFSET("F2_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_F2]));
+  OFFSET("F3_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_F3]));
+  OFFSET("F4_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_F4]));
+  OFFSET("F5_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_F5]));
+  OFFSET("FR_LOC_OFF",   offsetof (struct cursor, loc[IA64_REG_F16]));
+  OFFSET("LOC_SIZE",
+  (offsetof (struct cursor, loc[1]) - offsetof (struct cursor, loc[0])));
+  OFFSET("SIGCONTEXT_ADDR_OFF", offsetof (struct cursor, sigcontext_addr));
+  return 0;
+}
diff --git a/src/ia64/mk_Lcursor_i.c b/src/ia64/mk_Lcursor_i.c
new file mode 100644
index 000..aee2e7e
--- /dev/null
+++ b/src/ia64/mk_Lcursor_i.c
@@ -0,0 +1,2 @@
+#define UNW_LOCAL_ONLY
+#include "mk_Gcursor_i.c"
diff --git a/src/ia64/mk_cursor_i b/src/ia64/mk_cursor_i
new file mode 100755
index 000..9211f91
--- /dev/null
+++ b/src/ia64/mk_cursor_i
@@ -0,0 +1,7 @@
+#!/bin/sh
+test -z "$1" && exit 1
+echo "/* GENERATED */"
+echo 

Bug#883858: libunwind FTBFS on ia64

[Jason Duerstock]

Source: libunwind
Severity: normal

Dear Maintainer,

It appears as though some files went missing from libunwind between 1.1 and 
1.2.  It now fails to build from source:

make[1]: Leaving directory '/mnt/a/sid/libunwind-1.2.1'
   dh_auto_build
make -j2
make[1]: Entering directory '/mnt/a/sid/libunwind-1.2.1'
Making all in src
make[2]: Entering directory '/mnt/a/sid/libunwind-1.2.1/src'
make[2]: *** No rule to make target 'ia64/mk_Gcursor_i.c', needed by 
'mk_Gcursor_i.s'.  Stop.
make[2]: Leaving directory '/mnt/a/sid/libunwind-1.2.1/src'
Makefile:595: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/mnt/a/sid/libunwind-1.2.1'
dh_auto_build: make -j2 returned exit code 2
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#883850: gcc-7-cross-ports: Please add support for ia64 to gcc-cross-ports

[Jason Duerstock]

Source: gcc-7-cross-ports
Severity: normal

Dear Maintainer,

As I am working toward getting added to Debian ports, please add ia64 support 
to this cross package.

Thank you!



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#883819: openssh source includes an onerous dependency on gtk-3

[Jason Duerstock]

Source: openssh
Severity: normal
Tags: patch

Dear Maintainer,

The openssh package requires gtk-3-dev, which introduces an excessively heavy 
build footprint on systems
that don't use a GUI.  The attached patch makes this requirement optional with 
a build profile named
"pkg.openssh.nognome".

Please include this in your next source package update.

Thank you!



-- System Information:
Debian Release: buster/sid
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- debian/rules2017-10-07 08:43:16.0 -0400
+++ debian/rules2017-12-07 15:56:25.277464323 -0500
@@ -144,7 +144,9 @@
$(MAKE) -C debian/build-deb $(PARALLEL) 
ASKPASS_PROGRAM='/usr/bin/ssh-askpass'
$(MAKE) -C debian/build-udeb $(PARALLEL) 
ASKPASS_PROGRAM='/usr/bin/ssh-askpass' ssh scp sftp sshd ssh-keygen
 
+ifeq ($(filter pkg.openssh.nognome,$(DEB_BUILD_PROFILES)),)
$(MAKE) -C contrib gnome-ssh-askpass3 CC='$(CC) $(CPPFLAGS) $(CFLAGS) 
-Wall -Wl,--as-needed $(LDFLAGS)' PKG_CONFIG=$(PKG_CONFIG)
+endif
 
 override_dh_auto_build-indep:
 
--- debian/control  2017-10-07 08:43:16.0 -0400
+++ debian/control  2017-12-07 15:39:41.595079474 -0500
@@ -9,7 +9,7 @@
dpkg-dev (>= 1.16.1~),
libaudit-dev [linux-any],
libedit-dev,
-   libgtk-3-dev,
+   libgtk-3-dev ,
libkrb5-dev | heimdal-dev,
libpam0g-dev | libpam-dev,
libselinux1-dev [linux-any],
@@ -178,6 +178,7 @@
  remove it once the upgrade is complete and nothing depends on it.
 
 Package: ssh-askpass-gnome
+Build-Profiles: 
 Section: gnome
 Priority: optional
 Architecture: any

Bug#883808: libbonobo2-0 does not understand nodoc build profile

[Jason Duerstock]

Package: libbonobo2-0
Version: 2.32.1-3
Severity: normal
Tags: patch

Dear Maintainer,

the libbonobo2-0 debian package does not support the "nodoc" profile.  I 
believe the attached patch corrects this.


-- System Information:
Debian Release: buster/sid
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libbonobo2-0 depends on:
ii  libbonobo2-common  2.32.1-3
ii  libc6.12.25-3
ii  libglib2.0-0   2.54.2-1
ii  liborbit-2-0   1:2.14.19-4
ii  libxml22.9.4+dfsg1-5.1

Versions of packages libbonobo2-0 recommends:
ii  dbus-x11  1.12.2-1

Versions of packages libbonobo2-0 suggests:
pn  libbonobo2-bin  

-- no debconf information
--- debian/rules.orig   2017-12-07 14:34:41.214078334 -0500
+++ debian/rules2017-12-07 14:41:48.716809380 -0500
@@ -12,7 +12,13 @@
 DEB_DH_MAKESHLIBS_ARGS_ALL += -V 'libbonobo2-0 (>= 2.32.1-3~)'
 DEB_DH_SHLIBDEPS_ARGS_ALL += -Llibbonobo2-0
 DEB_CONFIGURE_LIBEXECDIR := 
"\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/bonobo-activation"
-DEB_CONFIGURE_EXTRA_FLAGS += --enable-gtk-doc 
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 
+ifeq ($(filter nodoc,$(DEB_BUILD_PROFILES)),)
+DEB_CONFIGURE_EXTRA_FLAGS = --enable-gtk-doc
+else
+DEB_CONFIGURE_EXTRA_FLAGS = --disable-gtk-doc
+endif
+
+DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
 install/libbonobo2-common::
rm -f $(CURDIR)/debian/tmp/usr/lib/*/bonobo/servers/broken.server
--- debian/control.in.orig  2017-12-07 14:43:58.129637658 -0500
+++ debian/control.in   2017-12-07 14:44:19.517774972 -0500
@@ -14,8 +14,8 @@
libglib2.0-dev (>= 2.26.0),
libxml2-dev (>= 2.6.7),
libpopt-dev,
-   gtk-doc-tools,
-   docbook-xml,
+   gtk-doc-tools ,
+   docbook-xml ,
autotools-dev,
libglib2.0-doc
 Standards-Version: 3.8.4

Bug#883724: mono FTBFS on ia64

[Jason Duerstock]

Package: mono
Severity: normal
Tags: patch

Dear Maintainer,

Mono fails to build from source on ia64.  At least on initial glance, this 
appears to be because it does
not recognize libatomic-ops-dev on the platform.

See attached patch.

-- System Information:
Debian Release: buster/sid
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- configure.ac.orig   2017-12-06 15:41:00.654825611 -0500
+++ configure.ac2017-12-06 15:41:17.758945149 -0500
@@ -3194,7 +3194,7 @@
 dnl Use GCC atomic ops if they work on the target.
 if test x$GCC = "xyes"; then
case $TARGET in
-   X86 | AMD64 | ARM | ARM64 | POWERPC | POWERPC64 | MIPS | S390X | SPARC 
| SPARC64)
+   X86 | AMD64 | ARM | ARM64 | POWERPC | POWERPC64 | MIPS | S390X | SPARC 
| SPARC64 | IA64)
AC_DEFINE(USE_GCC_ATOMIC_OPS, 1, [...])
;;
esac

Bug#883308: libseccomp2 is missing ia64 support

[Jason Duerstock]

Package: libseccomp2
Severity: normal

Dear Maintainer,

libseccomp2 is missing ia64 support.  it would be awfully nice if it was added.
(I hope to add it myself at some point, and this seems like a good place for a 
reminder.)

Thanks,

Jason


-- System Information: Debian Release: buster/sid Architecture: ia64
Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Bug#883285: glibc: ia64 glibc crashes on thread exit

[Jason Duerstock]

Source: glibc
Severity: normal
Tags: patch

Dear Maintainer,

glibc 2.24 has an ia64 bug as detailed here:
https://sourceware.org/bugzilla/show_bug.cgi?id=21672

The patch as scheduled to be merged into 2.27 is available here:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=patch;h=01b87c656f670863ce437421b8e9278200965d38

Thank you!

Jason



-- System Information:
Debian Release: buster/sid
Architecture: ia64

Kernel: Linux 3.14-0.bpo.2-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
>From 01b87c656f670863ce437421b8e9278200965d38 Mon Sep 17 00:00:00 2001
From: Adhemerval Zanella 
Date: Mon, 28 Aug 2017 11:24:35 -0300
Subject: [PATCH] ia64: Fix thread stack allocation permission set (BZ #21672)

This patch fixes ia64 failures on thread exit by madvise the required
area taking in consideration its disjoing stacks
(NEED_SEPARATE_REGISTER_STACK).  Also the snippet that setup the
madvise call to advertise kernel the area won't be used anymore in
near future is reallocated in allocatestack.c (for consistency to
put all stack management function in one place).

Checked on x86_64-linux-gnu and i686-linux-gnu for sanity (since
it is not expected code changes for architecture that do not
define NEED_SEPARATE_REGISTER_STACK) and also got a report that
it fixes ia64-linux-gnu failures from Sergei Trofimovich
.

	[BZ #21672]
	* nptl/allocatestack.c [_STACK_GROWS_DOWN] (setup_stack_prot):
	Set to use !NEED_SEPARATE_REGISTER_STACK as well.
	(advise_stack_range): New function.
	* nptl/pthread_create.c (START_THREAD_DEFN): Move logic to mark
	stack non required to advise_stack_range at allocatestack.c
---
 ChangeLog |  9 +
 nptl/allocatestack.c  | 29 -
 nptl/pthread_create.c | 27 ++-
 3 files changed, 39 insertions(+), 26 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 07cf8dd..b2016ca 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,12 @@
+2017-08-29  Adhemerval Zanella  
+
+	[BZ #21672]
+	* nptl/allocatestack.c [_STACK_GROWS_DOWN] (setup_stack_prot):
+	Set to use !NEED_SEPARATE_REGISTER_STACK as well.
+	(advise_stack_range): New function.
+	* nptl/pthread_create.c (START_THREAD_DEFN): Move logic to mark
+	stack non required to advise_stack_range at allocatestack.c
+
 2017-08-29  Szabolcs Nagy  
 
 	* sysdeps/unix/sysv/linux/aarch64/sys/procfs.h: Use __uint64_t.
diff --git a/nptl/allocatestack.c b/nptl/allocatestack.c
index 6d1bcaa..8766deb 100644
--- a/nptl/allocatestack.c
+++ b/nptl/allocatestack.c
@@ -356,7 +356,7 @@ setup_stack_prot (char *mem, size_t size, char *guard, size_t guardsize,
 		  const int prot)
 {
   char *guardend = guard + guardsize;
-#if _STACK_GROWS_DOWN
+#if _STACK_GROWS_DOWN && !defined(NEED_SEPARATE_REGISTER_STACK)
   /* As defined at guard_position, for architectures with downward stack
  the guard page is always at start of the allocated area.  */
   if (__mprotect (guardend, size - guardsize, prot) != 0)
@@ -372,6 +372,33 @@ setup_stack_prot (char *mem, size_t size, char *guard, size_t guardsize,
   return 0;
 }
 
+/* Mark the memory of the stack as usable to the kernel.  It frees everything
+   except for the space used for the TCB itself.  */
+static inline void
+__always_inline
+advise_stack_range (void *mem, size_t size, uintptr_t pd, size_t guardsize)
+{
+  uintptr_t sp = (uintptr_t) CURRENT_STACK_FRAME;
+  size_t pagesize_m1 = __getpagesize () - 1;
+#if _STACK_GROWS_DOWN && !defined(NEED_SEPARATE_REGISTER_STACK)
+  size_t freesize = (sp - (uintptr_t) mem) & ~pagesize_m1;
+  assert (freesize < size);
+  if (freesize > PTHREAD_STACK_MIN)
+__madvise (mem, freesize - PTHREAD_STACK_MIN, MADV_DONTNEED);
+#else
+  /* Page aligned start of memory to free (higher than or equal
+ to current sp plus the minimum stack size).  */
+  uintptr_t freeblock = (sp + PTHREAD_STACK_MIN + pagesize_m1) & ~pagesize_m1;
+  uintptr_t free_end = (pd - guardsize) & ~pagesize_m1;
+  if (free_end > freeblock)
+{
+  size_t freesize = free_end - freeblock;
+  assert (freesize < size);
+  __madvise ((void*) freeblock, freesize, MADV_DONTNEED);
+}
+#endif
+}
+
 /* Returns a usable stack for a new thread either by allocating a
new stack or reusing a cached stack of sufficient size.
ATTR must be non-NULL and point to a valid pthread_attr.
diff --git a/nptl/pthread_create.c b/nptl/pthread_create.c
index 2f8ada3..83b88bf 100644
--- a/nptl/pthread_create.c
+++ b/nptl/pthread_create.c
@@ -551,31 +551,8 @@ START_THREAD_DEFN
 }
 #endif
 
-  /* Mark the memory of the stack as usable to the kernel.  We free
- everything except for the space used for the TCB itself.  */
-  size_t pagesize_m1 = __getpagesize () - 1;
-#ifdef _STACK_GROWS_DOWN
-  char *sp = CURRENT_STACK_FRAME;
-  size_t freesize = (sp - (char *) 

Bug#883012: glibc: add/fix ia64 support

[Jason Duerstock]

Source: glibc
Severity: normal
Tags: patch

Dear Maintainer,

The attached patch fixes the debian build infrastructure related to the ia64 
platform.
Please include it in the next release.

Thank you.


-- System Information:
Debian Release: buster/sid
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- /dev/null	2017-11-02 15:00:19.23689 -0400
+++ debian/sysdeps/ia64.mk	2017-11-28 11:53:40.800452725 -0500
@@ -0,0 +1,2 @@
+# configuration options for all flavours
+libc = libc6.1
--- debian/rules.d/control.mk.orig	2017-11-28 11:55:14.529110191 -0500
+++ debian/rules.d/control.mk	2017-11-28 11:55:34.181248078 -0500
@@ -3,7 +3,7 @@
 libc0_3_archs := hurd-i386
 libc6_archs   := amd64 arm64 armel armhf hppa i386 m68k mips mipsel mipsn32 mipsn32el mips64 mips64el mipsr6 mipsr6el \
  mipsn32r6 mipsn32r6el mips64r6 mips64r6el nios2 powerpc powerpcspe ppc64 ppc64el sparc sparc64 s390x sh3 sh4 x32
-libc6_1_archs := alpha
+libc6_1_archs := alpha ia64
 
 control_deps := $(wildcard debian/control.in/*) $(addprefix debian/control.in/, $(libc_packages))
 triggers := binutils, linux-libc-dev [linux-any], $(BASE_CC)$(DEB_GCC_VERSION)
--- debian/control.in/main.orig	2017-11-28 11:57:01.701862299 -0500
+++ debian/control.in/main	2017-11-28 11:57:25.738031026 -0500
@@ -143,8 +143,8 @@
 Section: oldlibs
 Multi-Arch: foreign
 Depends: ${misc:Depends},
-	 libc6 (>= 2.3.6-2) [!any-i386 !alpha !armhf !hurd-any !kfreebsd-any],
- libc6.1 (>= 2.3.6-2) [alpha],
+	 libc6 (>= 2.3.6-2) [!any-i386 !alpha !armhf !hurd-any !ia64 !kfreebsd-any],
+ libc6.1 (>= 2.3.6-2) [alpha ia64],
  libc0.3 (>= 2.3.6-2) [!linux-any !kfreebsd-any !hurd-i386],
  libc0.1 (>= 2.3.6-2) [!linux-any !hurd-any !kfreebsd-i386],
  libc6 (>= 2.13-5) [armhf i386],

Bug#882874: glibc 2.25 FTBFS on ia64

[Jason Duerstock]

Source: glibc
Followup-For: Bug #882874

This patch appears to correct the problem.

-- System Information:
Debian Release: buster/sid
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- sysdeps/ia64/dl-machine.h
+++ sysdeps/ia64/dl-machine.h
@@ -45,7 +45,8 @@
 }
 
 #define ELF_MACHINE_BEFORE_RTLD_RELOC(dynamic_info)		\
-	__ia64_init_bootstrap_fdesc_table (_map);
+	__ia64_init_bootstrap_fdesc_table (_map);	\
+	_dl_fptr_init();
 
 /* Return nonzero iff ELF header is compatible with the running host.  */
 static inline int __attribute__ ((unused))

Bug#882874: glibc 2.25 FTBFS on ia64

[Jason Duerstock]

I understand.  Thank you.

On Mon, Nov 27, 2017 at 3:23 PM, Aurelien Jarno <aurel...@aurel32.net>
wrote:

> Hi,
>
> On 2017-11-27 13:08, Jason Duerstock wrote:
> > Source: glibc
> > Version: 2.25
> > Severity: normal
> >
> > Dear Maintainer,
> > When trying to build glibc 2.25 under ia64, ld.so does not build
> properly,
> > and produces a segmentation fault immediately upon execution.
>
> Just to be clear, Debian doesn't support ia64 anymore. There is no
> problem to add patches to fix this issue, but don't expect an active
> work on our side to fix it.
>
> Aurelien
>
> --
> Aurelien Jarno  GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
>

Bug#882874: glibc 2.25 FTBFS on ia64

[Jason Duerstock]

Source: glibc
Version: 2.25
Severity: normal

Dear Maintainer,
When trying to build glibc 2.25 under ia64, ld.so does not build properly,
and produces a segmentation fault immediately upon execution.

The following backtrace is common to every combination of toolchain part and 
compilation flag I've tried:

GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "ia64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./ld.so...done.
(gdb) run
Starting program: /root/sid/glibc-2.25/build-tree/ia64-libc/elf/ld.so
Failed to read a valid object file image from memory.

Program received signal SIGSEGV, Segmentation fault.
make_fdesc (gp=2305843043573611080, ip=) at dl-fptr.c:127
127   old = root->first_unused;
(gdb) bt
#0  make_fdesc (gp=2305843043573611080, ip=) at dl-fptr.c:127
#1  _dl_make_fptr (map=0x2008000553a8 <_rtld_local+2448>, 
sym=0x20080540, ip=2305843043573579456) at dl-fptr.c:243
#2  0x20084440 in elf_machine_rela (skip_ifunc=0, 
reloc_addr_arg=0x200800050640 <_rtld_local_ro+208>,
version=, sym=0x20080540, reloc=0x20080f68, 
map=0x2008000553a8 <_rtld_local+2448>)
at ../sysdeps/ia64/dl-machine.h:432
#3  elf_dynamic_do_Rela (skip_ifunc=0, lazy=0, nrelative=, 
relsize=, reladdr=,
map=0x2008000553a8 <_rtld_local+2448>) at do-rel.h:137
#4  _dl_start (arg=0x6fffb670) at rtld.c:502
#5  0x20081990 in _start ()
(gdb)

It appears that local->root is set to NULL at execution time, even before any 
instructions are set.

I have tried binutils (2.25, 2.28, 2.29.1) and gcc 6.4.0 and 7.2.0.


-- System Information:
Debian Release: buster/sid
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Bug#881818: xsltproc: FTBFS on ia64

[Jason Duerstock]

Package: xsltproc
Version: 1.1.26-14.1
Severity: normal
Tags: patch

Dear Maintainer,
When trying to build on ia64, the compiler complains that it cannot find 
INT_MAX for libxslt/transform.c.
The attached patch #includes the appropriate system header file.


-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xsltproc depends on:
ii  libc6.1 2.13-38+deb7u10
ii  libxml2 2.8.0+dfsg1-7+wheezy5
ii  libxslt1.1  1.1.26-14.1

xsltproc recommends no packages.

xsltproc suggests no packages.

-- no debconf information
--- libxslt/transform.c.orig	2017-11-15 09:21:22.240917554 -0500
+++ libxslt/transform.c	2017-11-15 09:21:33.780859781 -0500
@@ -21,6 +21,7 @@
 
 #include 
 #include 
+#include 
 
 #include 
 #include 

Bug#743065: chicken: also FTBFS on ia64

[Jason Duerstock]

Package: chicken
Version: 4.11.0-1
Followup-For: Bug #743065

Dear Maintainer,
This bug affects ia64 in 4.11.0-1 as well.  The problem is that the build 
system assums that LDFLAGS will always just
include "-Wl,..." and it is safe to directly append to it.  The attached patch 
remedies that.

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- debian/rules	2016-12-14 17:41:18.0 -0500
+++ ../c.d.r	2017-11-14 11:45:18.366307669 -0500
@@ -35,7 +35,7 @@
 # placed by dpkg-buildpackage. If absolute files are specified,
 # i.e. /var/lib/chicken, then those files will be installed on the
 # build system, but will not end up in the package.
-	$(MAKE) PREFIX="$(CURDIR)/debian/tmp/usr" LINKER_LINK_SHARED_DLOADABLE_OPTIONS='-L. -shared $(LDFLAGS),-R"."' LINKER_LINK_SHARED_PROGRAM_OPTIONS='$(LDFLAGS),-R"."' LIBCHICKEN_SO_LINKER_OPTIONS='$(LDFLAGS),-soname,libchicken.so.8' VARDIR="$(CURDIR)/debian/tmp/var/lib" install
+	$(MAKE) PREFIX="$(CURDIR)/debian/tmp/usr" LINKER_LINK_SHARED_DLOADABLE_OPTIONS='-L. -shared $(LDFLAGS) -Wl,-R"."' LINKER_LINK_SHARED_PROGRAM_OPTIONS='$(LDFLAGS) -Wl,-R"."' LIBCHICKEN_SO_LINKER_OPTIONS='$(LDFLAGS) -Wl,-soname,libchicken.so.8' VARDIR="$(CURDIR)/debian/tmp/var/lib" install
 #	chrpath -d $(CURDIR)/debian/tmp/usr/bin/*
 	chrpath -d $(CURDIR)/debian/tmp/var/lib/chicken/8/*.so
 

Bug#881611: libbsd: build test for ia64 is incorrect

[Jason Duerstock]

Source: libbsd
Severity: normal

Dear Maintainer,

In test/nlist.c, there is an incorrect test for the ia64 processor.  The 
attached patch removes it.

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- test/nlist.c.orig	2017-11-13 06:44:04.609586836 -0500
+++ test/nlist.c	2017-11-13 06:44:47.109587129 -0500
@@ -69,8 +69,8 @@
 	rc = nlist(argv[0], nl);
 	assert(rc == 0);
 
-#if defined(__ia64__) || (defined(__powerpc64__) && _CALL_ELF == 1)
-	/* On IA64 and PowerPC 64-bit ELFv1, the functions are stored in
+#if defined(__powerpc64__) && _CALL_ELF == 1
+	/* On PowerPC 64-bit ELFv1, the functions are stored in
 	 * the .text sections but they are accessed through a function
 	 * descriptor stored in a data section, for example for PowerPC
 	 * 64-bit that section is called .opd. */

Bug#881372: gcc-7: gccgo runtime fails to build on ia64

[Jason Duerstock]

Will do, thank you.

On Sun, Nov 12, 2017 at 6:34 AM, Matthias Klose <d...@debian.org> wrote:

> On 10.11.2017 21:28, Jason Duerstock wrote:
> > Package: gcc-7
> > Version: 7.2.0-12
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > When trying to build the gccgo runtime on ia64, the build fails with
> undefined references to 'lfstackPack' and 'lfstackUnpack'.
> >
> > I believe this is fixed by the attached patch.
>
> Please submit this patch upstream, tested against trunk. I'd like to avoid
> building up a stack of unsupported ia64 patches locally.  Please also test
> your
> patches against gcc-8.
>

Bug#881372: gcc-7: gccgo runtime fails to build on ia64

[Jason Duerstock]

Package: gcc-7
Version: 7.2.0-12
Severity: normal

Dear Maintainer,

When trying to build the gccgo runtime on ia64, the build fails with undefined 
references to 'lfstackPack' and 'lfstackUnpack'.

I believe this is fixed by the attached patch.

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-7 depends on:
ii  binutils  2.25-5+deb8u1
ii  cpp-7 7.2.0-12
ii  gcc-7-base7.2.0-12
ii  libc6.1   2.13-38+deb7u10
ii  libcc1-0  7.2.0-12
ii  libgcc-7-dev  7.2.0-12
ii  libgcc1   1:7.2.0-12
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-12
ii  libunwind70.99-0.3
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6.1-dev  2.13-38+deb7u10

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- debconf information excluded
--- src/libgo/go/runtime/lfstack_64bit.go.orig	2017-11-10 14:19:42.699987069 -0500
+++ src/libgo/go/runtime/lfstack_64bit.go	2017-11-10 14:19:52.635987138 -0500
@@ -2,7 +2,7 @@
 // Use of this source code is governed by a BSD-style
 // license that can be found in the LICENSE file.
 
-// +build amd64 arm64 mips64 mips64le ppc64 ppc64le s390x arm64be alpha sparc64
+// +build amd64 arm64 mips64 mips64le ppc64 ppc64le s390x arm64be alpha sparc64 ia64
 
 package runtime
 

Bug#881294: guile-2.0 FTBFS for ia64

[Jason Duerstock]

Package: guile-2.0
Version: 2.0.13+1-4
Severity: normal

Dear Maintainer,

guile-2.0 contains a long-standing bug on the ia64 platform.  The structure 
used for the setjmp()/longjmp()
implementation is not properly initialized when a thread is created.  More 
detail is available here:

https://lists.gnu.org/archive/html/bug-guile/2017-11/msg0.html

I have included a patch against 2.0.13.

Thank you for your time and your work.

Jason


-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages guile-2.0 depends on:
ii  guile-2.0-libs  2.0.13+1-4

guile-2.0 recommends no packages.

Versions of packages guile-2.0 suggests:
pn  guile-2.0-doc  

-- debconf information excluded
diff --git a/libguile/threads.c b/libguile/threads.c
index dcbd24d..0f688c3 100644
--- a/libguile/threads.c
+++ b/libguile/threads.c
@@ -552,6 +552,7 @@ guilify_self_1 (struct GC_stack_base *base)
   t.base = base->mem_base;
 #ifdef __ia64__
   t.register_backing_store_base = base->reg_base;
+  t.pending_rbs_continuation = 0;
 #endif
   t.continuation_root = SCM_EOL;
   t.continuation_base = t.base;

Bug#881288: gcc-7 fails to patch when old distribution detected

[Jason Duerstock]

Package: gcc-7
Version: 7.2.0-12
Severity: normal

Dear Maintainer,

When gcc-7 detects one of many outdated distributions, it attempts to apply the 
"gcc-hash-style-both" patch,
rather than "gcc-hash-style-gnu".  gcc-hash-style-both is sufficiently crufty 
that it fails to apply.

I suggest either removing the detection, or rebasing the patch.  I have 
included a patch to remove the detection.

Thank you for your time and work.

Jason

-- System Information:
Debian Release: 7.11
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable')
Architecture: ia64

Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-7 depends on:
ii  binutils  2.25-5+deb8u1
ii  cpp-7 7.2.0-12
ii  gcc-7-base7.2.0-12
ii  libc6.1   2.13-38+deb7u10
ii  libcc1-0  7.2.0-12
ii  libgcc-7-dev  7.2.0-12
ii  libgcc1   1:7.2.0-12
ii  libgmp10  2:6.1.2+dfsg-1.1
ii  libisl15  0.18-1
ii  libmpc3   1.0.3-2
ii  libmpfr4  3.1.6-1
ii  libstdc++67.2.0-12
ii  libunwind70.99-0.3
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages gcc-7 recommends:
ii  libc6.1-dev  2.13-38+deb7u10

Versions of packages gcc-7 suggests:
pn  gcc-7-doc 
pn  gcc-7-locales 
pn  libasan4-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

-- debconf information:
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line 
30.
--- debian/rules.patch.orig	2017-11-09 12:17:23.775340303 -0500
+++ debian/rules.patch	2017-11-09 12:17:56.799340531 -0500
@@ -39,13 +39,8 @@
 	gcc-textdomain \
 	gcc-driver-extra-langs$(if $(with_linaro_branch),-linaro)
 
-ifneq (,$(filter $(distrelease),etch lenny squeeze wheezy dapper hardy intrepid jaunty karmic lucid))
-  debian_patches += gcc-hash-style-both
-else
-  debian_patches += gcc-hash-style-gnu
-endif
-
 debian_patches += \
+	gcc-hash-style-gnu \
 	libstdc++-pic \
 	libstdc++-doclink \
 	libstdc++-man-3cxx \

Bug#879959: gcc-7 uses outdated version number for libunwind when building for ia64

[Jason Duerstock]

Source: gcc-7
Severity: normal

Dear Maintainer,

When attempting to build gcc-7 for ia64, the package tries to require libunwind7
when the current version is libunwind8.  The attached patch should correct this.

Jason
diff -u gcc-7-7.2.0/debian/control gcc-7-7.2.0/debian/control
--- gcc-7-7.2.0/debian/control
+++ gcc-7-7.2.0/debian/control
@@ -9,7 +9,7 @@
   libc6.1-dev (>= 2.13-5) [alpha ia64] | libc0.3-dev (>= 2.13-5) [hurd-i386] | libc0.1-dev (>= 2.13-5) [kfreebsd-i386 kfreebsd-amd64] | libc6-dev (>= 2.13-5), libc6-dev (>= 2.13-31) [armel armhf], libc6-dev-amd64 [i386 x32], libc6-dev-sparc64 [sparc], libc6-dev-sparc [sparc64], libc6-dev-s390 [s390x], libc6-dev-s390x [s390], libc6-dev-i386 [amd64 x32], libc6-dev-powerpc [ppc64], libc6-dev-ppc64 [powerpc], libc0.1-dev-i386 [kfreebsd-amd64], lib32gcc1 [amd64 ppc64 kfreebsd-amd64 mipsn32 mipsn32el mips64 mips64el s390x sparc64 x32], libn32gcc1 [mips mipsel mips64 mips64el], lib64gcc1 [i386 mips mipsel mipsn32 mipsn32el powerpc sparc s390 x32], libc6-dev-mips64 [mips mipsel mipsn32 mipsn32el], libc6-dev-mipsn32 [mips mipsel mips64 mips64el], libc6-dev-mips32 [mipsn32 mipsn32el mips64 mips64el], libc6-dev-x32 [amd64 i386], libx32gcc1 [amd64 i386], libc6.1-dbg [alpha ia64] | libc0.3-dbg [hurd-i386] | libc0.1-dbg [kfreebsd-i386 kfreebsd-amd64] | libc6-dbg, 
   kfreebsd-kernel-headers (>= 0.84) [kfreebsd-any], linux-libc-dev [m68k], 
   m4, libtool, autoconf2.64, 
-  libunwind7-dev (>= 0.98.5-6) [ia64], libatomic-ops-dev [ia64], 
+  libunwind8-dev [ia64], libatomic-ops-dev [ia64], 
   autogen , gawk, lzma, xz-utils, patchutils, 
   zlib1g-dev, systemtap-sdt-dev [linux-any kfreebsd-any hurd-any], 
   binutils:native (>= 2.29.1) | binutils-multiarch:native (>= 2.29.1), binutils-hppa64-linux-gnu:native (>= 2.29.1) [hppa amd64 i386 x32], 
diff -u gcc-7-7.2.0/debian/control.m4 gcc-7-7.2.0/debian/control.m4
--- gcc-7-7.2.0/debian/control.m4
+++ gcc-7-7.2.0/debian/control.m4
@@ -74,7 +74,7 @@
   LIBC_BUILD_DEP, LIBC_BIARCH_BUILD_DEP LIBC_DBG_DEP
   kfreebsd-kernel-headers (>= 0.84) [kfreebsd-any], linux-libc-dev [m68k],
   AUTO_BUILD_DEP BASE_BUILD_DEP
-  libunwind7-dev (>= 0.98.5-6) [ia64], libatomic-ops-dev [ia64],
+  libunwind8-dev [ia64], libatomic-ops-dev [ia64],
   autogen , gawk, lzma, xz-utils, patchutils,
   zlib1g-dev, SDT_BUILD_DEP
   BINUTILS_BUILD_DEP,
diff -u gcc-7-7.2.0/debian/rules.conf gcc-7-7.2.0/debian/rules.conf
--- gcc-7-7.2.0/debian/rules.conf
+++ gcc-7-7.2.0/debian/rules.conf
@@ -373,11 +373,13 @@
   GCC_MULTILIB_BUILD_DEP = g++-multilib [$(multilib_archs)]$(pf_ncross),
 endif
 
-LIBUNWIND_DEV_DEP := libunwind7-dev$(LS)$(AQ) (>= 0.98.5-6)
+LIBUNWIND_DEV_DEP := libunwind8-dev$(LS)$(AQ)
 LIBUNWIND_BUILD_DEP := $(LIBUNWIND_DEV_DEP) [ia64],
 LIBATOMIC_OPS_BUILD_DEP := libatomic-ops-dev$(LS) [ia64],
 ifneq ($(DEB_TARGET_ARCH),ia64)
   LIBUNWIND_DEV_DEP := # nothing
+else ifneq (,$(filter $(DEB_STAGE),stage1 stage2))
+  LIBUNWIND_DEV_DEP := # nothing
 endif
 
 ifneq (,$(filter $(distrelease),lenny etch squeeze dapper hardy jaunty karmic lucid maverick natty))