From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.17-rc4-mm3-lockdep compilation error
Date: Mon, 29 May 2006 20:09:39 +0200 [thread overview]
Message-ID: <6bffcb0e0605291109s92ade61k4d4a96cd99e7ccf0@mail.gmail.com> (raw)
Hi Ingo,
lockdep-serial.patch is causing this error
/usr/src/linux-work/drivers/serial/serial_core.c:621:16: warning: incorrect type
in assignment (different base types)
/usr/src/linux-work/drivers/serial/serial_core.c:621:16: expected int [signed
] [addressable] [assigned] flags
/usr/src/linux-work/drivers/serial/serial_core.c:621:16: got
restricted unsig ned int
[usertype] flags
/usr/src/linux-work/drivers/serial/serial_core.c:686:12: warning:
incorrect type in
assignment (different base types)
/usr/src/linux-work/drivers/serial/serial_core.c:686:12: expected
restricted unsigned int
[usertype] new_flags
/usr/src/linux-work/drivers/serial/serial_core.c:686:12: got int
[signed] [ad dressable]
[assigned] flags
/usr/src/linux-work/drivers/serial/serial_core.c:2264:3: error:
undefined identi fier
'port_lock_key'
/usr/src/linux-work/drivers/serial/serial_core.c: In function
'uart_add_one_port ':
/usr/src/linux-work/drivers/serial/serial_core.c:2264: error:
'port_lock_key' un declared
(first use in this function)
/usr/src/linux-work/drivers/serial/serial_core.c:2264: error: (Each
undeclared i dentifier is
reported only once
/usr/src/linux-work/drivers/serial/serial_core.c:2264: error: for each
function it appears in.)
make[3]: *** [drivers/serial/serial_core.o] Error 1
make[2]: *** [drivers/serial] Error 2
make[1]: *** [drivers] Error 2
make: *** [_all] Error 2
gcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-libgcj-multifile
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
reply other threads:[~2006-05-29 18:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6bffcb0e0605291109s92ade61k4d4a96cd99e7ccf0@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®