public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Me Myself and I <stargate7thsymbol@live.co.uk>
To: <gcc-help@gcc.gnu.org>, <java@gcc.gnu.org>
Subject: RE: Almost successfull compiling GCJ, however..
Date: Mon, 05 Mar 2012 23:39:00 -0000	[thread overview]
Message-ID: <BAY147-W551177225724C370C4E1E3D0500@phx.gbl> (raw)
In-Reply-To: <4F54869B.20409@redhat.com>


obj/gmp/fib_table.h

is an empty file.

?

> Date: Mon, 5 Mar 2012 09:25:47 +0000
> From: aph@redhat.com
> To: gcc-help@gcc.gnu.org
> Subject: Re: Almost successfull compiling GCJ, however..
> 
> On 03/05/2012 05:10 AM, Me Myself and I wrote:
> > 
> > In response to the previous email to self, I have altered the prefix to be
> > 
> > --prefix=/home/User/
> > 
> > and encounter the precise same sort of error:
> > 
> > make;
> > 
> > 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
> > 
> > Why on earth doesn't this complete without these errors?  Can I afford to ignore them
> > and go on to make install; anyway?
> 
> It's hard for us to understand why you haven't looked to see
> what the problem is.  FIB_TABLE_LIMIT should be defined in
> obj/gmp/fib_table.h.
> 
> Andrew.
 		 	   		  

  parent reply	other threads:[~2012-03-05 23:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  0:28 Me Myself and I
2012-03-05  0:34 ` Per Bothner
2012-03-05  5:11   ` Me Myself and I
     [not found]     ` <4F54869B.20409@redhat.com>
2012-03-05 23:39       ` Me Myself and I [this message]
2012-03-06 14:58         ` Ian Lance Taylor
2012-03-07  0:28           ` Me Myself and I
2012-03-07  1:20             ` Jonathan Wakely
2012-03-07  1:56               ` Jonathan Wakely
2012-03-07  2:42           ` Me Myself and I
2012-03-07  9:23             ` Jonathan Wakely
2012-03-07 11:07               ` Me Myself and I
2012-03-07 18:49                 ` Jonathan Wakely
2012-03-07 23:51                   ` Me Myself and I
2012-03-08  0:04                     ` Jonathan Wakely
2012-03-08  1:27                       ` Me Myself and I
2012-03-08  6:47                         ` Ian Lance Taylor
2012-03-08  8:18                           ` Me Myself and I
2012-03-08 10:01                             ` Andrew Haley
     [not found]                             ` <CAM1kHc0_-ASxEmHs2rW8HYv7foo70kF4Ztr-J+Q3coD6THLsKA@mail.gmail.com>
2012-03-09  2:32                               ` Me Myself and I
2012-03-09 16:19                             ` Ian Lance Taylor

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=BAY147-W551177225724C370C4E1E3D0500@phx.gbl \
    --to=stargate7thsymbol@live.co.uk \
    --cc=gcc-help@gcc.gnu.org \
    --cc=java@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).