All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: drivers/ieee1394 duplicate symbol, 2.4.8-pre4
Date: Sun, 5 Aug 2001 23:53:43 -0400	[thread overview]
Message-ID: <20010805235343.S30381@visi.net> (raw)
In-Reply-To: <32414.997069600@ocs3.ocs-net>
In-Reply-To: <32414.997069600@ocs3.ocs-net>; from kaos@ocs.com.au on Mon, Aug 06, 2001 at 01:46:40PM +1000

On Mon, Aug 06, 2001 at 01:46:40PM +1000, Keith Owens wrote:
> drivers/ieee1394/raw1394.c:spinlock_t host_info_lock = SPIN_LOCK_UNLOCKED;
> drivers/ieee1394/nodemgr.c:spinlock_t host_info_lock = SPIN_LOCK_UNLOCKED;
> 
> when both raw1394 and nodemgr are linked into vmlinux, it gets
> 
> drivers/ieee1394/raw1394.o(.data+0x8): multiple definition of `host_info_lock'
> drivers/ieee1394/ieee1394.o(.data+0x8c): first defined here
> 
> Either host_info_lock should be static or it should be defined as
> extern in one source and referenced in the others.

It should be static. Thanks for the report. I believe this is fixed in
CVS, and if not, it will be soon.

Hopefully we'll get a chance to sync CVS to Linus before 2.4.8 final. If
not, I'll submit a patch for that bug atleast.

-- 
 .----------=======-=-======-=========-----------=====------------=-=-----.
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'

      reply	other threads:[~2001-08-06  3:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06  3:46 drivers/ieee1394 duplicate symbol, 2.4.8-pre4 Keith Owens
2001-08-06  3:53 ` Ben Collins [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=20010805235343.S30381@visi.net \
    --to=bcollins@debian.org \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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.