public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Incomplete dependencies for libio/old*.c
Date: Sun, 27 Apr 2003 16:11:00 -0000	[thread overview]
Message-ID: <m3k7dg9kwn.fsf@whitebox.local> (raw)

Dependencies are generated using the non-pic command line (ie. without
-DSHARED).  This is a problem with some of the compatibility sources
which check SHLIB_COMPAT before including the headers, so that the
generated dependency list is incomplete.

Andreas.

2003-04-27  Andreas Schwab  <schwab@suse.de>

	* Makeconfig (+mkdep): Add -DMAKING_DEPENDENCIES.
	* include/shlib-compat.h (SHLIB_COMPAT) [MAKING_DEPENDENCIES]:
	Define to 1.

--- Makeconfig.~1.282.~	2003-04-16 23:05:35.000000000 +0200
+++ Makeconfig	2003-04-27 14:21:24.000000000 +0200
@@ -557,7 +557,7 @@ endif
 # The -MP flag tells GCC >= 3.2 (which we now require) to produce dummy
 # targets for headers so that removed headers don't break the build.
 ifndef +mkdep
-+mkdep = $(CC) -M -MP
++mkdep = $(CC) -DMAKING_DEPENDENCIES -M -MP
 endif
 
 # The program that makes Emacs-style TAGS files.
--- include/shlib-compat.h.~1.10.~	2002-10-14 11:06:09.000000000 +0200
+++ include/shlib-compat.h	2003-04-27 14:23:50.000000000 +0200
@@ -26,7 +26,12 @@
 #include <abi-versions.h>	/* header generated by abi-versions.awk */
 #endif
 
-#if defined HAVE_ELF && defined SHARED && defined DO_VERSIONING
+#ifdef MAKING_DEPENDENCIES
+
+/* While computing dependencies we want to see all headers.  */
+# define SHLIB_COMPAT(lib, introduced, obsoleted)	1
+
+#elif defined HAVE_ELF && defined SHARED && defined DO_VERSIONING
 
 /* The file abi-versions.h (generated by scripts/abi-versions.awk) defines
    symbols like `ABI_libm_GLIBC_2_0' for each version set in the source

             reply	other threads:[~2003-04-27 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27 16:11 Andreas Schwab [this message]
2003-04-27 18:35 ` Roland McGrath

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=m3k7dg9kwn.fsf@whitebox.local \
    --to=schwab@suse.de \
    --cc=libc-hacker@sources.redhat.com \
    /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).