Azure-Samples / iot-hub-c-raspberrypi-client-app

Application collects weather data from a BME280 sensor and sends it to IoT hub, also take actions according to cloud-to-device message, device management.
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-raspberry-pi-kit-c-get-started
MIT License
36 stars 34 forks source link

Installing error of libcurl4-openssl-dev on Raspbian buster #34

Open yjin81 opened 4 years ago

yjin81 commented 4 years ago

Hey

I am trying to use this on Raspbian buster, and having an installation error of libcurl4-openssl-dev as below after running the ./setup.sh command. I am not sure whether this already supports Raspbian buster.

The following packages have unmet dependencies:
 libcurl4-openssl-dev : Conflicts: libssl1.0-dev but 1.0.2q-2 is to be installed
E: Unable to correct problems, you have held broken packages.

But if I try to install libcurl4-openssl-dev by apt-get install command, I do not get the same error. image

Tobro88 commented 3 years ago

Just wanted to chime in on having the exact same problem without having been able to solve it. I am using Raspberry Pi4 with Buster (I am making a wild assumption here that if it is intended to work on a Pi3 it should be possible to make it work on Pi4 as well) - if it isn't supposed to work perhaps it would be good to list a warning high up on the original tutorial page(link)

There are some discussions on an Alexa related thread about the same problem (link). There a solution is stated where you do:

sudo nano /home/pi/pi.sh

and then find libssl1.0-dev and change to libssl-dev.

However I can not even find the pi.sh script...

Tobro88 commented 3 years ago

Well whaddayouknow? Instead of tearing out my hair in not being able to find a pi.sh file I tried my luck by replacing libssl1.0-dev with libssl-dev in setup.sh. And it seems to do the job!

Emphasis lies on "seems" because I am running into my next problem now (fatal: unable to connect to git.drogon.net).

Tobro88 commented 3 years ago

But that problem seems to be resolved by commenting out the following lines in setup.sh:

git clone git://git.drogon.net/wiringPi cd ./wiringPi ./build cd ..

I think that's justified because I have installed wiringPi separately already (sudo ap-get install wiringpi).

And then...

EUREKA! IT WORKS!