On 28/11/12 18:52, Rick Stevens wrote:
> I reiterate:
>
> 1. Install the kernel source RPM.
>
> 2. Navigate to your ~/rpmbuild/SPECS directory.
>
> 3. Do "rpmbuild -bp --target=x86_64 kernel.spec" or
> "rpmbuild -bp --target=i686 kernel.spec" depending on your
>
On Wed, 2012-11-28 at 13:10 -0800, Joe Zeff wrote:
> What would be nice would be something like the traditional ./configure
> that didn't just examine the build environment, but probed the hardware
> and included the drivers you needed and only those. There would also be
> (I hope) a way to sp
On 11/28/2012 12:43 PM, JD wrote:
I do know about these rpmbuild options, which, when turned off
(--without xx)
does shorten the build time. But it is not enough. Building bazillions
of useless
(with regards to the user's HW platform) driver, enabling features by
default
which the user might not
On Wed, Nov 28, 2012 at 9:16 AM, Richard Shaw wrote:
> On Tue, Nov 27, 2012 at 6:44 PM, JD wrote:
>
>> The rpmbuild interface does not provide the user a way
>> to go through the entire config options before proceeding
>> to build the kernel. If it does, I would really like to know
>> how it's d
On 11/28/2012 09:46 AM, Bryn M. Reeves issued this missive:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/28/2012 05:07 PM, JD wrote:
The main point is that the build takes too darned long. On my
unicore cpu, it takes almost 2 days. Building bazillions of useless
modules is a great waste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/28/2012 05:07 PM, JD wrote:
> The main point is that the build takes too darned long. On my
> unicore cpu, it takes almost 2 days. Building bazillions of useless
> modules is a great waste of time and machine.
If you want to change the set of mo
On Tue, Nov 27, 2012 at 6:44 PM, JD wrote:
> The rpmbuild interface does not provide the user a way
> to go through the entire config options before proceeding
> to build the kernel. If it does, I would really like to know
> how it's done.
>
I agree it's not intuitive but check and see if this i
On Tue, Nov 27, 2012 at 6:19 PM, William Brown wrote:
> On Tue, 2012-11-27 at 21:06 -0500, Brian West wrote:
> > On 11/27/2012 07:44 PM, JD wrote:
> > > Hi Bruno, Alan,
> > >
> > > The rpmbuild interface does not provide the user a way
> > > to go through the entire config options before proceedin
On 11/27/2012 06:06 PM, Brian West issued this missive:
On 11/27/2012 07:44 PM, JD wrote:
Hi Bruno, Alan,
The rpmbuild interface does not provide the user a way
to go through the entire config options before proceeding
to build the kernel. If it does, I would really like to know
how it's done.
On 11/27/2012 09:19 PM, William Brown wrote:
On Tue, 2012-11-27 at 21:06 -0500, Brian West wrote:
On 11/27/2012 07:44 PM, JD wrote:
Hi Bruno, Alan,
The rpmbuild interface does not provide the user a way
to go through the entire config options before proceeding
to build the kernel. If it does,
On Tue, 2012-11-27 at 21:06 -0500, Brian West wrote:
> On 11/27/2012 07:44 PM, JD wrote:
> > Hi Bruno, Alan,
> >
> > The rpmbuild interface does not provide the user a way
> > to go through the entire config options before proceeding
> > to build the kernel. If it does, I would really like to know
On 11/27/2012 07:44 PM, JD wrote:
Hi Bruno, Alan,
The rpmbuild interface does not provide the user a way
to go through the entire config options before proceeding
to build the kernel. If it does, I would really like to know
how it's done.
The current rpmbuild of the kernel builds bazillions of
Hi Bruno, Alan,
The rpmbuild interface does not provide the user a way
to go through the entire config options before proceeding
to build the kernel. If it does, I would really like to know
how it's done.
The current rpmbuild of the kernel builds bazillions of
drivers, most of which are very lik
13 matches
Mail list logo
