On Thu, 08 Feb 2007 15:02:00 -0800, Paul Pluzhnikov <[EMAIL PROTECTED]> wrote: > Robert Heller <[EMAIL PROTECTED]> writes: > >> These would be the RHEL 4.x compatibility packages. They might do what >> you need though, > > I seriously doubt they will -- OP will still be compiling against > newer libc and kernel headers, and linking against newer libc.so. > > If it *does* work for non-trivial programs, please post an update.
Seems to work. I have a problem with linking to libperl.so, but I know what to do (link against same libperl on the build box). My app runs, but fails to link to perl when it decides to do so at runtime. > Otherwise, the "standard" options are: > - develop on the lowest release you plan to support (usually the > simplest option), > - install a FC6-x86 -> FC3-x86 cross-compiler > - use Apptools: http://autopackage.org/apbuild-apgcc.php > >> by giving you an even older build chain then is normal >> for either FC3 or FC6. Generally, code built with an older build >> chain, so long as it it not too old, will result in executables that >> will run on a various newer systems. > > But that says nothing about executables running on older systems > then what they were built on. Build chain itself is likely not the > problem, it's the libraries and headers that the executable uses. Agreed. Also, interestingly, not only the app used to fail witi SIGFPE, but also "ldd app". I hope that I will fix the perl issue tonight. i _______________________________________________ help-gplusplus mailing list help-gplusplus@gnu.org http://lists.gnu.org/mailman/listinfo/help-gplusplus
