[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1020280: marked as done (mixxx FTBFs on hppa architecture (with patch))

Your message dated Sun, 09 Oct 2022 15:06:05 +0000
with message-id <E1ohXsT-006Q1D-FP@fasolo.debian.org>
and subject line Bug#1020280: fixed in mixxx 2.3.3~dfsg-2
has caused the Debian Bug report #1020280,
regarding mixxx FTBFs on hppa architecture (with patch)
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1020280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020280
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: mixxx
Version: 2.3.3~dfsg-1
Severity: important
Tags: hppa, patch, ftbfs

attached patch fixes this build error on hppa:

In file included from /<<PKGBUILDDIR>>/lib/benchmark/src/sysinfo.cc:64:
/<<PKGBUILDDIR>>/lib/benchmark/src/cycleclock.h:219:2: error: #error You need to define CycleTimer for your OS and CPU
  219 | #error You need to define CycleTimer for your OS and CPU

Please include in next upload.
Thanks!
Helge
diff -up ./lib/benchmark/src/cycleclock.h.org ./lib/benchmark/src/cycleclock.h
--- ./lib/benchmark/src/cycleclock.h.org	2022-09-19 06:14:28.454775112 +0000
+++ ./lib/benchmark/src/cycleclock.h	2022-09-19 06:20:45.298702719 +0000
@@ -108,6 +108,10 @@ inline BENCHMARK_ALWAYS_INLINE int64_t N
   int64_t itc;
   asm("mov %0 = ar.itc" : "=r"(itc));
   return itc;
+#elif defined(__hppa__)
+  unsigned long cr16;
+  asm("mfctl 16,%0" : "=r" (cr16));
+  return cr16;
 #elif defined(COMPILER_MSVC) && defined(_M_IX86)
   // Older MSVC compilers (like 7.x) don't seem to support the
   // __rdtsc intrinsic properly, so I prefer to use _asm instead

--- End Message ---
--- Begin Message --- 
Source: mixxx
Source-Version: 2.3.3~dfsg-2
Done: Dennis Braun <d_braun@kabelmail.de>

We believe that the bug you reported is fixed in the latest version of
mixxx, 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 1020280@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dennis Braun <d_braun@kabelmail.de> (supplier of updated mixxx 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Mon, 19 Sep 2022 19:41:47 +0200
Source: mixxx
Architecture: source
Version: 2.3.3~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Dennis Braun <d_braun@kabelmail.de>
Closes: 1020280
Changes:
 mixxx (2.3.3~dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS on hppa build, thanks to Helge Deller (Closes: #1020280)
Checksums-Sha1:
 e270de998615286b9c89ee20aada2b762b256cb5 2949 mixxx_2.3.3~dfsg-2.dsc
 18af19346443262aeda4978b833b523f01f70415 27964 mixxx_2.3.3~dfsg-2.debian.tar.xz
Checksums-Sha256:
 733bdef96a70e4864bf0f522f4aef4908ced3a7cf4a4ab7a38526d97b7d60391 2949 mixxx_2.3.3~dfsg-2.dsc
 41d49a76348e22e3c40e3b22db316ce57bbdf7c14d9b864c351acdb957b3ed34 27964 mixxx_2.3.3~dfsg-2.debian.tar.xz
Files:
 6e43b2b91c5f596b1646683837bd9420 2949 sound optional mixxx_2.3.3~dfsg-2.dsc
 1105cb9f5d83f981fdb00e3e5be45140 27964 sound optional mixxx_2.3.3~dfsg-2.debian.tar.xz

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

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmNC4ZEACgkQafL8UW6n
GZMw3xAAphhNdRAEwEUgL0i7IHAssFVJ/OT5VIFqnYAGHYi7DjlHdrPbK2SDOEAk
PAVjD4rJ30TCrEQblJutPsz9j0JYu4p7/c8DKYiA5AHQPb/4bIrb/5SnVJf92VGT
/jGdPG/541g3FJkZrjPQKQoQy/wiCAxeemGCRpfziZ1ieR/7H6XbC29WTq2JA2r7
CAHR611blJtA430VdAI+7M1UyrB+puwyVtG7CFLzLFjiIqWk+iG/qI3DDF4iwcKo
0/19loEouX+WT67541Ii6gVrtvk0HsO2CvCW8vDWYqGZ+t1z9a7xmSgG5mhRNtcA
MXmWOT498eHAWPNmm3HNTeFAFdV8j7metYPEXqFOQsf0XwWwOnau86xtbAGk2j3z
Fd8cMfHYMkOTGwPPVU1yDOCKiKJXl+3SOOjp5QFO9FnN92Ew8AGFI5XW7dt/Mq1L
5VEMu+dbWVnbbnWnSLD2oKmvUvCNBleSy8yMixuwVWEQOz7TSOpb27olwA2rKx/E
DIde84umNGj+Iz7AHe0666uvIkUg9YSzc15HNKoLlosKvN5EMeAaQwrGNtDORmHe
hlAoRxjNv+2P+Ea0nD3pIN0NTsPE6fMCPKfI5TZUnyHfmf9g8fiL81L3PFum2XSy
GPxhPH+aMGsec53EAfQMKs86X2X5ih83YkHBb8sU0hWKbyTrsW0=
=e/BV
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: