View Single Post
Old 04-28-03, 12:09 PM   #3
briansladecek
Registered User
 
Join Date: Apr 2003
Location: United States
Posts: 21
Default

Quote:
Originally posted by Kiamu
segfault:

http://cs-www.bu.edu/help/unix/segmentation_fault.html

the glibc is one of the most important libs in linux. if you make any errors compiling and installing it, you will be in deep trouble. don't know what went wrong, but the glibc does not like it, if you compile it with any optimisation flags turned on (CFLAGS and CXXFLAGS).
Howdy,

I think Tommi is following the advice from posts on this forum and many others, concerning the glibc problems with Redhat 9. I know I solved the problem by updating my glibc with the RPM's found on one of the Redhat 9 update mirrors.

* I guess he was building it from source instead of using the regular RPM update. In that case, your advice about optimization flags and glibc is well taken.

The funny thing about Redhat RPM's (in the case, specifically, about the glibc libraries), is that they provide (for Intel procs) an i686 update and and i386 update. I have no clue what "-march=" the stock glibc libraries were built against. But, when I tried to update with the i686 glibc RPM (cause my kernel and other libraries were built as such), it failed because the glibc i686 common libraries were not found.

Well, Redhat does not provide the glibc common libraries for i686. However, in the i386 update directory, there are the development, common, and several other glibc RPM dependency files there. I just install those updates and it works fine.

Anyone know more about the stock glibc libraries Redhat provides for an i686 or above host system? I can only assume they use a stock i386 glibc even though the rest of your libraries can be optimized for your higher instruction set host system. So, why do they provide an i686 glibc update and not include the common libraries to work with that RPM? any ideas?

thanks,

Brian Sladecek
briansladecek is offline   Reply With Quote