[Bug java/28149] New: Fail to test GCC on simulation due to libjava build errors.

[Bug java/28149] New: Fail to test GCC on simulation due to libjava build errors.

[jserv at kaffe dot org]

While testing GCC on a simulator[1], there are some build errors causing the
process failed. The files are involving in:
(1) libjava/java/util/natVMTimeZone.cc
(2) libjava/classpath/native/fdlibm/mprec.c

Attachment attempts to fix the issue and drive testing GCC on simulation
continue.

[1] Reference: http://gcc.gnu.org/simtest-howto.html


-- 
           Summary: Fail to test GCC on simulation due to libjava build
                    errors.
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jserv at kaffe dot org
 GCC build triplet: i486-linux-gnu
  GCC host triplet: i486-linux-gnu
GCC target triplet: arm-elf


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

[Bug java/28149] Fail to test GCC on simulation due to libjava build errors.

[jserv at kaffe dot org]

------- Comment #1 from jserv at kaffe dot org  2006-06-24 07:52 -------
Created an attachment (id=11739)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11739&action=view)
Fix build errors in libjava when target = arm-elf simulation


-- 


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

[Bug java/28149] Fail to test GCC on simulation due to libjava build errors.

[tromey at gcc dot gnu dot org]

------- Comment #2 from tromey at gcc dot gnu dot org  2006-06-27 15:30 -------
The mprec part of this patch looks fine to me.
This should go in Classpath as well as libgcj.

The timezone part of this patch looks odd.
I would expect that we would need another case in there
for "__timezone" -- both a configure check and another
#if.


-- 

tromey at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-06-27 15:30:56
               date|                            |


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

[Bug java/28149] Fail to test GCC on simulation due to libjava build errors.

[jserv at kaffe dot org]

------- Comment #3 from jserv at kaffe dot org  2006-06-29 06:43 -------
(In reply to comment #2)
> The timezone part of this patch looks odd.
> I would expect that we would need another case in there
> for "__timezone" -- both a configure check and another
> #if.

I compared automake detecting report between gcc/gcj and GNU Classpath, and I
found that macro definition HAVE_UNDERSCORE_TIMEZONE was set to different
values. For the former, that is 1, and becomes unset for the later. GNU
Classpath bootstrapped with Automake 1.9.6 works for me, and configure script
outputs the right results.

Still, I don't find other clues.


-- 


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

[Bug java/28149] Fail to test GCC on simulation due to libjava build errors.

[manu at gcc dot gnu dot org]

------- Comment #4 from manu at gcc dot gnu dot org  2007-02-14 15:37 -------
(In reply to comment #3)
> (In reply to comment #2)
> > The timezone part of this patch looks odd.
> > I would expect that we would need another case in there
> > for "__timezone" -- both a configure check and another
> > #if.
> 
> I compared automake detecting report between gcc/gcj and GNU Classpath, and I
> found that macro definition HAVE_UNDERSCORE_TIMEZONE was set to different
> values. For the former, that is 1, and becomes unset for the later. GNU
> Classpath bootstrapped with Automake 1.9.6 works for me, and configure script
> outputs the right results.
> 

Maybe you should ask about that in the gcc@gcc.gnu.org and java@gcc.gnu.org
mailing lists, so your question will reach a wider audience.

I had to disable java to bootstrapped+test using a simulator. :(



-- 


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