All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.21-pre3 fails compile of ehci-hcd.c
Date: 09 Jan 2003 02:11:15 -0500	[thread overview]
Message-ID: <1042096276.8219.126.camel@madmax> (raw)

Hello All,

Noticed that I could not get patch-2.4.21-pre3 to compile:

	make[3]: Entering directory `/usr/src/kernels/linux-2.4.20/drivers/usb'
	ld -m elf_i386 -r -o usbcore.o usb.o usb-debug.o hub.o devio.o inode.o drivers.o devices.o hcd.o
	gcc -D__KERNEL__ -I/usr/src/kernels/linux-2.4.20/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4    -nostdinc -iwithprefix include -DKBUILD_BASENAME=ehci_hcd  -c -o hcd/ehci-hcd.o hcd/ehci-hcd.chcd/ehci-hcd.c: In function `ehci_start':
	hcd/ehci-hcd.c:343: parse error before `;'
	hcd/ehci-hcd.c:416: parse error before `;'
	hcd/ehci-hcd.c: In function `ehci_stop':
	hcd/ehci-hcd.c:501: parse error before `;'
	hcd/ehci-hcd.c: In function `ehci_irq':
	hcd/ehci-hcd.c:685: parse error before `;'

I'm not sure why gcc 2.95.3 is failing on the macro expansion, but it is
turning:
	ehci_warn (ehci, "illegal capability!\n");
into:
	printk("<4>"  "%s %s: "   "illegal capability!\n" , hcd_name, ( ehci   ) ;
which is missing the ->... structure reference.  The macros in
ehci-dbg.c work just fine if you give them one or more arguments
following the format string definition.

Compiler is gcc 2.95.3, binutils 2.12.90.0.9 20020526, glibc 2.2.5 on a
Slackware 8.0 distribution.

Kris



             reply	other threads:[~2003-01-09  7:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09  7:11 Kristofer T. Karas [this message]
2003-01-09  7:38 ` 2.4.21-pre3 fails compile of ehci-hcd.c Greg KH
2003-01-09  8:29   ` Kristofer T. Karas
2003-01-09  8:54     ` Greg KH

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=1042096276.8219.126.camel@madmax \
    --to=ktk@enterprise.bidmc.harvard.edu \
    --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 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.