From: "Jon K. Akers" <jka@mbi.ufl.edu>
To: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: RE: 2.5.69-mm5
Date: Wed, 14 May 2003 10:33:43 -0400 [thread overview]
Message-ID: <CDD2FA891602624BB024E1662BC678ED843F91@mbi-00.mbi.ufl.edu> (raw)
I like to at least build the new stuff that comes out with Andrew's
patches, and building the new gadget code that came out in -mm4 I got
this when building as a module:
make -f scripts/Makefile.build obj=drivers/serial
make -f scripts/Makefile.build obj=drivers/usb/gadget
gcc -Wp,-MD,drivers/usb/gadget/.net2280.o.d -D__KERNEL__ -Iinclude
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=i686
-Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc
-iwithprefix include -DMODULE -DKBUILD_BASENAME=net2280
-DKBUILD_MODNAME=net2280 -c -o drivers/usb/gadget/net2280.o
drivers/usb/gadget/net2280.c
drivers/usb/gadget/net2280.c:2623: pci_ids causes a section type
conflict
make[2]: *** [drivers/usb/gadget/net2280.o] Error 1
make[1]: *** [drivers/usb/gadget] Error 2
make: *** [drivers] Error 2
I was not able to test this particular part of the code with -mm4, as I
use a single processor system and could not get to the module building
process then.
I have also tested this by compiling it into the kernel, with the same
results:
gcc -Wp,-MD,drivers/usb/gadget/.net2280.o.d -D__KERNEL__ -Iinclude
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=i686
-Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc
-iwithprefix include -DKBUILD_BASENAME=net2280
-DKBUILD_MODNAME=net2280 -c -o drivers/usb/gadget/net2280.o
drivers/usb/gadget/net2280.c
drivers/usb/gadget/net2280.c:2623: pci_ids causes a section type
conflict
make[2]: *** [drivers/usb/gadget/net2280.o] Error 1
make[1]: *** [drivers/usb/gadget] Error 2
make: *** [drivers] Error 2
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2003-05-14 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 14:33 Jon K. Akers [this message]
2003-05-14 16:30 ` 2.5.69-mm5 Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 16:35 2.5.69-mm5 Jon K. Akers
2003-05-14 16:42 ` 2.5.69-mm5 Greg KH
2003-05-14 8:29 2.5.69-mm5 Andrew Morton
2003-05-14 12:33 ` 2.5.69-mm5 Ed Tomlinson
2003-05-15 19:51 ` 2.5.69-mm5 William Lee Irwin III
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=CDD2FA891602624BB024E1662BC678ED843F91@mbi-00.mbi.ufl.edu \
--to=jka@mbi.ufl.edu \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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