From: Andreas Jaeger <aj@suse.com>
To: libc-ports@sourceware.org
Subject: Fix arm warning
Date: Mon, 16 Apr 2012 10:17:00 -0000 [thread overview]
Message-ID: <201204161217.41536.aj@suse.com> (raw)
Building for ARM I got lots of these warnings:
../glibc-ports-2.15/sysdeps/unix/sysv/linux/arm/ldsodefs.h:41:0: warning:
"MORE_ELF_HEADER_DATA" redefined [enabled by default]
../sysdeps/unix/sysv/linux/ldsodefs.h:64:0: note: this is the location of
the previous definition
This is still in git head. Let's undef it like we undef the other
variables.
Ok to commit?
Andreas
2012-04-16 Andreas Jaeger <aj@suse.de>
* sysdeps/unix/sysv/linux/arm/ldsodefs.h: Undefine
MORE_ELF_HEADER_DATA to avoid warnings about redefinition.
diff --git a/sysdeps/unix/sysv/linux/arm/ldsodefs.h
b/sysdeps/unix/sysv/linux/arm/ldsodefs.h
index 839dc18..6966f8a 100644
--- a/sysdeps/unix/sysv/linux/arm/ldsodefs.h
+++ b/sysdeps/unix/sysv/linux/arm/ldsodefs.h
@@ -1,5 +1,5 @@
/* Run-time dynamic linker data structures for loaded ELF shared objects.
- Copyright (C) 2010 Free Software Foundation, Inc.
+ Copyright (C) 2010, 2012 Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
@@ -23,6 +23,7 @@
#undef VALID_ELF_HEADER
#undef VALID_ELF_OSABI
+#undef MORE_ELF_HEADER_DATA
#ifdef __ARM_EABI__
#define EXTRA_OSABI ELFOSABI_ARM_AEABI
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
next reply other threads:[~2012-04-16 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 10:17 Andreas Jaeger [this message]
2012-04-16 23:25 ` Carlos O'Donell
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=201204161217.41536.aj@suse.com \
--to=aj@suse.com \
--cc=libc-ports@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).