legacy linker (uses libc5) fails on linux kernel 2.6.25 -
We have a legacy linker that uses libc5, and due to many factors, we only have binary and the source Yes, version control will have saved us from our current problem ... which is now in use for our full equipment series and product line, but this horse has long gone for a long time.
This linker fails with this message on the Linux kernel 2.6.24, but 2.6.25 (and 2.6.26)
Virtual Memory has crossed 'New' / Pre>We had a similar problem with this legacy compiler, but with some stackoverflow.com and much research, we found that the compiler problem was due to "Brack Rendimization" in Linux kernel 2.6.25. Alternatively, set up a sysctl vars and an environment variable:
/ proc / sys / kernel / randomize_v_space = 0 or 1 setenv MALLOC_TOP_PAD_ 536870 912This, however, It does not help to linker
I got it from using "LDD", which the linker shared more library dependency (compiler was only libc.so.5):
libg ++ .27 => /usr/lib/libg++.so.27 (0xb7eca000) libstdc ++ So.27 => /usr/lib/libstdc++.so.27 (0xb7e99000) libm.so.5 => /lib/libm.so.5 (0xb7e90000) libc.so.5 => /lib/libc.so. 5 (0xb7dd3000)And I have read that I might have to install the libc5 version of libg ++. So.27 I hesitate to do this because I do not know whether this latest lib + + Override So.72 and will cause problems for non-libc5 apps.
So, do I find the Liby version of League +. .27, or is there a better way to disable brack rendering, or is there another difference between 2.6.24 and 2.6.25 kernel, which is causing the linker problem?
Edit
See all the details of this search and my final resolution.
This does not answer your question at all, but in your situation, I know-to-work Libc + libstdc ++ combination, or even kernel + libc + libstdc ++ (in this case you need a virtual machine, obviously). In this way, you can try things relatively easily, without dismissing any thing.
The best way to be compatible with the old library is to use this old library, after all, because it is "just", Tokenen's problem, using some kind of jail / crute / virtual machine is very much Should not be a problem?
Comments
Post a Comment