Skip to content
Snippets Groups Projects
Commit f6172702 authored by Samuel Thibault's avatar Samuel Thibault
Browse files

debian/libc0.3.symbols.hurd-amd64: Fix symbols for hurd-amd64

libnsl and libutil are not actually built any more, only for
compatibility for archs supported in older releases.

The host_kernel_version RPC was actually dropped on 64bit.
parent 677e9a99
No related branches found
No related tags found
No related merge requests found
......@@ -2,6 +2,7 @@ glibc (2.38-2) UNRELEASED; urgency=medium
 
* debian/patches/hurd-i386/git-powerpc-longjmp.diff: Fix build after chk
hidden builtin fix.
* debian/libc0.3.symbols.hurd-amd64: Fix symbols for hurd-amd64.
 
-- Samuel Thibault <sthibault@debian.org> Fri, 04 Aug 2023 14:08:45 +0200
 
......
......@@ -26,8 +26,6 @@ libmemusage.so #PACKAGE# #MINVER#
munmap@Base 2.38
realloc@Base 2.38
#include "symbols.wildcards"
libnsl.so.1 #PACKAGE# #MINVER#
#include "symbols.wildcards"
libnss_compat.so.2 #PACKAGE# #MINVER#
#include "symbols.wildcards"
libnss_dns.so.2 #PACKAGE# #MINVER#
......@@ -44,8 +42,6 @@ libresolv.so.2 #PACKAGE# #MINVER#
#include "symbols.wildcards"
librt.so.1 #PACKAGE# #MINVER#
#include "symbols.wildcards"
libutil.so.1 #PACKAGE# #MINVER#
#include "symbols.wildcards"
libanl.so.1 #PACKAGE# #MINVER#
#include "symbols.wildcards"
###
......@@ -851,11 +847,10 @@ libmachuser.so.1 #PACKAGE# #MINVER#
__gsync_wake@Base 2.38
__host_adjust_time64@Base 2.38
__host_adjust_time@Base 2.38
__host_kernel_version@Base 2.38
__host_get_kernel_version@Base 2.38
__host_get_time64@Base 2.38
__host_get_time@Base 2.38
__host_info@Base 2.38
__host_kernel_version@Base 2.38
__host_processor_set_priv@Base 2.38
__host_processor_sets@Base 2.38
__host_processors@Base 2.38
......@@ -1018,7 +1013,6 @@ libmachuser.so.1 #PACKAGE# #MINVER#
host_get_time64@Base 2.38
host_get_time@Base 2.38
host_info@Base 2.38
host_kernel_version@Base 2.38
host_processor_set_priv@Base 2.38
host_processor_sets@Base 2.38
host_processors@Base 2.38
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment