Cross compiling for RPi - error while loading shared libraries





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







3















I'm trying to compile a simple program (blinking.c) on my Ubuntu using the ARM cross compile toolchain (arm-linux-gnueabihf-gcc) and run it on my Raspberry Pi. The program is using the wiringPi shared library (wiringPi.so) located in ~/wiringPi/wiringPi on Ubuntu. The code follows:



#include "wiringPi.h"

int main (void)
{
wiringPiSetup();
pinMode(0, OUTPUT);

for (;;)
{
digitalWrite(0, HIGH);
delay(500);
digitalWrite(0, LOW);
delay(500);
}

return 0;
}


I used the command:



arm-linux-gnueabihf-gcc blinking.c -o blinking -L ~/wiringPi/wiringPi -lwiringPi -I ~/wiringPi/wiringPi


to compile and successfully get the object file, which I then transfer to Raspberry Pi.

However, when trying to run the program on Pi, I get the following error:
./blinking: error while loading shared libraries: libwiringPi.so: cannot open shared object file: No such file or directory



What am I missing?










share|improve this question







New contributor




A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • It looks like it can't find the library on the Pi. Have you installed wiringPi on the Pi (it should be preinstalled in full Raspbian, but not in Raspbian Lite).

    – joan
    9 hours ago











  • @joan Haven't installed wiringPi on Raspberry (using Raspbian Lite). I thought the compiler links the shared libraries to the program object files. I guess I need to learn more about dynamic libraries. Just saw the answer by Ralf which explains it.

    – A6SE
    9 hours ago






  • 1





    The Answer and comment are true BUT the the library should be installed on standard Raspbian - it is used by gpio. Currently /usr/lib/libwiringPi.so.2.50 (with a link from /usr/lib/libwiringPi.so) I note the OP has not identified what OS is in use.

    – Milliways
    7 hours ago




















3















I'm trying to compile a simple program (blinking.c) on my Ubuntu using the ARM cross compile toolchain (arm-linux-gnueabihf-gcc) and run it on my Raspberry Pi. The program is using the wiringPi shared library (wiringPi.so) located in ~/wiringPi/wiringPi on Ubuntu. The code follows:



#include "wiringPi.h"

int main (void)
{
wiringPiSetup();
pinMode(0, OUTPUT);

for (;;)
{
digitalWrite(0, HIGH);
delay(500);
digitalWrite(0, LOW);
delay(500);
}

return 0;
}


I used the command:



arm-linux-gnueabihf-gcc blinking.c -o blinking -L ~/wiringPi/wiringPi -lwiringPi -I ~/wiringPi/wiringPi


to compile and successfully get the object file, which I then transfer to Raspberry Pi.

However, when trying to run the program on Pi, I get the following error:
./blinking: error while loading shared libraries: libwiringPi.so: cannot open shared object file: No such file or directory



What am I missing?










share|improve this question







New contributor




A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • It looks like it can't find the library on the Pi. Have you installed wiringPi on the Pi (it should be preinstalled in full Raspbian, but not in Raspbian Lite).

    – joan
    9 hours ago











  • @joan Haven't installed wiringPi on Raspberry (using Raspbian Lite). I thought the compiler links the shared libraries to the program object files. I guess I need to learn more about dynamic libraries. Just saw the answer by Ralf which explains it.

    – A6SE
    9 hours ago






  • 1





    The Answer and comment are true BUT the the library should be installed on standard Raspbian - it is used by gpio. Currently /usr/lib/libwiringPi.so.2.50 (with a link from /usr/lib/libwiringPi.so) I note the OP has not identified what OS is in use.

    – Milliways
    7 hours ago
















3












3








3








I'm trying to compile a simple program (blinking.c) on my Ubuntu using the ARM cross compile toolchain (arm-linux-gnueabihf-gcc) and run it on my Raspberry Pi. The program is using the wiringPi shared library (wiringPi.so) located in ~/wiringPi/wiringPi on Ubuntu. The code follows:



#include "wiringPi.h"

int main (void)
{
wiringPiSetup();
pinMode(0, OUTPUT);

for (;;)
{
digitalWrite(0, HIGH);
delay(500);
digitalWrite(0, LOW);
delay(500);
}

return 0;
}


I used the command:



arm-linux-gnueabihf-gcc blinking.c -o blinking -L ~/wiringPi/wiringPi -lwiringPi -I ~/wiringPi/wiringPi


to compile and successfully get the object file, which I then transfer to Raspberry Pi.

However, when trying to run the program on Pi, I get the following error:
./blinking: error while loading shared libraries: libwiringPi.so: cannot open shared object file: No such file or directory



What am I missing?










share|improve this question







New contributor




A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I'm trying to compile a simple program (blinking.c) on my Ubuntu using the ARM cross compile toolchain (arm-linux-gnueabihf-gcc) and run it on my Raspberry Pi. The program is using the wiringPi shared library (wiringPi.so) located in ~/wiringPi/wiringPi on Ubuntu. The code follows:



#include "wiringPi.h"

int main (void)
{
wiringPiSetup();
pinMode(0, OUTPUT);

for (;;)
{
digitalWrite(0, HIGH);
delay(500);
digitalWrite(0, LOW);
delay(500);
}

return 0;
}


I used the command:



arm-linux-gnueabihf-gcc blinking.c -o blinking -L ~/wiringPi/wiringPi -lwiringPi -I ~/wiringPi/wiringPi


to compile and successfully get the object file, which I then transfer to Raspberry Pi.

However, when trying to run the program on Pi, I get the following error:
./blinking: error while loading shared libraries: libwiringPi.so: cannot open shared object file: No such file or directory



What am I missing?







c wiringpi cross-compilation shared-libraries






share|improve this question







New contributor




A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 9 hours ago









A6SEA6SE

1183




1183




New contributor




A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






A6SE is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • It looks like it can't find the library on the Pi. Have you installed wiringPi on the Pi (it should be preinstalled in full Raspbian, but not in Raspbian Lite).

    – joan
    9 hours ago











  • @joan Haven't installed wiringPi on Raspberry (using Raspbian Lite). I thought the compiler links the shared libraries to the program object files. I guess I need to learn more about dynamic libraries. Just saw the answer by Ralf which explains it.

    – A6SE
    9 hours ago






  • 1





    The Answer and comment are true BUT the the library should be installed on standard Raspbian - it is used by gpio. Currently /usr/lib/libwiringPi.so.2.50 (with a link from /usr/lib/libwiringPi.so) I note the OP has not identified what OS is in use.

    – Milliways
    7 hours ago





















  • It looks like it can't find the library on the Pi. Have you installed wiringPi on the Pi (it should be preinstalled in full Raspbian, but not in Raspbian Lite).

    – joan
    9 hours ago











  • @joan Haven't installed wiringPi on Raspberry (using Raspbian Lite). I thought the compiler links the shared libraries to the program object files. I guess I need to learn more about dynamic libraries. Just saw the answer by Ralf which explains it.

    – A6SE
    9 hours ago






  • 1





    The Answer and comment are true BUT the the library should be installed on standard Raspbian - it is used by gpio. Currently /usr/lib/libwiringPi.so.2.50 (with a link from /usr/lib/libwiringPi.so) I note the OP has not identified what OS is in use.

    – Milliways
    7 hours ago



















It looks like it can't find the library on the Pi. Have you installed wiringPi on the Pi (it should be preinstalled in full Raspbian, but not in Raspbian Lite).

– joan
9 hours ago





It looks like it can't find the library on the Pi. Have you installed wiringPi on the Pi (it should be preinstalled in full Raspbian, but not in Raspbian Lite).

– joan
9 hours ago













@joan Haven't installed wiringPi on Raspberry (using Raspbian Lite). I thought the compiler links the shared libraries to the program object files. I guess I need to learn more about dynamic libraries. Just saw the answer by Ralf which explains it.

– A6SE
9 hours ago





@joan Haven't installed wiringPi on Raspberry (using Raspbian Lite). I thought the compiler links the shared libraries to the program object files. I guess I need to learn more about dynamic libraries. Just saw the answer by Ralf which explains it.

– A6SE
9 hours ago




1




1





The Answer and comment are true BUT the the library should be installed on standard Raspbian - it is used by gpio. Currently /usr/lib/libwiringPi.so.2.50 (with a link from /usr/lib/libwiringPi.so) I note the OP has not identified what OS is in use.

– Milliways
7 hours ago







The Answer and comment are true BUT the the library should be installed on standard Raspbian - it is used by gpio. Currently /usr/lib/libwiringPi.so.2.50 (with a link from /usr/lib/libwiringPi.so) I note the OP has not identified what OS is in use.

– Milliways
7 hours ago












1 Answer
1






active

oldest

votes


















4














Shared or dynamic libraries are needed at run time. So you need the library not only on the build system but in on the target system, in this case on the PI.



This is different from static libraries. If you use a static library at build time, all the needed code from the library would be included in the executable, and the library would not be needed to run the program.



So you have to copy the library to the PI into a directory that is searched for shared libraries, such as /usr/lib or /usr/local/lib. You can also set LD_LIBRARY_PATH to point to the library, but then you must make sure it is always set when you want to execute the program.






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    return StackExchange.using("schematics", function () {
    StackExchange.schematics.init();
    });
    }, "cicuitlab");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "447"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });






    A6SE is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fraspberrypi.stackexchange.com%2fquestions%2f96177%2fcross-compiling-for-rpi-error-while-loading-shared-libraries%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    4














    Shared or dynamic libraries are needed at run time. So you need the library not only on the build system but in on the target system, in this case on the PI.



    This is different from static libraries. If you use a static library at build time, all the needed code from the library would be included in the executable, and the library would not be needed to run the program.



    So you have to copy the library to the PI into a directory that is searched for shared libraries, such as /usr/lib or /usr/local/lib. You can also set LD_LIBRARY_PATH to point to the library, but then you must make sure it is always set when you want to execute the program.






    share|improve this answer




























      4














      Shared or dynamic libraries are needed at run time. So you need the library not only on the build system but in on the target system, in this case on the PI.



      This is different from static libraries. If you use a static library at build time, all the needed code from the library would be included in the executable, and the library would not be needed to run the program.



      So you have to copy the library to the PI into a directory that is searched for shared libraries, such as /usr/lib or /usr/local/lib. You can also set LD_LIBRARY_PATH to point to the library, but then you must make sure it is always set when you want to execute the program.






      share|improve this answer


























        4












        4








        4







        Shared or dynamic libraries are needed at run time. So you need the library not only on the build system but in on the target system, in this case on the PI.



        This is different from static libraries. If you use a static library at build time, all the needed code from the library would be included in the executable, and the library would not be needed to run the program.



        So you have to copy the library to the PI into a directory that is searched for shared libraries, such as /usr/lib or /usr/local/lib. You can also set LD_LIBRARY_PATH to point to the library, but then you must make sure it is always set when you want to execute the program.






        share|improve this answer













        Shared or dynamic libraries are needed at run time. So you need the library not only on the build system but in on the target system, in this case on the PI.



        This is different from static libraries. If you use a static library at build time, all the needed code from the library would be included in the executable, and the library would not be needed to run the program.



        So you have to copy the library to the PI into a directory that is searched for shared libraries, such as /usr/lib or /usr/local/lib. You can also set LD_LIBRARY_PATH to point to the library, but then you must make sure it is always set when you want to execute the program.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 9 hours ago









        RalfFriedlRalfFriedl

        6811210




        6811210






















            A6SE is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            A6SE is a new contributor. Be nice, and check out our Code of Conduct.













            A6SE is a new contributor. Be nice, and check out our Code of Conduct.












            A6SE is a new contributor. Be nice, and check out our Code of Conduct.
















            Thanks for contributing an answer to Raspberry Pi Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fraspberrypi.stackexchange.com%2fquestions%2f96177%2fcross-compiling-for-rpi-error-while-loading-shared-libraries%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to label and detect the document text images

            Vallis Paradisi

            Tabula Rosettana