From: pjones <pjones@redhat.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: invalid storage class for some functions in grub_ls_list_files
Date: Wed, 27 Apr 2005 07:59:48 -0400 [thread overview]
Message-ID: <1114603188.7651.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1114551626.14788.14.camel@bauerbob.hirsch.lan>
On Tue, 2005-04-26 at 23:40 +0200, Thorsten Hirsch wrote:
> Hi,
>
> I couldn't find much in the archive about that one, so here's a
> compilation error of grub2 (gcc (GCC) 4.0.0 (Gentoo Linux 4.0.0)):
>
> gcc -Icommands -I./commands -I. -Iinclude -I./include -Wall -W
> -DGRUB_DATADIR=\"/opt/grub2/share/grub/i386-pc\" -g -O2 -DGRUB_UTIL=1
> -c -o grub_emu-commands_ls.o commands/ls.c
> commands/ls.c: In function 'grub_ls_list_files':
> commands/ls.c:107: error: invalid storage class for function
> 'print_files'
> commands/ls.c:115: error: invalid storage class for function
> 'print_files_long'
> commands/ls.c: In function 'grub_cmd_ls':
> commands/ls.c:223: error: invalid storage class for function
> 'grub_ls_print_files'
> make: *** [grub_emu-commands_ls.o] Error 1
This means you've got nested functions declared "static".
--
Peter
next prev parent reply other threads:[~2005-04-27 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 21:40 invalid storage class for some functions in grub_ls_list_files Thorsten Hirsch
2005-04-27 11:59 ` pjones [this message]
2005-04-27 12:59 ` Marco Gerards
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=1114603188.7651.0.camel@localhost.localdomain \
--to=pjones@redhat.com \
--cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.