public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
* Final errors in GCJ build, and I have success.
@ 2012-02-29 11:12 Me Myself and I
  2012-02-29 11:35 ` Jonathan Wakely
  0 siblings, 1 reply; 2+ messages in thread
From: Me Myself and I @ 2012-02-29 11:12 UTC (permalink / raw)
  To: gcc-help, java



I type

make install;

and the process seems to finish all my files, but ends with this:

fib2_ui.c:76:29: error: 'FIB_TABLE_LIMIT' undeclared (first use in this function)
fib2_ui.c:76:29: note: each undeclared identifier is reported only once for each function it appears in
make[5] *** [fib2_ui.lo] Error 1
make[5] Leaving directory '/home/User/gcc-4.6.2/objdir/gmp/mpn'
make[4] ***all-recursive] Error 1
make[4] Leaving directory '/home/User/gcc-4.6.2/objdir/gmp'
make[3] *** [all] Error 2
make[3] Leaving directory '/home/User/gcc-4.6.2/objdir/gmp'
make[2] *** [all-stage1-gmp] Error 2
make[2] Leaving directory '/home/User/gcc-4.6.2/objdir'
make[1] *** [stage1-bubble] Error 2
make[1] Leaving directory '/home/User/gcc-4.6.2/objdir'
make: *** [all] Error 2


It leaves the following log-ish files behind:

config.log
config.status
stage_current
stage_final
stage_last

Does this mean that my build is entirely finished and ready?
It looks like it is checking itself by calling a recursive fibonacci function, and fails.
How may I fix this?

Do I need to reply with any of the mentioned log files for more information?
 		 	   		  

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Final errors in GCJ build, and I have success.
  2012-02-29 11:12 Final errors in GCJ build, and I have success Me Myself and I
@ 2012-02-29 11:35 ` Jonathan Wakely
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Wakely @ 2012-02-29 11:35 UTC (permalink / raw)
  To: Me Myself and I; +Cc: gcc-help, java

On 29 February 2012 11:12, Me Myself and I wrote:
>
>
> I type
>
> make install;
>
> and the process seems to finish all my files, but ends with this:
>
> fib2_ui.c:76:29: error: 'FIB_TABLE_LIMIT' undeclared (first use in this function)
> fib2_ui.c:76:29: note: each undeclared identifier is reported only once for each function it appears in
> make[5] *** [fib2_ui.lo] Error 1
> make[5] Leaving directory '/home/User/gcc-4.6.2/objdir/gmp/mpn'
> make[4] ***all-recursive] Error 1
> make[4] Leaving directory '/home/User/gcc-4.6.2/objdir/gmp'
> make[3] *** [all] Error 2
> make[3] Leaving directory '/home/User/gcc-4.6.2/objdir/gmp'
> make[2] *** [all-stage1-gmp] Error 2
> make[2] Leaving directory '/home/User/gcc-4.6.2/objdir'
> make[1] *** [stage1-bubble] Error 2
> make[1] Leaving directory '/home/User/gcc-4.6.2/objdir'
> make: *** [all] Error 2
>
>
> It leaves the following log-ish files behind:
>
> config.log
> config.status
> stage_current
> stage_final
> stage_last
>
> Does this mean that my build is entirely finished and ready?

No, it exited with an error.

Is /home/User/gcc-4.6.2 where you have the gcc sources?

If so, then your objdir is inside the source dir.  The docs clearly
say not to do that:

http://gcc.gnu.org/wiki/InstallingGCC
"you need to run configure from outside the source directory"

http://gcc.gnu.org/install/configure.html
"building where objdir is a subdirectory of srcdir is unsupported"

I suggest you delete the entire gcc-4.6.2 directory, as you've now
fudged it by building in it, unpack the sources again, then read the
damn docs, then read them again, then create a new objdir
***outside*** the source directory (not inside it, outside, got it?)
and run configure and make again.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-02-29 11:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-29 11:12 Final errors in GCJ build, and I have success Me Myself and I
2012-02-29 11:35 ` Jonathan Wakely

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