From: Eli Zaretskii <eliz@gnu.org>
To: Ian Lance Taylor <iant@google.com>
Cc: joseph@codesourcery.com, gcc-patches@gcc.gnu.org,
gdb-patches@sources.redhat.com
Subject: Re: needed-list fails in libiberty
Date: Thu, 16 Apr 2009 17:47:00 -0000 [thread overview]
Message-ID: <8363h4lcc3.fsf@gnu.org> (raw)
In-Reply-To: <m33acayqkj.fsf@google.com>
> Cc: joseph@codesourcery.com, gcc-patches@gcc.gnu.org,
> gdb-patches@sources.redhat.com
> From: Ian Lance Taylor <iant@google.com>
> Date: Wed, 15 Apr 2009 06:49:48 -0700
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > 2009-04-14 Eli Zaretskii <eliz@gnu.org>
> >> >
> >> > * Makefile.in (needed-list): Target removed (not used in GCC
> >> > 3.0 and later). All references deleted.
> >>
> >> This is OK if you've done a clean bootstrap on a primary platform.
I bootstrapped yesterday's SVN on this platform:
Linux fencepost 2.6.16.29-xen #1 SMP Wed Dec 6 07:32:36 EST 2006 x86_64 GNU/Linux
> For a patch like this only the libiberty testsuite need be run.
After a successful bootstrap, I typed "make -C libiberty check", and
the test ran to completion without any errors.
Here's again the patch I suggest (this time including the removal of 2
obsolete Awk scripts). As I don't have write access, could someone
please commit it?
Thanks.
2009-04-16 Eli Zaretskii <eliz@gnu.org>
* Makefile.in (needed-list): Target removed (not used in GCC
3.0 and later). All references deleted.
(mostlyclean): Remove references to needed.awk and needed2.awk.
--- libiberty/Makefile.in~ 2009-04-15 14:07:06.825412329 -0400
+++ libiberty/Makefile.in 2009-04-15 15:15:03.574853288 -0400
@@ -100,7 +100,7 @@
SUBDIRS = testsuite
# FIXME: add @BUILD_INFO@ once we're sure it works for everyone.
-all: stamp-picdir $(TARGETLIB) needed-list required-list all-subdir
+all: stamp-picdir $(TARGETLIB) required-list all-subdir
@: $(MAKE) ; exec $(MULTIDO) $(FLAGS_TO_PASS) multi-do DO=all
.PHONY: check installcheck
@@ -377,22 +377,6 @@
mv -f $(DESTDIR)$(tooldir)/lib/$(MULTIOSDIR)/$(TARGETLIB)n $(DESTDIR)$(tooldir)/lib/$(MULTIOSDIR)/$(TARGETLIB)
@$(MULTIDO) $(FLAGS_TO_PASS) multi-do DO=install
-# needed-list is used by libstdc++. NEEDED is the list of functions
-# to include there. Do not add anything LGPL to this list; libstdc++
-# can't use anything encumbering.
-NEEDED = atexit calloc memchr memcmp memcpy memmove memset rename strchr \
- strerror strncmp strrchr strstr strtol strtoul tmpnam vfprintf vprintf \
- vfork waitpid bcmp bcopy bzero
-needed-list: Makefile
- rm -f needed-list; touch needed-list; \
- for f in $(NEEDED); do \
- for g in $(LIBOBJS) $(EXTRA_OFILES); do \
- case "$$g" in \
- *$$f*) echo $$g >> needed-list ;; \
- esac; \
- done; \
- done
-
# required-list was used when building a shared bfd/opcodes/libiberty
# library. I don't know if it used by anything currently.
required-list: Makefile
@@ -440,8 +424,8 @@
# multiple times, hence our explicit recursion with an empty SUBDIRS.
mostlyclean: mostlyclean-subdir
-rm -rf *.o pic core errs \#* *.E a.out
- -rm -f needed.awk needed2.awk errors dummy needed-list config.h stamp-*
- -rm -f $(CONFIG_H) $(NEEDED_LIST) stamp-picdir
+ -rm -f errors dummy config.h stamp-*
+ -rm -f $(CONFIG_H) stamp-picdir
-rm -f libiberty.aux libiberty.cp libiberty.cps libiberty.fn libiberty.ky
-rm -f libiberty.log libiberty.tmp libiberty.tps libiberty.pg
-rm -f libiberty.pgs libiberty.toc libiberty.tp libiberty.tpl libiberty.vr
next prev parent reply other threads:[~2009-04-16 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 14:10 Eli Zaretskii
2009-04-14 14:19 ` Joseph S. Myers
2009-04-14 14:42 ` Eli Zaretskii
2009-04-15 0:30 ` Ian Lance Taylor
2009-04-15 8:15 ` Eli Zaretskii
2009-04-15 13:50 ` Ian Lance Taylor
2009-04-16 17:47 ` Eli Zaretskii [this message]
2009-04-25 9:58 ` Eli Zaretskii
2009-04-25 22:41 ` Ian Lance Taylor
2009-04-26 17:44 ` Eli Zaretskii
2009-04-26 2:23 ` DJ Delorie
2009-04-26 17:44 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-04-14 14:10 Eli Zaretskii
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=8363h4lcc3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=iant@google.com \
--cc=joseph@codesourcery.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