• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 4182 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Linking two different libraries.

Pritam Nandy
Note: This was originally posted on 16th February 2010 at http://forums.arm.com

[font="Verdana"]
[size=2]
Hi,

How do I link two different libraries each of which have been generated by two different Compiler set? The first one's generated by using ADS 1.2 while the second one's generated by using RVDS 2.2. For linking, I need to use the RVDS 2.2 linker. Also, will I need to make any changes in other files such as the Scatter Load file (.scl) or Map file (.map) for generating the ELF as a result of linking this two separate libraries?

If somebody could also provide me the command-line options to be given to the linker for this purpose, that would be of help too.

If the above details are falling short for you to be able to answer this question, please do let me know the specifics that you need. I'll try to provide them at the earliest.

-Pritam.
[/size]
[/font]
  • Note: This was originally posted on 24th February 2010 at http://forums.arm.com

    [font="Arial"]
    RVDS and ADS use different binary ABIs, so you have to compile the RVDS library (and any code that library is linked with) using the old ADS ABI. If you don't then there is a high probability that (1) it won't work, or (2) it will look like it works and then crash in rather nasty and hard to predict ways. More information is provided on this documentation page:

    [url="http://infocenter.arm.com/help/topic/com.arm.doc.dui0202f/Chdccfff.html"]infocenter.arm.com/.../url]

    In terms of how to link - the same as you would link two binaries produced with the same compiler set - there is nothing special about linking two libraries from different tool sets.

    Note that the ADS ABI is deprecated in RVDS 2.2 and removed from RVDS 3.0, so it is not possible to link old binaries with the newer versions of the compiler - you will need to recompile old binaries from source with the newer tools.

    Hi,

    Now, when I try to run the linker to link the two libraries I get the following error message -
    Warning: L6637W: No input objects specified. At least one input object or library(object) must be specified.
    Building image.
    Optimizing COMMON Sections
    Q60X0A_SBNAX.scl(line 8126, col 23) Error: L6236E: No section matches selector - no section to be FIRST/LAST.
    Q60X0A_SBNAX.scl(line 8241, col 18) Error: L6236E: No section matches selector - no section to be FIRST/LAST.
    Not enough information to produce a SYMDEFs file.
    Not enough information to list image symbols.
    Not enough information to list the image map.
    Finished: 5 information, 1 warning and 2 error messages.

    Anybody, has an idea what this error's about and how could I fix it?
    [/font]
  • Arm Employee Badge
    Note: This was originally posted on 16th February 2010 at http://forums.arm.com

    How do I link two different libraries each of which have been generated by two different Compiler set? The first one's generated by using ADS 1.2 while the second one's generated by using RVDS 2.2. For linking, I need to use the RVDS 2.2 linker. Also, will I need to make any changes in other files such as the Scatter Load file (.scl) or Map file (.map) for generating the ELF as a result of linking this two separate libraries?


    RVDS and ADS use different binary ABIs, so you have to compile the RVDS library (and any code that library is linked with) using the old ADS ABI. If you don't then there is a high probability that (1) it won't work, or (2) it will look like it works and then crash in rather nasty and hard to predict ways. More information is provided on this documentation page:

    [url="http://infocenter.arm.com/help/topic/com.arm.doc.dui0202f/Chdccfff.html"]http://infocenter.arm.com/help/topic/com.a...f/Chdccfff.html[/url]

    In terms of how to link - the same as you would link two binaries produced with the same compiler set - there is nothing special about linking two libraries from different tool sets.

    Note that the ADS ABI is deprecated in RVDS 2.2 and removed from RVDS 3.0, so it is not possible to link old binaries with the newer versions of the compiler - you will need to recompile old binaries from source with the newer tools.
  • Arm Employee Badge
    Note: This was originally posted on 3rd March 2010 at http://forums.arm.com

    [font="Arial"]
    Hi,

    Now, when I try to run the linker to link the two libraries I get the following error message -
    [i]Warning: L6637W: No input objects specified. At least one input object or library(object) must be specified.
    [...]
    [/font]


    What command line are using?  It looks like you tried to use armlink as if you were doing a final link.

    A library is usually an archive file (.l, .b, .a or .lib) that has multiple object files (.o), called the "members", packed into it by armar (or just ar).  When armlink sees an archive file on it's command link it will usually use only the members that are needed to satisify a missed symbol definition.  If you give armlink just two archives there will be no missing symbol references and no members will be selected and you'll get the message above.

    If you have two libraries, foo.lib and bar.lib, and you are trying to make one new library out of them then you probably want to extract all the members and make a new library; something like this:
    mkdir newlib
    cd newlib
    armar -x .../foo.lib
    armar -x .../bar.lib
    armar -cr new.lib *.o