* Compiler & Statically Linked Question
@ 2002-11-26 18:50 Richard B. Tilley (Brad)
2002-11-26 19:12 ` Chris Friesen
0 siblings, 1 reply; 4+ messages in thread
From: Richard B. Tilley (Brad) @ 2002-11-26 18:50 UTC (permalink / raw)
To: linux-kernel
Hello,
I would like to start running some of the 2.5.x kernels for testing
purposes on a wide selection (about 12 machines) of Intel x86 PCs that I
have collected for testing purposes.
I would like to have one build machine where I build a kernel and then
use that kernel on all of the test PCs. I do not want to build a kernel
for each machine.
The PCs have very different hardware and I'd like to play around with
different c libraries on these PCs. So, what would be the best way to
build a kernel that would work in this type of environment?
Thank you,
Brad
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Compiler & Statically Linked Question
2002-11-26 18:50 Compiler & Statically Linked Question Richard B. Tilley (Brad)
@ 2002-11-26 19:12 ` Chris Friesen
2002-11-26 19:20 ` Richard B. Tilley (Brad)
0 siblings, 1 reply; 4+ messages in thread
From: Chris Friesen @ 2002-11-26 19:12 UTC (permalink / raw)
To: Richard B. Tilley (Brad); +Cc: linux-kernel
Richard B. Tilley (Brad) wrote:
> I would like to have one build machine where I build a kernel and then
> use that kernel on all of the test PCs. I do not want to build a kernel
> for each machine.
Build all the kernels for the lowest common denominator of processor,
and compile in all the drivers for all the hardware.
> The PCs have very different hardware and I'd like to play around with
> different c libraries on these PCs. So, what would be the best way to
> build a kernel that would work in this type of environment?
The kernel has nothing to do with different C libraries.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Compiler & Statically Linked Question
2002-11-26 19:12 ` Chris Friesen
@ 2002-11-26 19:20 ` Richard B. Tilley (Brad)
2002-11-26 19:39 ` Chris Friesen
0 siblings, 1 reply; 4+ messages in thread
From: Richard B. Tilley (Brad) @ 2002-11-26 19:20 UTC (permalink / raw)
To: Chris Friesen; +Cc: linux-kernel
On Tue, 2002-11-26 at 14:12, Chris Friesen wrote:
> The kernel has nothing to do with different C libraries.
>
> Chris
So, if the compiler on the build system was gcc-3.2 and the c library
was glibc-2.2.x, then it would not matter if the compiler and c library
on the install systems were of differing versions? Is this what you
mean?
Thank you,
Brad
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Compiler & Statically Linked Question
2002-11-26 19:20 ` Richard B. Tilley (Brad)
@ 2002-11-26 19:39 ` Chris Friesen
0 siblings, 0 replies; 4+ messages in thread
From: Chris Friesen @ 2002-11-26 19:39 UTC (permalink / raw)
To: Richard B. Tilley (Brad); +Cc: linux-kernel
Richard B. Tilley (Brad) wrote:
> So, if the compiler on the build system was gcc-3.2 and the c library
> was glibc-2.2.x, then it would not matter if the compiler and c library
> on the install systems were of differing versions? Is this what you
> mean?
Correct. The kernel is totally self-sufficient and does not use the C
library.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-11-26 19:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-26 18:50 Compiler & Statically Linked Question Richard B. Tilley (Brad)
2002-11-26 19:12 ` Chris Friesen
2002-11-26 19:20 ` Richard B. Tilley (Brad)
2002-11-26 19:39 ` Chris Friesen
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.