From: Axel Siebenwirth <axel@hh59.org>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.30: [SERIAL] build fails at 8250.c
Date: Fri, 2 Aug 2002 03:25:17 +0200 [thread overview]
Message-ID: <20020802012517.GA196@prester.freenet.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0208011425410.1612-100000@penguin.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
Hi!
building 2.5.30 fails at serial driver 8250 in file 8250.c compiled as
module.
This is how it looks like (full log gzipped and attached):
make[2]: Entering directory /usr/src/linux-2.5.30/drivers/serial'
gcc -Wp,-MD,./.8250.o.d -D__KERNEL__ -I/usr/src/linux-2.5.30/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -nostdinc -iwithprefix
include -DMODULE -include /usr/src/linux-2.5.30/include/linux/modversions.h
-DKBUILD_BASENAME=8250 -DEXPORT_SYMTAB -c -o 8250.o 8250.c
In file included from 8250.c:34:
/usr/src/linux-2.5.30/include/linux/serialP.h:50: field count' has
incomplete
type
8250.c:106: `ASYNC_BOOT_AUTOCONF' undeclared here (not in a function)
8250.c:106: `ASYNC_SKIP_TEST' undeclared here (not in a function)
8250.c:106: initializer element is not constant
8250.c:106: (near initialization for d_serial_port[0].flags')
8250.c:106: initializer element is not constant
8250.c:106: (near initialization for d_serial_port[0]')
8250.c:106: `ASYNC_BOOT_AUTOCONF' undeclared here (not in a function)
8250.c:106: `ASYNC_SKIP_TEST' undeclared here (not in a function)
8250.c:106: initializer element is not constant
8250.c:106: (near initialization for d_serial_port[1].flags')
8250.c:106: initializer element is not constant
8250.c:106: (near initialization for d_serial_port[1]')
8250.c:106: `ASYNC_BOOT_AUTOCONF' undeclared here (not in a function)
8250.c:106: `ASYNC_SKIP_TEST' undeclared here (not in a function)
8250.c:106: initializer element is not constant
8250.c:106: (near initialization for d_serial_port[2].flags')
8250.c:106: initializer element is not constant
...
and so on.
Regards,
Axel Siebenwirth
[-- Attachment #2: BUILD.LOG.gz --]
[-- Type: application/x-gunzip, Size: 2139 bytes --]
next prev parent reply other threads:[~2002-08-02 1:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 21:30 Linux 2.5.30 Linus Torvalds
2002-08-01 23:32 ` Banai Zoltan
2002-08-02 0:12 ` Alexander Viro
2002-08-02 0:38 ` Banai Zoltan
2002-08-02 3:17 ` Linus Torvalds
2002-08-02 12:23 ` Alan Cox
2002-08-02 16:57 ` Thomas Molina
2002-08-02 21:29 ` Linus Torvalds
2002-08-03 5:16 ` Nathaniel
2002-08-02 1:25 ` Axel Siebenwirth [this message]
2002-08-02 17:13 ` Linux 2.5.30: [SERIAL] build fails at 8250.c Russell King
2002-08-02 19:19 ` Axel Siebenwirth
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 22:49 Adam J. Richter
2002-08-02 23:56 ` Russell King
2002-08-03 0:12 ` Russell King
2002-08-03 1:05 ` Kai Germaschewski
2002-08-03 0:20 Adam J. Richter
2002-08-03 8:05 ` Russell King
2002-08-03 8:42 Adam J. Richter
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=20020802012517.GA196@prester.freenet.de \
--to=axel@hh59.org \
--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