This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug librt/23273] glibc 2.27 doesn't build on arm: .../librtld.os: In function `process_dl_debug': raise.c:(.text+0x4f0): undefined reference to `memcpy'
- From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 13 Jun 2018 18:57:38 +0000
- Subject: [Bug librt/23273] glibc 2.27 doesn't build on arm: .../librtld.os: In function `process_dl_debug': raise.c:(.text+0x4f0): undefined reference to `memcpy'
- Auto-submitted: auto-generated
- References: <bug-23273-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23273
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Sergei Trofimovich <slyfox at inbox dot ru> ---
Echoing https://sourceware.org/ml/libc-alpha/2018-06/msg00224.html here:
"""
CFLAGS/CPPFLAGS should work for us.
I was about to ask why glibc is special in handling CFLAGS. But I guess it's
not
special and is mimicked after default rules of GNU make. Which is:
.o: .S
$(AS) $(CPPFLAGS) $(ASFLAGS) ...
.o: .s
$(AS) $(ASFLAGS) ...
Thus passing ABI flags as part of ASFLAGS might be more generic (for projects
that use .s and .S). But for glibc CPPFLAGS are used in the same context as
[ASFLAGS].
"""
Bug can be closed as INVALID.
Thanks!
--- Comment #8 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
As per comment #7.
--
You are receiving this mail because:
You are on the CC list for the bug.