public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "klaus dot kusche at inode dot at" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/22344] New: Interix: "copying ..." when making libgcj takes too long
Date: Thu, 07 Jul 2005 10:15:00 -0000	[thread overview]
Message-ID: <20050707101529.22344.klaus.kusche@inode.at> (raw)

When making libgcj on Interix, the steps 
"copying selected object files to avoid basename conflicts..." followed by 
several "ln ... || cp ..." lines take *ages* compared to linux: Around 30 
minutes on an otherwise idle 3 GHz P4 machine.

The Task Manager shows a single "bash" consuming >97 % CPU in user mode all the 
time (we have bash instead of the microsoft sh as /bin/sh in our Interix).

Any chance to improve this?

-- 
           Summary: Interix: "copying ..." when making libgcj takes too long
           Product: gcc
           Version: 4.0.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: klaus dot kusche at inode dot at
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org
 GCC build triplet: i586-pc-interix3
  GCC host triplet: i586-pc-mingw32
GCC target triplet: i586-pc-mingw32


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


             reply	other threads:[~2005-07-07 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 10:15 klaus dot kusche at inode dot at [this message]
2005-07-07 13:01 ` [Bug libgcj/22344] " pinskia at gcc dot gnu dot org
2005-07-07 14:48 ` klaus dot kusche at inode dot at
2005-07-07 17:58 ` ro at techfak dot uni-bielefeld dot de

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=20050707101529.22344.klaus.kusche@inode.at \
    --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).