All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain Munaut <tnt@246tNt.com>
To: Joerg Maier <joerg.maier@shove-it.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: compile error on 2.6.20-rc1
Date: Sun, 17 Dec 2006 12:35:49 +0100	[thread overview]
Message-ID: <45852B95.6050008@246tNt.com> (raw)
In-Reply-To: <20061216135256.GB7526@shove-it.de>

Joerg Maier wrote:
> Hi,
>
> i got the following compile error:
>
> $ gcc -m32 -Wp,-MD,drivers/usb/host/.ohci-hcd.o.d  -nostdinc -isystem /usr/lib/gcc/powerpc-linux-gnu/4.1.2/include -D__KERNEL__ -Iinclude  -include include/linux/autoconf.h -Iarch/powerpc -Iarch/powerpc/include -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -msoft-float -pipe -Iarch/powerpc -ffixed-r2 -mmultiple -mno-altivec -funit-at-a-time -mstring -mcpu=powerpc -Wa,-maltivec -fomit-frame-pointer -g  -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign   -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(ohci_hcd)"  -D"KBUILD_MODNAME=KBUILD_STR(ohci_hcd)" -c -o drivers/usb/host/.tmp_ohci-hcd.o drivers/usb/host/ohci-hcd.c
> In file included from drivers/usb/host/ohci-hcd.c:945:
> drivers/usb/host/ohci-ppc-soc.c:225: error: redefinition of '__inittest'
> drivers/usb/host/ohci-pci.c:252: error: previous definition of '__inittest' was here
> drivers/usb/host/ohci-ppc-soc.c:225: error: redefinition of 'init_module'
> drivers/usb/host/ohci-pci.c:252: error: previous definition of 'init_module' was here
> drivers/usb/host/ohci-ppc-soc.c:226: error: redefinition of '__exittest'
> drivers/usb/host/ohci-pci.c:260: error: previous definition of '__exittest' was here
> drivers/usb/host/ohci-ppc-soc.c:226: error: redefinition of 'cleanup_module'
> drivers/usb/host/ohci-pci.c:260: error: previous definition of 'cleanup_module' was here
>
> i found both CONFIG macros set in my config: CONFIG_USB_OHCI_HCD_PPC_SOC and CONFIG_PCI. they lead to an include for ohci-ppc-soc.c and ohci-pci.c. Both declare (after preprocessing)  the symbol __inittest.
>
> Is the use of these two config options an error?
>
> Hoping that this was not discussed before and i did not find it.
>
> Joerg
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
>   
You can't compile ohci in module if you have several bus glues.

I sent a fix for this, it is in Greg KH "list", pending merge ...


    Sylvain

      reply	other threads:[~2006-12-17 11:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 13:52 compile error on 2.6.20-rc1 Joerg Maier
2006-12-17 11:35 ` Sylvain Munaut [this message]

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=45852B95.6050008@246tNt.com \
    --to=tnt@246tnt.com \
    --cc=joerg.maier@shove-it.de \
    --cc=linuxppc-dev@ozlabs.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.