Linux newbie question: I do have the glibc-devel-2.2.5.rpm from RH7.3 install CD. How can I extract those header files? Or is it necessary to install the rpm? Or....do I need to download the glibc-devel-2.2.5 sorces?

Thanks in advance!

Thanks 2 the sollution from cmleungive...

I now have no more linker erro's, just installed the compat-glibc lib... and it worked fine now , without reinstalling...

After reading through all the prior comments, I was able to get Kylix 3 running under Redhat 9 by doing the following:

1. Install the compat-glibc package.
2. Change the project include and lib directories to point to the /usr/i386-glibc21-linux/* instead of /usr/*.
3. Update the kylix/include/defs.h and _defs.h files with the new include path.
4. Add to the startbcb script before bcblin is executed the command: export LD_ASSUME_KERNEL=2.2.5

These were the only changes a needed to make for everything to work. Thanks for all your comments.

Hi,

Thanks for the comments and helpful thread.
I am running Linux7.3 and Kylix3. I have followed the steps and reconfigured my project as above, but I am still having a problem...

When I include <stdio.h> I get an error in _algobase.h E2285. I do not have this problem if I gcc from commandline. Any ideas ?

*edit* this was a problem with <string> instead of <string.h> and the memcmp funciton. its solved now

Hmmm I can't find anything on the net so I think i'll ask here:

Having received the errors with time.h, I moved /usr/include up to the top of the path list. That ended the time.h problem, but now I have one new error:

[Linker Fatal Error] Fatal: Unable to open file 'crt1.o'

Doing a search I found that crt1.o is found in /usr/lib, so not really knowing what was wrong I added that to the path directory after /usr/include.
It made no difference.

Does anyone know the solution to this problem?

Thanks alot
Paul

try to remove the /lib from the library path, that fixed the problem on my pc

I have the same problem when kylix3 runs on red hat linux 9. It has troubled me a long time.
Cmleungive's methods do work!
Hansentech gives a good working detail and HVDV makes me know that Cmleungive's methods do work.
thanks again to them!