Source: orc
Version: 1:0.4.39-2
Severity: important
Tags: patch

Hello,

orc currently FTBFS on hurd-amd64 because of symbols, could you apply
the attached fix?

Thanks,
Samuel

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unreleased'), 
(500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.9.8-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Samuel
<c> hiri, le cri ici, c des marrants
<c> j'ai un rep ".uglyhackdirectorywithoutacls" ds mon home
 -+- #ens-mim en stage -+-
--- debian/liborc-0.4-0t64.symbols.orig 2024-07-25 22:23:54.000000000 +0000
+++ debian/liborc-0.4-0t64.symbols      2024-07-25 22:09:29.000000000 +0000
@@ -160,7 +161,7 @@
  orc_mips_emit_swr@Base 1:0.4.34
  orc_mips_emit_wsbh@Base 1:0.4.34
  (arch=mipsel)orc_mips_get_cpu_flags@Base 1:0.4.34
- (arch=amd64 i386 hurd-i386)orc_mmx_get_cpu_flags@Base 1:0.4.34
+ (arch=any-amd64 any-i386)orc_mmx_get_cpu_flags@Base 1:0.4.34
  orc_mmx_load_constant@Base 1:0.4.34
  orc_neon64_reg_name_vector@Base 1:0.4.34
  orc_neon_emit_loadil@Base 1:0.4.34
@@ -242,7 +244,7 @@
  orc_program_take_code@Base 1:0.4.34
  orc_rule_register@Base 1:0.4.34
  orc_rule_set_new@Base 1:0.4.34
- (arch=amd64 i386 hurd-i386)orc_sse_get_cpu_flags@Base 1:0.4.34
+ (arch=any-amd64 any-i386)orc_sse_get_cpu_flags@Base 1:0.4.34
  orc_sse_load_constant@Base 1:0.4.34
  orc_sse_restore_mxcsr@Base 1:0.4.34
  orc_sse_set_mxcsr@Base 1:0.4.34

Reply via email to