This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Disabling an host package
- From: Bart Veer <bartv at ecoscentric dot com>
- To: andrew dot lunn at ascom dot ch
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Mon, 23 Sep 2002 11:34:08 +0100 (BST)
- Subject: Re: [ECOS] Disabling an host package
- References: <20020923082227.GF11487@biferten.ma.tech.ascom.ch>
>>>>> "Andrew" == Andrew Lunn <andrew.lunn@ascom.ch> writes:
Andrew> Hi folks
Andrew> When running to root configure script is it possible to
Andrew> disable the building of a package?
Not at this time. Since we may end up with quite a few packages with
host-side support, and since new packages may get added at any time,
adding --enable/--disable flags to the toplevel configure script is
not sensible. Instead it would be better for each per-package
configure script to perform appropriate autoconf tests and suppress
the build if the host is not up to the job - that is already done in
various places.
Andrew> I don't have the necassary linux stuff hanging around to
Andrew> be able to build the USB kernel module. It would be nice
Andrew> if i could disable this being built?
Which USB kernel module are you talking about here? The ecos_usbeth
loadable deriver in io/usb/eth/slave/current/host is not
autoconfiscated, so the toplevel configure script should ignore it.
The code in io/usb/slave/current/host should not have any unusual
requirements.
Hmmm, except that there are #include's for <linux/usb.h> and
<linux/usbdevice_fs.h>. If you are still running a 2.2. kernel without
the USB backport then those headers may not exist. OK, I'll add some
autoconf tests for those.
Bart
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss