> On Sep 17, 2015, at 4:35 PM, Matthew Flatt <mfl...@cs.utah.edu> wrote:
> 
> Our experience is that building shared libraries on a machine with
> GLibC 2.12 produces shared libraries that work most everywhere. In
> other words, you should rebuild the shared libraries on that ancient
> Linux installation, and then you're probably in good shape for the
> foreseeable future.

Got it. Many thanks!

John

> 
> At Thu, 17 Sep 2015 19:25:27 -0400, "'John Clements' via Racket Users" wrote:
>> Okay, really, this question as not that much to do with Racket, but…
>> 
>> As part of the ‘portaudio’ package, there are a number of shared libraries. 
>> It 
>> turns out that I’m going to be teaching in a room running an ancient Linux 
>> (CentOS 6?), and when I try to start portaudio, I get an error message 
>> indicating that my shared library wants a GLIBC with version >= 2.14, and 
>> this 
>> machine has 2.12, dating back to 2010.
>> 
>> So, here’s my question: would it be likely to solve my problem to just 
>> statically link my library against a current version of glibc, or is this an 
>> Extremely Bad Idea because the version of glibc that’s installed on a 
>> machine 
>> knows things about the OS that would be broken if I were to use a statically 
>> linked library?
>> 
>> … Or is there some other thing I should be doing? I see that DrRacket starts 
>> up fine, which suggests to me the racket has solved this problem.
>> 
>> Many thanks in advance!
>> 
>> John
>> 
>> 
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to racket-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to