public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/20160] [4.0 Regression] link errors building libgcj tests
Date: Fri, 25 Feb 2005 19:50:00 -0000	[thread overview]
Message-ID: <20050225140724.15336.qmail@sourceware.org> (raw)
In-Reply-To: <20050223105204.20160.rearnsha@gcc.gnu.org>


------- Additional Comments From rearnsha at gcc dot gnu dot org  2005-02-25 14:07 -------
The build fails:

rm -fr .libs/libgcj.lax/libgcjgc_convenience.a
mkdir .libs/libgcj.lax/libgcjgc_convenience.a
(cd .libs/libgcj.lax/libgcjgc_convenience.a &&
/work/rearnsha/gnu/egcs/binutils/ar x
/work/rearnsha/gnu/egcs/arm-elf/thumb/libjava/../boehm-gc/.libs/libgcjgc_convenience.a)
copying selected object files to avoid basename conflicts...
rm -fr .libs/libgcj.lax
mkdir .libs/libgcj.lax
cp org/ietf/jgss/MessagesBundle.properties.o
.libs/libgcj.lax/lt1-MessagesBundle.properties.o
cp .libs/libgcj.lax/libgcj0_convenience.a/EventListener.o
.libs/libgcj.lax/lt2-EventListener.o
cp: cannot stat `.libs/libgcj.lax/libgcj0_convenience.a/EventListener.o': No
such file or directory
cp .libs/libgcj.lax/libgcj0_convenience.a/ContentHandler.o
.libs/libgcj.lax/lt3-ContentHandler.o
cp: cannot stat `.libs/libgcj.lax/libgcj0_convenience.a/ContentHandler.o': No
such file or directory
cp .libs/libgcj.lax/libgcj0_convenience.a/Attributes.o
.libs/libgcj.lax/lt4-Attributes.o
cp: cannot stat `.libs/libgcj.lax/libgcj0_convenience.a/Attributes.o': No such
file or directory

etc.

Incidentally, wouldn't it be more efficient to use links (either hard or soft)
rather than doing a copy?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|aoliva at gcc dot gnu dot   |rearnsha at gcc dot gnu dot
                   |org                         |org
             Status|WAITING                     |ASSIGNED
   Last reconfirmed|2005-02-24 22:01:51         |2005-02-25 14:07:21
               date|                            |


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


  parent reply	other threads:[~2005-02-25 14:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 14:05 [Bug libgcj/20160] New: " rearnsha at gcc dot gnu dot org
2005-02-23 14:06 ` [Bug libgcj/20160] " rmathew at gcc dot gnu dot org
2005-02-24 14:12 ` rearnsha at gcc dot gnu dot org
2005-02-24 14:12 ` rearnsha at gcc dot gnu dot org
2005-02-24 15:28 ` rearnsha at gcc dot gnu dot org
2005-02-24 22:55 ` rth at gcc dot gnu dot org
2005-02-25  8:05 ` rth at gcc dot gnu dot org
2005-02-25 14:07 ` aoliva at gcc dot gnu dot org
2005-02-25 16:55 ` aoliva at gcc dot gnu dot org
2005-02-25 19:49 ` aoliva at gcc dot gnu dot org
2005-02-25 19:50 ` rearnsha at gcc dot gnu dot org [this message]
2005-02-26  1:35 ` aoliva at gcc dot gnu dot org
2005-02-28 13:15 ` [Bug libgcj/20160] [4.0/4.1 " rearnsha at gcc dot gnu dot org
2005-03-02  0:11 ` aoliva at redhat dot com
2005-03-02  0:27 ` cvs-commit at gcc dot gnu dot org
2005-03-02  2:56 ` cvs-commit at gcc dot gnu dot org
2005-03-02  3:34 ` 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=20050225140724.15336.qmail@sourceware.org \
    --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).