Ok. I see I realize I will have better luck getting backward compatibility rather than forward compatibility.
Jeremiah Richard Shann <[email protected]> wrote: >I have done a bit of research on this topic and have come up with these > >http://www.pixelbeat.org/programming/linux_binary_compatibility.html > >http://www.redhat.com/archives/psyche-list/2003-June/msg00095.html > >http://unix.stackexchange.com/questions/9705/can-new-glibc-versions-be-used-with-an-old-kernel > >Another interesting link >http://stackoverflow.com/questions/6941332/anticipate-kernel-too-old-errors-between-2-6-16-and-2-6-26-kernel-versions >which has this snippet: >One way you can determine the minimum kernel version for a given ELF >file is to run file on it, like so: > >$ echo 'int main(){}' > test.c >$ gcc -o test test.c >$ file test >test: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked >(uses shared libs), for GNU/Linux 2.6.38, not stripped > >The important part here is the "for GNU/Linux 2.6.38", which indicates >the minimum kernel version. > >Richard > > > >On Sat, 2012-08-25 at 09:25 +0100, Richard Shann wrote: >> I should explain better: >> On Fri, 2012-08-24 at 23:35 -0500, Jeremiah Benham wrote: >> > Unfortunately I am not getting a segfault. I do know what to do now. >> > It >> > segfaults after I added the libglib libraries. >> what I am thinking is that it is not because the libglib libraries are >> the wrong ones, but that they allow the program to get as far as >> actually starting, whereupon it tries a glibc call (likely the startup >> before main() ) and that segfaults. You could find out where it >> segfaults to confirm this, my guess is it is before it gets to main(). >> (use gdb with b main). If it was adding the libglib libraries that was >> bad it would get past main and try to call gtk_init() and then crash. >> >> Hence my reasoning that trying to run with a miss-matched pair of >> kernel-glibc is probably a dead end. >> >> So the thing to try is putting in the libglib stuff and running on some >> other modern distro. Possibly taking out glibc as it is available in the >> distro, (and the glibc in the distro will work with the kernel in that >> distro). >> >> Richard >> >> >> _______________________________________________ >> Denemo-devel mailing list >> [email protected] >> https://lists.gnu.org/mailman/listinfo/denemo-devel > > _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
