public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/36640] Build gcc-4.2.1 release fails when configured with --with-xmlj using Sun's ld
Date: Sun, 29 Jun 2008 05:27:00 -0000	[thread overview]
Message-ID: <20080629052614.25382.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36640-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rob1weld at aol dot com  2008-06-29 05:26 -------
>> I don't understand the last comment.  Do you still have a bug to report?
Yes.

>>If no, then please close this, if yes, then please state what is different
>>from the successful build you used to obtain the test results.

The successful build is the result NOT configuring with "--with-xmlj" 


When I build I submit the test results to help the community. The test results
posted show that the numbers of FAILs is similar to other platforms, thus it is
a "successful" build (but without "--with-xmlj" which I would add if it did not
block the build).


The number of PASSes for the C compiler is very high and this version of GCC
(4.2.1) is one of the higher 4.2.x series that can be built. There are other
bug reports here by other people who were unable to build other 4.2.x versions
on OpenSolaris. I hope I have explained the significance of my post adequately.

Blows own horn. This is a milestone for the month old operating system.


I am not expert enough in Java to be the one who would fix this for us all.
Even if I was I would be opening this report to post the fix. 

Please do not close this bug unless it is either:
1. Fixed.
2. Decided it will not be fixed.


>>Anyway, if you have the relocation issue still, it'd be interesting to see
>>  cd i386-pc-solaris2.11/libjava
>>  ./libtool --tag=CXX --config
>>  ./libtool --tag=GCJ --config
>>to exclude a bogus pic_flag setting.

Here they are (from a successful build, no "--with-xmlj"):


-- 


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


  parent reply	other threads:[~2008-06-29  5:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 15:34 [Bug libgcj/36640] New: " rob1weld at aol dot com
2008-06-26 17:53 ` [Bug libgcj/36640] " rob1weld at aol dot com
2008-06-27  8:43 ` rob1weld at aol dot com
2008-06-27  8:47 ` rwild at gcc dot gnu dot org
2008-06-29  5:27 ` rob1weld at aol dot com [this message]
2008-06-29  5:40 ` rob1weld at aol dot com
2008-06-29  5:42 ` rob1weld at aol dot com
2008-08-11  1:25 ` pinskia at gcc dot gnu dot org
2009-01-27 23:33 ` rob1weld at aol dot com

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=20080629052614.25382.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).