linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Marcel Holtmann <marcel@holtmann.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	kernel list <linux-kernel@vger.kernel.org>,
	linux-zigbee-devel <linux-zigbee-devel@lists.sourceforge.net>,
	Alexander Smirnov <alex.bluesman.smirnov@gmail.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jukka Rissanen <jukka.rissanen@linux.intel.com>
Subject: Re: linux-next: Tree for Jan 14 (lowpan, 802.15.4)
Date: Fri, 17 Jan 2014 10:49:59 -0800	[thread overview]
Message-ID: <52D97B57.9000000@infradead.org> (raw)
In-Reply-To: <CALT56yPzfkz7=WdT0p6EYXdsQJUT+Ld9gdd72z6_czn0YaKUWA@mail.gmail.com>

On 01/14/2014 02:54 PM, Dmitry Eremin-Solenikov wrote:
> Hello,
> 
> 
> On Tue, Jan 14, 2014 at 9:49 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> On 01/13/2014 09:51 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> This tree fails (more than usual) the powerpc allyesconfig build.
>>>
>>> Changes since 20140113:
>>>
>>
>>
>> on i386:
>>
>> net/built-in.o: In function `header_create':
>> 6lowpan.c:(.text+0x166149): undefined reference to `lowpan_header_compress'
>> net/built-in.o: In function `bt_6lowpan_recv':
>> (.text+0x166b3c): undefined reference to `lowpan_process_data'
> 
> Ah, nice Makefile hack there.
> David, Marcel, could you please consider the attached patch.
> 
> 

Hi,
I guess that the Makefile hack is still causing problems.
With today's linux-next (20140117), I see these build errors (or warnings
in the case of loadable modules):


when 802.15.4 and Bluetooth are built as loadable modules:

WARNING: net/ieee802154/6lowpan_iphc: 'lowpan_header_compress' exported twice. Previous export was in net/bluetooth/bluetooth.ko
WARNING: net/ieee802154/6lowpan_iphc: 'lowpan_process_data' exported twice. Previous export was in net/bluetooth/bluetooth.ko

when they are builtin to the kernel image:

net/ieee802154/built-in.o: In function `lowpan_header_compress':
(.text+0x3d00): multiple definition of `lowpan_header_compress'
net/bluetooth/built-in.o:(.text+0x2e8f0): first defined here
net/ieee802154/built-in.o: In function `lowpan_process_data':
(.text+0x3230): multiple definition of `lowpan_process_data'
net/bluetooth/built-in.o:(.text+0x2de20): first defined here


-- 
~Randy

  parent reply	other threads:[~2014-01-17 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  5:51 linux-next: Tree for Jan 14 Stephen Rothwell
2014-01-14 17:49 ` linux-next: Tree for Jan 14 (lowpan, 802.15.4) Randy Dunlap
2014-01-14 22:54   ` Dmitry Eremin-Solenikov
2014-01-15  9:45     ` Alexander Aring
2014-01-15 23:36     ` David Miller
2014-01-17 18:49     ` Randy Dunlap [this message]
2014-01-17 19:13     ` Stephen Warren
2014-01-17 19:20       ` Randy Dunlap
2014-01-17 20:59       ` Dmitry Eremin-Solenikov

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=52D97B57.9000000@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alex.bluesman.smirnov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dbaryshkov@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).