Re: Cross compile, no grmic/grmiregistry

2005-11-10 Thread TJ Laurenzo
> Call me silly, I don't really know how and where to file a PR. Is there > any guideline? I just realized that I referred you to a PR and you had asked what that meant. It is a record in the GCC Bugzilla database: http://gcc.gnu.org/bugzilla/ TJ

Re: Cross compile, no grmic/grmiregistry

2005-11-10 Thread TJ Laurenzo
Rui, I just checked in the patch to correct this problem. See PR 20993. This has also been backported to the 4.0 branch, so if you update on either mainline or the 4.0 branch, you should get the fix. Note that the fix is to gcjh, so you are best rebuilding from scratch. TJ On 11/10/05, Rui Wan

Re: Cross compile, no grmic/grmiregistry

2005-11-09 Thread TJ Laurenzo
> Are you talking of a cross-compiler (target != host) or > a crossed-native compiler (target==host!=build)? I think > Rui was complaining about these tools not being generated > in the cross-compiler case while you might have observed > these being created in the crossed-native compiler case. > >

Re: Cross compile, no grmic/grmiregistry

2005-11-09 Thread TJ Laurenzo
> - - 8< - > ## For now, only on native systems. FIXME. > if NATIVE > bin_PROGRAMS = jv-convert gij grmic grmiregistry gcj-dbtool > endif > - - 8< - > > So this is expected behaviour at

Re: Segmentation Fault building GCC for i686-pc-mingw32

2005-09-21 Thread TJ Laurenzo
Correlating the stacktrace with CVS revealed that this was fixed a few hours after I updated. The bug was 23929. Ranjit, thanks for the help getting the debugger going. TJ

Segmentation Fault building GCC for i686-pc-mingw32

2005-09-20 Thread TJ Laurenzo
I'm getting a segmentation fault in the GCC build from today's CVS HEAD. I am building the suite for mingw using a cross compiler from Linux. This setup was working fine prior to updating to the latest CVS head today. My old sources, which were working correctly, were from 9/1/2005. In both cas