public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "th.r.klein at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/47836] Some Cross Compiler can't build target-libiberty or target-zlib
Date: Fri, 24 Jun 2011 11:11:00 -0000 [thread overview]
Message-ID: <bug-47836-4-kpbEYKxej2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47836-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47836
--- Comment #15 from th.r.klein at web dot de 2011-06-24 11:10:27 UTC ---
The commit helps suppress building of target-libiberty.
But there is still a try to build target-zlib.
Isn't it possible to add a manual switch to prevent building of such target
libraries by adding them to
'noconfigdirs' with eg. --disable-target-zlib?
For a possible implementation see
(http://gcc.gnu.org/ml/gcc-patches/2011-03/msg00374.html)
or below.
Index: configure.ac
===================================================================
--- configure.ac (revision 175346)
+++ configure.ac (working copy)
@@ -1880,6 +1880,28 @@ case ,${enable_languages},:${enable_objc_gc} in
;;
esac
+# a user defined "--disable-target-.." was given
+# add this to the ingnore list if not already present
+for target_lib_var in $target_libraries
+do
+ var=`$as_echo "$target_lib_var" | sed 's/[[-+.]]/_/g'`
+ eval is_enabled=\$enable_$var
+ if test x$is_enabled = xno ; then
+ append_var=yes
+ for var in $noconfigdirs $skipdirs
+ do
+ if test x$var = x$target_lib_var ; then
+ append_var=no
+ break
+ fi
+ done
+ if test x$append_var = xyes ; then
+ noconfigdirs="$noconfigdirs $target_lib_var"
+ echo "add $target_lib_var to noconfigdirs"
+ fi
+ fi
+done
+
# Remove the entries in $skipdirs and $noconfigdirs from $configdirs,
# $build_configdirs and $target_configdirs.
# If we have the source for $noconfigdirs entries, add them to $notsupp.
next prev parent reply other threads:[~2011-06-24 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:03 [Bug regression/47836] New: " th.r.klein at web dot de
2011-02-21 19:22 ` [Bug regression/47836] " pinskia at gcc dot gnu.org
2011-02-22 19:53 ` th.r.klein at web dot de
2011-02-22 22:57 ` pinskia at gcc dot gnu.org
2011-02-23 18:10 ` th.r.klein at web dot de
2011-02-23 20:45 ` pinskia at gcc dot gnu.org
2011-02-24 20:15 ` th.r.klein at web dot de
2011-02-26 15:36 ` rwild at gcc dot gnu.org
2011-02-27 9:34 ` th.r.klein at web dot de
2011-02-27 22:48 ` pinskia at gcc dot gnu.org
2011-02-28 20:25 ` th.r.klein at web dot de
2011-03-02 5:57 ` rwild at gcc dot gnu.org
2011-03-02 16:50 ` joseph at codesourcery dot com
2011-06-22 20:18 ` hp at gcc dot gnu.org
2011-06-22 21:33 ` hp at gcc dot gnu.org
2011-06-24 11:11 ` th.r.klein at web dot de [this message]
2011-06-27 20:58 ` hp at gcc dot gnu.org
2011-06-27 21:04 ` hp at gcc dot gnu.org
2011-10-07 4:26 ` fzvqedi at v dot mintemail.com
2012-02-02 8:18 ` pinskia at gcc dot gnu.org
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=bug-47836-4-kpbEYKxej2@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).