[<prev] [next>] [day] [month] [year] [list]
Message-ID: <dac45060801160532k3960d521wbce09bc44be145ee@mail.gmail.com>
Date: Wed, 16 Jan 2008 15:32:22 +0200
From: "Mark Ryden" <markryde@...il.com>
To: netdev@...r.kernel.org
Subject: Compiling as a module using the 2.6.25 git tree
Hello,
A question about compiling as module using the 2.6.25 git tree:
I had git cloned the 2.6.25 DaveM tree.
I ran "make menuconfig".
In many cases I see in the help:
"To compile this code as a module, choose M here: the
module will be called ..."
For example, in "Packet Generator" or in 802.1d Etherent Bridging
(CONFIG_BRIDGE).
However, I cannot choose 'M' here ; the toggle is only between
building into the kernel ('*')
or not.
BRIDGE depends (according to the help) only on CONFIG_NET and I have
CONFIG_NET selected.
more .config | grep CONFIG_INET
CONFIG_INET=y
Also llc is configured: (though in fact bridge selects llc).
more .config | grep LLC
CONFIG_LLC=y
CONFIG_LLC2=y
And in the Kconfig file we have:
config BRIDGE
tristate "802.1d Ethernet Bridging"
When I try "make menuconfig" on the kernel of a distro (like FC8) I
**can** choose
bridge as a module. (I see it as 'M').
Any ideas why? Is is something due to using the git tree?
Mark
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists