public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at eyesopen dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/33781] [4.3/4.4 Regression] "Arg list too long" building libgcc.a
Date: Thu, 12 Jun 2008 21:31:00 -0000	[thread overview]
Message-ID: <20080612213102.24651.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33781-754@http.gcc.gnu.org/bugzilla/>



------- Comment #20 from roger at eyesopen dot com  2008-06-12 21:31 -------
Hi Ralf,

Thanks for your patch.

Sorry for the delay in replying, I needed to check out mainline on my IRIX
box and rebuild a baseline, and once that had completed "make -k check",
I tried with "--enable-fixed-point" first without, and then with your
patch.  The good news is that this allows the libgcc build to get further,
but unfortunately the bad news is that we die just a little further on with
a similar "execvp: /bin/sh: Arg list too long".

This second failure is where we run nm on all of the objects and pipe the
results through mkmap-flat.awk to create tmp-libgcc.map.  This looks to be
in the same libgcc/Makefile.in in the libgcc.map rule (when SHLIB_MKMAP is
defined).

I do like your PR33781.diff patch which moves us in the right direction.
Is it possible/safe to apply similar voodoo to the libgcc.map rule?

Many thanks again for your help.  I've no personal interest in using fixed
point arithmetic on the MIPS, but resolving this issue on IRIX helps keep
the build machinery portable.  If it's not IRIX now, it'll be some other
platform with a low MAXARGS limit in the near future.

Roger
--


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33781


  parent reply	other threads:[~2008-06-12 21:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 15:37 [Bug bootstrap/33781] New: [4.3 " roger at eyesopen dot com
2007-10-22  8:43 ` [Bug bootstrap/33781] " pinskia at gcc dot gnu dot org
2007-10-30 14:01 ` jakub at gcc dot gnu dot org
2007-10-30 14:03 ` jakub at gcc dot gnu dot org
2007-11-01 16:03 ` dj at redhat dot com
2007-11-01 17:15 ` roger at eyesopen dot com
2007-11-01 20:03 ` dj at redhat dot com
2007-11-01 22:26 ` jakub at gcc dot gnu dot org
2007-11-01 22:35 ` jakub at gcc dot gnu dot org
2007-11-02 16:42 ` roger at eyesopen dot com
2007-11-02 17:12 ` roger at eyesopen dot com
2007-11-02 17:41 ` dj at redhat dot com
2007-11-02 18:41 ` jakub at gcc dot gnu dot org
2007-11-02 18:56 ` dj at redhat dot com
2007-11-02 18:58 ` dj at redhat dot com
2007-11-05  3:15 ` mmitchel at gcc dot gnu dot org
2008-01-31 10:45 ` fxcoudert at gcc dot gnu dot org
2008-02-01 17:43 ` sayle at gcc dot gnu dot org
2008-03-15  0:44 ` [Bug bootstrap/33781] [4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-06-06 15:01 ` rguenth at gcc dot gnu dot org
2008-06-09  8:34 ` Ralf dot Wildenhues at gmx dot de
2008-06-09 18:42 ` Ralf dot Wildenhues at gmx dot de
2008-06-12 21:31 ` roger at eyesopen dot com [this message]
2008-06-12 21:46 ` Ralf dot Wildenhues at gmx dot de
2008-06-14  7:26 ` rwild at gcc dot gnu dot org
2008-08-27 22:05 ` jsm28 at gcc dot gnu dot org
2009-01-24 10:22 ` rguenth at gcc dot gnu dot org
2009-04-07 20:40 ` [Bug bootstrap/33781] [4.3/4.4/4.5 " PHHargrove at lbl dot gov
2009-04-07 20:46 ` rwild at gcc dot gnu dot org
2009-04-07 23:39 ` PHHargrove at lbl dot gov
2009-08-04 12:37 ` rguenth at gcc dot gnu dot org
2010-05-22 18:20 ` [Bug bootstrap/33781] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot 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=20080612213102.24651.qmail@sourceware.org \
    --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).