From: Andreas Schwab <schwab@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Fix install-headers to install <bits/stdio_lim.h>
Date: Sun, 26 Sep 2004 21:03:00 -0000 [thread overview]
Message-ID: <je7jqgagjw.fsf@sykes.suse.de> (raw)
Running make install-headers should also install <bits/stdio_lim.h>, this
is needed when bootstrapping the toolchain.
Andreas.
2004-09-26 Andreas Schwab <schwab@suse.de>
* stdio-common/Makefile (headers): Add bits/stdio_lim.h.
(install-others): Don't define.
($(inst_includedir)/bits/stdio_lim.h): Remove rule.
Index: stdio-common/Makefile
===================================================================
RCS file: /cvs/glibc/libc/stdio-common/Makefile,v
retrieving revision 1.90
diff -u -p -a -u -p -a -r1.90 stdio-common/Makefile
--- stdio-common/Makefile 10 Aug 2004 18:01:29 -0000 1.90
+++ stdio-common/Makefile 26 Sep 2004 19:54:08 -0000
@@ -21,7 +21,7 @@
#
subdir := stdio-common
-headers := printf.h stdio_ext.h
+headers := printf.h stdio_ext.h bits/stdio_lim.h
routines := \
ctermid cuserid \
@@ -36,8 +36,6 @@ routines := \
remove rename \
flockfile ftrylockfile funlockfile
-install-others = $(inst_includedir)/bits/stdio_lim.h
-
include ../Makeconfig
aux := errlist siglist printf-parsemb printf-parsewc
@@ -59,9 +57,6 @@ test-srcs = tst-unbputc tst-printf
include ../Rules
-$(inst_includedir)/bits/stdio_lim.h: $(common-objpfx)bits/stdio_lim.h $(+force)
- $(do-install)
-
ifeq ($(cross-compiling),no)
.PHONY: do-tst-unbputc do-tst-printf
tests: do-tst-unbputc do-tst-printf
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2004-09-26 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 21:03 Andreas Schwab [this message]
2004-09-26 21:30 ` Roland McGrath
2004-09-26 21:37 ` Andreas Schwab
2004-09-26 21:59 ` Roland McGrath
2004-09-26 21:31 ` 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=je7jqgagjw.fsf@sykes.suse.de \
--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).