From: Lukasz Majewski <lukma@denx.de>
To: Joseph Myers <joseph@codesourcery.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Arnd Bergmann <arnd@arndb.de>,
GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell <carlos@redhat.com>,
Lukasz Majewski <lukma@denx.de>
Subject: [PATCH] support: arm: Add libc_do_syscall function to libsupport routines
Date: Mon, 15 Mar 2021 16:47:23 +0100 [thread overview]
Message-ID: <20210315154723.11687-1-lukma@denx.de> (raw)
The ARM port requires the __libc_do_syscall function to be able to call
utimensat_time64 syscall required to check if file system supports 64
bit time.
This patch adds the sysdeps/unix/sysv/linux/arm/libc-do-syscall.S to
libsupport routines.
It fixes the following error on ARM 32 bit port:
y2038-glibc/support/support_path_support_time64.c:34: undefined reference to
`__libc_do_syscall'
collect2: error: ld returned 1 exit status
---
sysdeps/unix/sysv/linux/arm/Makefile | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/sysdeps/unix/sysv/linux/arm/Makefile b/sysdeps/unix/sysv/linux/arm/Makefile
index abdf01f00c..2344e74554 100644
--- a/sysdeps/unix/sysv/linux/arm/Makefile
+++ b/sysdeps/unix/sysv/linux/arm/Makefile
@@ -55,6 +55,11 @@ LDFLAGS-tst-rfc3484-2 += $(common-objpfx)csu/libc-do-syscall.o
LDFLAGS-tst-rfc3484-3 += $(common-objpfx)csu/libc-do-syscall.o
endif
+ifeq ($(subdir),support)
+libsupport-sysdep_routines += libc-do-syscall
+libsupport-static-only-routines += libc-do-syscall
+endif
+
abi-variants := soft hard
ifeq (,$(filter $(default-abi),$(abi-variants)))
--
2.20.1
next reply other threads:[~2021-03-15 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:47 Lukasz Majewski [this message]
2021-03-15 15:55 ` Florian Weimer
2021-03-15 22:14 ` Lukasz Majewski
2021-03-16 5:10 ` Florian Weimer
2021-03-16 9:06 ` Lukasz Majewski
2021-03-16 12:46 ` Adhemerval Zanella
2021-03-16 13:17 ` Adhemerval Zanella
2021-03-16 14:17 ` Lukasz Majewski
2021-03-16 14:25 ` Adhemerval Zanella
2021-03-16 14:28 ` Florian Weimer
2021-03-16 15:36 ` Lukasz Majewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210315154723.11687-1-lukma@denx.de \
--to=lukma@denx.de \
--cc=adhemerval.zanella@linaro.org \
--cc=arnd@arndb.de \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).