public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "conveycj at npt dot nuwc dot navy dot mil" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/21217] New: "Argument list too long" when guilding gcj
Date: Mon, 25 Apr 2005 14:37:00 -0000	[thread overview]
Message-ID: <20050425143544.21217.conveycj@npt.nuwc.navy.mil> (raw)

I'm using Debian Sid on a Pentium IV.

I downloaded the released version of 4.0.0  (gcc-4.0.0.tar.gz).

I unzipped it into:  /home/cjc/packages/gcc-4.0.0
I created a directory to build into: /home/cjc/packages/o

In the /home/cjc/packages/o directory, I ran this command:
/home/cjc/packages/gcc-4.0.0/configure --prefix=/opt/gcc-4.0.0 --enable-threads
--enable-languages=c,c++,java 

I then ran "make". Well into the building of GCJ, I noticed this error:

ln org/ietf/jgss/MessagesBundle.properties.o
.libs/libgcj.lax/lt1-MessagesBundle.properties.o || cp
org/ietf/jgss/MessagesBundle.properties.o
.libs/libgcj.lax/lt1-MessagesBundle.properties.o
./libtool: line 4696: /usr/bin/expr: Argument list too long


The subsequent "make install" seemed to execute without any problem.

-- 
           Summary: "Argument list too long" when guilding gcj
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: conveycj at npt dot nuwc dot navy dot mil
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


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


             reply	other threads:[~2005-04-25 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 14:37 conveycj at npt dot nuwc dot navy dot mil [this message]
2005-04-25 14:44 ` [Bug libgcj/21217] " pinskia at gcc dot gnu dot org
2005-04-25 14:45 ` pinskia 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=20050425143544.21217.conveycj@npt.nuwc.navy.mil \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).