[ale] glibc compatibility problem

[Bob Toxen]

On Tue, Jun 15, 2004 at 10:46:13AM -0400, Dow Hurst wrote:
> Does it really require access to the source code or just unlinked binaries? 
> At what point does glibc dependencies get inserted into a program during 
> construction?
You need only the unlinked object files (*.o) to link with whatever
reasonably compatible libraries are on the current system.  This is
what we used to do in the Unix world "in the old days" so that an
application would run on somewhat different versions of a system without
giving clients the source code.

Note too that there is some flexibility in mixing and matching kernels
with the rest of the system.  I discovered by accident a few years ago
that a 2.4 kernel will happily power an older version of Slackware that
expected a 2.2 kernel, for example.
> Dow
Bob


> Dow Hurst wrote:
> >But it *does* require access to the source code to do it, correct?  And, 
> >help from those who have access?  This is the modelling package from 
> >Schrodinger and they probably would prefer we buy the latest version as 
> >an upgrade to even bother with helping in a situation like this.  I 
> >guess I'll need to reload with SuSE 9.0 instead of 9.1.  The new 2.6 
> >kernel series that doesn't require mounting of removeable media is so 
> >nice for users.  I really wanted to have it.  But, no matter, I can 
> >reload quickly.
> >Dow
> >
> >
> >Bob Toxen wrote:
> >
> >>Dow,
> >>
> >>It does sound like rebuilding or at least re-linking under 2.6 would 
> >>solve
> >>this problem.  An alternative would be static linking.
> >>
> >>Bob
> >>
> >>On Mon, Jun 14, 2004 at 05:58:41PM -0400, Dow Hurst wrote:
> >>
> >>>I have an application that is refusing to run under the 2.6 kernel 
> >>>with this error:
> >>>
> >>>/usr/local/schrodinger/maestro-v51020/bin/Linux-x86/maestro: 
> >>>relocation error: 
> >>>/usr/local/schrodinger/maestro-v51020/bin/Linux-x86/maestro: symbol 
> >>>errno, version GLIBC_2.0 not defined in file libc.so.6 with link time 
> >>>reference
> >>>Maestro: Could not load shared library
> >>>
> >>>Is there a way around this or do I need a new binary compiled under 
> >>>libc 2.3.3?  Running SuSE 9.1 with 2.6.4-54.5-smp.  Thanks,
> >>>Dow
> >>>
> >>>
> >>>-- 
> >>>__________________________________________________________
> >>>Dow Hurst                  Office: 770-499-3428            *
> >>>Systems Support Specialist    Fax: 770-423-6744            *
> >>>1000 Chastain Rd. Bldg. 12                                 *
> >>>Chemistry Department SC428  Email:   dhurst at kennesaw.edu   *
> >>>Kennesaw State University         Dow.Hurst at mindspring.com *
> >>>Kennesaw, GA 30144                                         *
> >>>************************************************************
> >>>This message (including any attachments) contains          *
> >>>confidential information intended for a specific individual*
> >>>and purpose, and is protected by law.  If you are not the  *
> >>>intended recipient, you should delete this message and are *
> >>>hereby notified that any disclosure, copying, distribution *
> >>>of this message, or the taking of any action based on it,  *
> >>>is strictly prohibited.                                    *
> >>>************************************************************
> >>>
> >>>_______________________________________________
> >>>Ale mailing list
> >>>Ale at ale.org
> >>>http://www.ale.org/mailman/listinfo/ale
> >>
> >>
> >>
> >

> -- 
> __________________________________________________________
> Dow Hurst                  Office: 770-499-3428            *
> Systems Support Specialist    Fax: 770-423-6744            *
> 1000 Chastain Rd. Bldg. 12                                 *
> Chemistry Department SC428  Email:   dhurst at kennesaw.edu   *
> Kennesaw State University         Dow.Hurst at mindspring.com *
> Kennesaw, GA 30144                                         *
> ************************************************************
> This message (including any attachments) contains          *
> confidential information intended for a specific individual*
> and purpose, and is protected by law.  If you are not the  *
> intended recipient, you should delete this message and are *
> hereby notified that any disclosure, copying, distribution *
> of this message, or the taking of any action based on it,  *
> is strictly prohibited.                                    *
> ************************************************************

> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale