Sfdwhf

A case of the sniffles

RSA: Danger of using p to create q

dbcc cleantable batch size explanation

Why "Having chlorophyll without photosynthesis is actually very dangerous" and "like living with a bomb"?

how to check a propriety using r studio

"You are your self first supporter", a more proper way to say it

Mortgage Pre-approval / Loan - Apply Alone or with Fiancée?

Roll the carpet

Important Resources for Dark Age Civilizations?

How can bays and straits be determined in a procedurally generated map?

Do I have a twin with permutated remainders?

Did Shadowfax go to Valinor?

What doth I be?

Is it possible to do 50 km distance without any previous training?

Is it inappropriate for a student to attend their mentor's dissertation defense?

Is it unprofessional to ask if a job posting on GlassDoor is real?

What's that red-plus icon near a text?

Which country benefited the most from UN Security Council vetoes?

Can a Cauchy sequence converge for one metric while not converging for another?

How is it possible to have an ability score that is less than 3?

How does one intimidate enemies without having the capacity for violence?

Two films in a tank, only one comes out with a development error – why?

How to move a thin line with the black arrow in Illustrator?

How much RAM could one put in a typical 80386 setup?

Cross compiling for RPi - error while loading shared libraries

Missing libcofi_rpi.so on host machineMongodb cross compilation on linux for Raspberry Pihow to install cross-compiled OpenCV's libraries on raspbery piCross Compiling Protobuf for Raspberry PiCross-Compiling kernel can't find gccEmbedded Xinu for RPiCross Compile Error Using arm-linux-gnueabihf-gccWhen I compile with arm-linux-gnueabihf-g++ version 4.7, I get error while loading shared libraries: libstdc++.so.6Is it possible to fix the “cannot find -lgcc” and “cannot find -lgcc_s” error messages when using arm-linux-gnueabihf-g++ as a linker?What's causing these crashes after cross-compiling?

.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?

c wiringpi cross-compilation shared-libraries

share|improve this question

asked 2 hours ago

A6SEA6SE

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.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  2 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
  2 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
  12 mins ago
  
  
  

  
  
  
  

add a comment | 

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?

c wiringpi cross-compilation shared-libraries

share|improve this question

asked 2 hours ago

A6SEA6SE

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.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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
  2 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
  2 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
  12 mins ago
  
  
  

  
  
  
  

add a comment | 

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

asked 2 hours ago

A6SEA6SE

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.

#include "wiringPi.h"



int main (void)

{

    wiringPiSetup();

    pinMode(0, OUTPUT);



    for (;;)

    {

        digitalWrite(0, HIGH);

        delay(500);

        digitalWrite(0, LOW);

        delay(500);

    }



    return 0;

}

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

share|improve this question

asked 2 hours ago

A6SEA6SE

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.

share|improve this question

asked 2 hours ago

A6SEA6SE

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.

asked 2 hours ago

A6SEA6SE

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.

asked 2 hours ago

A6SEA6SE

1183

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

answered 2 hours ago

RalfFriedlRalfFriedl

6811210

add a comment | 

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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

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

Name

Email

Required, but never shown

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

answered 2 hours ago

RalfFriedlRalfFriedl

6811210

add a comment | 

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

answered 2 hours ago

RalfFriedlRalfFriedl

6811210

add a comment | 

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

answered 2 hours ago

RalfFriedlRalfFriedl

6811210

share|improve this answer

answered 2 hours ago

RalfFriedlRalfFriedl

6811210

answered 2 hours ago

RalfFriedlRalfFriedl

6811210

answered 2 hours ago

RalfFriedlRalfFriedl

6811210