This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: unresolved symbols when link an application statically


On Wed, 2003-04-16 19:59:34 +0700, Alexey Morozov <morozov at novosoft dot ru>
wrote in message <20030416125934 dot GC9203 at bebi dot novosoft dot ru>:
> On Tue, Apr 15, 2003 at 11:37:12PM -0700, Roland McGrath wrote:
> > Object files and static libraries (.a) are not ABI-compatible with a new
> > libc.  The only guarantee you get is that (correct) shared objects (.so)
> > that worked before will continue to work.  If you have static libraries,
> > you need to recompile them from source using the new libc's headers if you
> > want to link against a new libc.
[...]
> I understand that another option is to install glibc-2.2 headers and static
> libs and compile my application against this library...

Uargs. That sounds like I should go^Wrun to toilett! If Oracle is too
dumb, dump them:) Ask for shared libraries. By the way - they eventually
won't give you anything if your system isn't certified...

Welcome to commercial software:(

MfG, JBG (been there, gone back)

-- 
   Jan-Benedict Glaw       jbglaw at lug-owl dot de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

Attachment: pgp00000.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]