fixincludes myth or reality?

[cts]

is fixincludes a myth? if not, where is it?

My tale:
RedHat8 kernel 18 on i686 installed OK
BUT
trying to get Kylix3 to work - it does, sort of
but everyone says it needs kernel 19 or 20

I need to bebuild the kernel (the idea seems grotesque but never mind)
I tried to make xconfig
but got errors in some header files
(I just came here from linuxquestions.org, there is a thread there, search for "fixincludes")

Seems like I need "fixincludes"
This is much talked about but where is it?
so I downloads a whole new gcc

try to configure the gcc but it halts saying:
checking size of short... configure: error: cannot determine a size for short
Configure in /usr/gccobj/gcc failed, exiting.
This is braindead software : the first thing you learn in school is the size of short.

Is this fatal?
Anyway I try
make bootstrap
and get a lot of header errors - seems like the elusive "fixincludes"
is still required and absent...

there is a directory called fixinc,
the README is packed with mumbo-jumbo
I dont want to join that cult...

My task is to investigate Linux and determine if it
is a suitable real-world replacement for Windows

I have to report: It aint
1) No functioning C++IDE (kylix3 is almost there)
2) Updates require kernel compile which is neither advisable nor possible.
(It may be possible for a coterie of experts (polite description), but
do they have the numbers and the social skills for business?)

[cts]

Install impressions:
Despite my negative assesment,
RedHat8 installation was excellent
Hardware recognition was excellent.
the Package Manager rpm system is excellent.

So the only problems so far are:
RW-CD on parallel port requires xconfig
(see header problem above)

Kylix3 is recommended to run on kernel 20
(see header problem above)

I stand by my remark that the clear majority of Makefiles I have encountered since 1969 have failed.

"Makefile considered harmful"?

[yinrunning]

My task is to investigate Linux and determine if it
is a suitable real-world replacement for Windows

I have to report: It aint
1) No functioning C++IDE (kylix3 is almost there)
2) Updates require kernel compile which is neither advisable nor possible.
(It may be possible for a coterie of experts (polite description), but
do they have the numbers and the social skills for business?)

From what you said in your post, it doesn't seem like you know enough about *nix to make an informed decision on that. Your personal lack of knowledge about the OS doesn't have anything to do with the feasibility of its use.

And, it's not up to any of us what you say about Linux or whether or not your company uses it. If you handed a bunch of MAC users a copy of Win2K Pro Advanced server and said, "Hey, you've got a week to set this all up and tell us what you think of it.", their responses would probably be along the same lines as yours are.

Basically, if it doesn't make business sense at this point in time for you and your company, then keep using Windows. The crashes and hangs that result are your problems. In my personal opinion, the Windows approach is "Give a man a fish", while the *nix approach is "Teach him how to fish." Which you choose is up to you.

[JohnT]

Fixincludes reading ....................HERE (http://www.google.com/linux?hl=en&lr=&ie=ISO-8859-1&q=fixincludes&btnG=Google+Search)

[endoalpha]

I am nor sure why you think Linux is the problem. There are plenty of other c++ ides for linux. check http://www.google.com/search?hl=en&ie=utf-8&oe=utf-8&q=c++ide+linux
as for the fixincludes problem... check here http://www.gnu.org/software/autogen/fixinc.html

and... Maybe your social skills are good for business, but your problem solving skills are sorely lacking.