From: Roberto Gaggiotti <rgaggiotti@videoblaster.it>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.4.9 on alphaev56
Date: Thu, 30 Aug 2001 17:48:37 +0200 [thread overview]
Message-ID: <3B8E6055.42EF59FB@videoblaster.it> (raw)
[-- Attachment #1: Type: text/plain, Size: 2774 bytes --]
gcc -D__KERNEL__ -I/usr/src/linux-2.4.9/include -Wall
-Wstrict-prototypes -Wno-t
rigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe
-mno-fp
-regs -ffixed-8 -mcpu=ev56 -Wa,-mev6 -c -o pc_keyb.o pc_keyb.c
In file included from pc_keyb.c:36:
/usr/src/linux-2.4.9/include/asm/keyboard.h:25: warning: `struct
kbd_repeat' dec
lared inside parameter list
/usr/src/linux-2.4.9/include/asm/keyboard.h:25: warning: its scope is
only thisdefinition or declaration, which is probably not what you want.
pc_keyb.c:545: variable `kbdrate' has initializer but incomplete type
pc_keyb.c:546: warning: excess elements in struct initializer
pc_keyb.c:546: warning: (near initialization for `kbdrate')
pc_keyb.c:548: warning: excess elements in struct initializer
pc_keyb.c:548: warning: (near initialization for `kbdrate')
pc_keyb.c: In function `parse_kbd_rate':
pc_keyb.c:574: dereferencing pointer to incomplete type
pc_keyb.c:575: dereferencing pointer to incomplete type
pc_keyb.c:575: invalid use of undefined type `struct kbd_repeat'
pc_keyb.c:576: dereferencing pointer to incomplete type
pc_keyb.c:577: dereferencing pointer to incomplete type
pc_keyb.c:590: dereferencing pointer to incomplete type
pc_keyb.c:591: dereferencing pointer to incomplete type
pc_keyb.c: At top level:
pc_keyb.c:606: conflicting types for `pckbd_rate'
/usr/src/linux-2.4.9/include/asm/keyboard.h:25: previous declaration of
`pckbd_rate'
pc_keyb.c: In function `pckbd_rate':
pc_keyb.c:611: storage size of `old_rep' isn't known
pc_keyb.c:612: sizeof applied to an incomplete type
pc_keyb.c:614: sizeof applied to an incomplete type
pc_keyb.c:615: sizeof applied to an incomplete type
pc_keyb.c:611: warning: unused variable `old_rep'
pc_keyb.c: At top level:
pc_keyb.c:545: storage size of `kbdrate' isn't known
make[3]: *** [pc_keyb.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.9/drivers/char'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.9/drivers/char'
make[1]: *** [_subdir_char] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.9/drivers'
make: *** [_dir_drivers] Error
2
-----------------
Linux admin.private.net 2.4.6 #3 gio lug 12 20:38:25 CEST 2001 alpha
unknown
Gnu C 3.0.1
Gnu make 3.79
binutils 2.11.2
util-linux 2.10h
mount 2.10h
modutils 2.4.6
e2fsprogs 1.20-WIP
isdn4k-utils 3.1beta7
Linux C Library 2.1.3
Dynamic linker (ldd) 2.1.3
Linux C++ Library 3.0.1
Procps 2.0.6
Net-tools 1.55
Console-tools 0.2.3
Sh-utils 2.0
cat: /proc/modules: File o directory inesistente
Modules
Loaded
[-- Attachment #2: Card for Roberto Gaggiotti --]
[-- Type: text/x-vcard, Size: 249 bytes --]
begin:vcard
n:Gaggiotti;Roberto
x-mozilla-html:FALSE
url:www.videoblaster.it
org:Videoblaster S.r.l.
adr:;;Via Montebello, 71;Ancona;Italy;60127;
version:2.1
email;internet:rgaggiotti@videoblaster.it
x-mozilla-cpt:;0
fn:Roberto Gaggiotti
end:vcard
next reply other threads:[~2001-08-30 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 15:48 Roberto Gaggiotti [this message]
2001-08-31 6:05 ` kernel 2.4.9 on alphaev56 Andrey Panin
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=3B8E6055.42EF59FB@videoblaster.it \
--to=rgaggiotti@videoblaster.it \
--cc=linux-kernel@vger.kernel.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