Thanks for your help Mike.

After I emailed you (and the list) the 2nd time, I took another look at the
code and moved the structs above the declarations.  I compiled and voila!
Everything worked fine (for that part of my errors).

Now... it's a new ball of wax...

Changing and configuring things to the way I want them. ;)

Thanks again for your help.  It's appreciated.

Expect more posts to the list from me later... when I start to mess with the
code some more.

-Jesse

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of rom-
> [EMAIL PROTECTED]
> Sent: Sunday, February 12, 2006 9:26 AM
> To: [email protected]
> Subject: ROM digest, Vol 1 #1013 - 2 msgs
> 
> Send ROM mailing list submissions to
>       [email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://www.rom.org/cgi-bin/mailman/listinfo/rom
> or, via email, send a message with subject or body 'help' to
>       [EMAIL PROTECTED]
> 
> You can reach the person managing the list at
>       [EMAIL PROTECTED]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ROM digest..."
> 
> 
> Today's Topics:
> 
>    1. Fedora Core 4 still complains about incomplete elements
> ([EMAIL PROTECTED])
>    2. Re: Fedora Core 4 still complains about incomplete elements (Michael
> Barton)
> 
> --__--__--
> 
> Message: 1
> Date: Sat, 11 Feb 2006 18:04:20 -0500
> From: <[EMAIL PROTECTED]>
> To: [email protected]
> Cc: [EMAIL PROTECTED]
> Reply-To: [EMAIL PROTECTED]
> Subject: Fedora Core 4 still complains about incomplete elements
> 
> 
> Hi Mike (and others),
> 
> > Welcome to GCC 4!
> 
> Thanks!?
> GCC 4 is picky. :(
> 
> > It's not the array size that's the problem, it's the fact that it's
> > trying to use clan_type, flag_type, etc. before they're defined.
> 
> That much makes sense to me, but...
> 
> > You know all of those delcarations it complained about?  Yeah, those.=20
> 
> Do I ever! (There's, umm... LOTS of them)
> 
> > Move them down to the bottom of the file, after all the structure
> > definitions.  Then it'll compile.
> 
> The complaints are from a file called tables.h, which is an #include.
> I've tried to move the #include to the bottom of the file, but the same
> warnings appear.
> 
> Aside from moving the tables, do you have any other suggestions or am I
> too daft to even bother playing with this anymore?
> 
> > --Mike
> 
> -Jesse
> 
> PS.  If I move the #include to the very top of the files, will that change
> anything?  I don't have the code with me so I can't try it before I ask
> it.
> 
> 
> --__--__--
> 
> Message: 2
> Date: Sat, 11 Feb 2006 17:26:37 -0600
> From: Michael Barton <[EMAIL PROTECTED]>
> To: [email protected]
> Subject: Re: Fedora Core 4 still complains about incomplete elements
> 
> Sorry, I meant move the array declarations within tables.h.
> Like you have,
> 
>   extern  const   struct  clan_type       clan_table[MAX_CLAN];
>   extern  const   struct  position_type   position_table[];
> 
> etc...  Then below those is:
> 
>   struct flag_type
>   {
>       char *name;
>       int bit;
>       bool settable;
>   };
>   struct clan_type
>   {
>       char        *name;
>       char        *who_name;
>       sh_int      hall;
>       bool        independent; /* true for loners */
>   };
> 
> etc...
> 
> See, it's trying to create arrays of clan_type and flag_type and stuff
> before they've been defined.  GCC 4 decided to be picky about this.  I
> assume they started to comply with some part of the C specs that
> everyone else ignores.
> 
> So anyway, take all those extern array declarations in tables.h and
> move them to the bottom of the file, under the struct definitions.=20
> That's all I changed to get stock ROM to compile on my FC4 machine.
> 
> 
> On 2/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Hi Mike (and others),
> >
> > > Welcome to GCC 4!
> >
> > Thanks!?
> > GCC 4 is picky. :(
> >
> > > It's not the array size that's the problem, it's the fact that it's
> > > trying to use clan_type, flag_type, etc. before they're defined.
> >
> > That much makes sense to me, but...
> >
> > > You know all of those delcarations it complained about?  Yeah, those.=
> =3D20
> >
> > Do I ever! (There's, umm... LOTS of them)
> >
> > > Move them down to the bottom of the file, after all the structure
> > > definitions.  Then it'll compile.
> >
> > The complaints are from a file called tables.h, which is an #include.
> > I've tried to move the #include to the bottom of the file, but the same
> w=
> arnings appear.
> >
> > Aside from moving the tables, do you have any other suggestions or am I
> t=
> oo daft to even bother playing with this anymore?
> >
> > > --Mike
> >
> > -Jesse
> >
> > PS.  If I move the #include to the very top of the files, will that
> chang=
> e anything?  I don't have the code with me so I can't try it before I ask
> i=
> t.
> >
> >
> 
> 
> --__--__--
> 
> --
> ROM mailing list
> [email protected]
> http://www.rom.org/cgi-bin/mailman/listinfo/rom
> 
> End of ROM Digest

-- 
ROM mailing list
[email protected]
Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom

Reply via email to