piscsi: Missing header file during easyinstall.sh compilation

Info

  • Which version of Pi are you using: Raspberry Pi Zero W
  • Which github revision of software: v21.10.01
  • Which board version: 68kmla Version 2.4a
  • Which computer is the RaSCSI connected to: Mac Plus (well, eventually, I have not soldered in the headers to my RaspPi yet)

Describe the issue

After following the Setup Instructions and running ./easyinstall.sh, I get the following build error:


-- Creating directory obj/fullspec
mkdir -p obj/fullspec
arm-linux-gnueabihf-g++ -O3 -Wall -Werror -DNDEBUG -std=c++17 -Wno-psabi -iquote                                    . -D_FILE_OFFSET_BITS=64 -MD -MP  -DCONNECT_TYPE_FULLSPEC -c rascsi.cpp -o obj/                                   fullspec/rascsi.o
In file included from devices/device_factory.h:18:0,
                 from rascsi.cpp:19:
./rascsi_interface.pb.h:9:42: fatal error: google/protobuf/stubs/common.h: No su                                   ch file or directory
 #include <google/protobuf/stubs/common.h>
                                          ^
compilation terminated.
Makefile:153: recipe for target 'obj/fullspec/rascsi.o' failed
make: *** [obj/fullspec/rascsi.o] Error 1

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 18 (11 by maintainers)

Most upvoted comments

So after some fiddling, I was able to successfully complete the upgrade from RaspOS “stretch” to “buster” on my 8GB card.

I ran “easyinstall.sh” and it completed without a hitch. I haven’t tested RaSCSI yet, because I still have to do some soldering, but since this ticket pertained to “easyinstall.sh”, and it now runs, I am closing this ticket.

To recap, this is what I have confirmed:

  • “easyinstall.sh” does not work with “stretch” due to a missing “stdout_color_sinks.h”
  • Upgrading from “stretch” to “buster” does resolve the problem.

I more or less used this guide https://pimylifeup.com/upgrade-raspbian-stretch-to-raspbian-buster for the upgrade, but had to resolve several issues due to low disk space and/or incompatible packages. None of this really has any bearing on RaSCSI and are just quirks of my own setup.