All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Bergeron <chris@pcburn.com>
To: linux-kernel@vger.kernel.org
Subject: Getting make net/built-in.o Error with 2.6.21.1 Build
Date: Mon, 07 May 2007 19:30:56 -0400	[thread overview]
Message-ID: <463FB6B0.3070005@pcburn.com> (raw)

On trying to build a 2.6.21.1 kernel using the configuration at 
http://pcburn.com/files/kernel/breaks.2.6.21.1.config I'm getting the 
following error with Networking Support -> Bluetooth Subsystem Support 
-> HIDP protocol support set to built-in:

  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
net/built-in.o: In function `hidp_add_connection':
(.text+0x8bb08): undefined reference to `hid_ff_init'
make: *** [.tmp_vmlinux1] Error 1

Works with that option turned off.  Also, the GCC version I'm using is 
the current Debian Etch release: gcc (GCC) 4.1.2 20061115 (prerelease) 
(Debian 4.1.1-21).  I also tried it with gcc (GCC) 3.4.6 (Debian 
3.4.6-5) for the same result.

I don't need to build that, so I simply unset it.  If this is at all 
useful and you need something else just CC: me in the reply.

Thanks,
-- Chris

             reply	other threads:[~2007-05-07 23:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 23:30 Chris Bergeron [this message]
2007-05-08  0:25 ` Getting make net/built-in.o Error with 2.6.21.1 Build Satyam Sharma
2007-05-08  0:25   ` Satyam Sharma
2007-05-08 15:49   ` Jiri Kosina
2007-05-08 15:49     ` Jiri Kosina
2007-05-08 16:05     ` Satyam Sharma
2007-05-08 16:05       ` Satyam Sharma
2007-05-08 16:23       ` Jiri Kosina
2007-05-08 16:23         ` Jiri Kosina
2007-05-08 16:48         ` [Bluez-devel] " Marcel Holtmann
2007-05-08 16:48           ` Marcel Holtmann
2007-05-08 17:47           ` Jiri Kosina
2007-05-08 17:47             ` Jiri Kosina
2007-05-08 17:50             ` [Bluez-devel] " Marcel Holtmann
2007-05-08 17:50               ` Marcel Holtmann
2007-05-08 17:50               ` Marcel Holtmann

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=463FB6B0.3070005@pcburn.com \
    --to=chris@pcburn.com \
    --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.