Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

libc

  • 14-04-2004 12:12am
    #1
    fractal
    Registered Users, Registered Users 2 Posts: 95 ✭✭


    Quick question...

    Could anyone tell me what libc.a does? If an executable is dependant on libc.so does libc.a have to be there too?

    Any help _greatly_ appreciated and the sooner the better! (not meaning to rush anyone, but my FYP is due on Friday) BAH!


Comments

  • #2
    albertw
    Closed Accounts Posts: 395 ✭✭albertw


    Originally posted by fractal
    Could anyone tell me what libc.a does? If an executable is dependant on libc.so does libc.a have to be there too?

    They are both c libraries. .a is an archive library, and .so is the shared object library.

    Deleting libc.a will render any programs that are linked against it unuseable, so its probably best to leave it there.

    Most programs are compiled against the .so, and I think that is the default.

    Cheers,
    ~Al


  • #3
    Dizz
    Closed Accounts Posts: 423 ✭✭Dizz


    .a are libraries that are statically linked to at compile time - all code needed by the application linking to the .a is pulled into the appplication's executable (hence larger executables)
    .so are dynamic libraries who methods/functions are loaded when needed at runtime (more commonly a link to a library with it's version in the filename)
    How an application is linked to a library of either type is up to the developer of said application.
    You could delete the .a file if you are not doing any development work or compiling new packages but don't delete the .so or its corresponding link - don't delete anything libc related - could wind up with nasty probs seeing almost everything (correct me if wrong) has a dependancy on libc

    Dizz


Advertisement