recently I wanted to reinstall apollocaffe, I executed this command in terminal :
$git clone http://github.com/Russell91/apollocaffe.git && apollocaffe
after this I looked inside of apollocaffe for "Makefile.config" , but there isn't there, just "Makefile.config.example "
I used cmake for installing apollocaffe but after installing it doesn't contain : apollocaffe.so.
I looked Russell91's git about inside of apollocaffe's package , and I didn't see Makefile.config ethier.
what should I do?
I appreciate any help.
Edit:
I found that because I wanted to reinstall apollocaffe, I used :
rm -rf /apollocaffe
and this is the reason, but I don't know How can I fix it?
Related
I am trying to stall wiringpi in the raspberry for using the GPIO in C but the message says that:
"Package wiringpi is not available but is referred to by another package.
This may mean that the package is missing, has been obsolited , or is only available from nother source"
Does anyone knows why this is happening? I already check some similiar issues and nothing. The upgrade is already done . Or which apt does substitute wiringpi
(I am using the raspberry pi4)
Thanks a lot and have great day!!
I aleady found a solution!! thanks anyway here is the link just in case anyone has te same problem
http://wiringpi.com/download-and-install/
$ git clone git://git.drogon.net/wiringPi
$ cd ~/wiringPi
$ git pull origin
$ ./build
Ubuntu 20.04, downloaded singularity 3.7.3.tar.gz, sha256 matches, unzipped it and followed instructions but keep getting
Failed to get package version. Abort.
Any quick suggestions what I'm missing. I installed GO using a snap, and when I check the version I get
$ go version go version go1.16.3 linux/amd64
What am I missing. Thx, J.
I found a bug / problem!
In the file
/singularity/mconfig
is some code to check the version?
# if test -z "${package_version}" ; then
# echo "Failed to get package version. Abort."
# exit 1
# fi
I can't tell why this doesn't work because the file it is looking for is present.
If I comment out this code, the config, compile and install work seamlessly and do produce the correct version information! The syslabs.io people make it incredibly difficult to contact them to suggest a bug.
V2, got it to work, this is new to me but the quirk was I was downloading the .tar.gz into a directory that was already within a git repo. This affects where mconfig looks for the "VERSION" file and causes an error. Created a new directory outside any git repo's, dowloaded, untarred and mconfig,make, and make install all worked fine. Strange thae where it looks for VERSION file is changed?
I've upgraded React Native from 0.52 to 0.59 I'm aware this is a massive jump but I thought might as well go for it, and now getting glog/logging.h file not found.
I'm also aware that there are similar questions on here. But I've literally tried everything out there and I just can't seem to get this issue fixed.
Here's one of the things that I've tried:
cd node_modules/react-native/scripts && ./ios-install-third-party.sh && cd ../../../
cd node_modules/react-native/third-party/glog-0.3.4/ && ../../scripts/ios-configure-glog.sh && cd ../../../../
Anyone would think this would solve it right? I've left no stone unterned and it just doesn't want to go away. Fun!
Found a reference to the XCode app name having spaces here:
https://github.com/facebook/react-native/issues/19774
I also found that as I was using multiple versions, I had "XCode 10.1.app". When I changed it to XCode.app (and run something like sudo xcode-select --switch /Applications/Xcode.app to update the XCode path), my app built without this problem or any of the others I'd experienced to date with glog.
I install godef:
$ go get -u github.com/rogpeppe/godef
Looks great:
$ which godef
/home/username/go/bin/godef
Right where I expect it:
$ echo $GOPATH
/home/username/go
But when called as a command line tool:
$ godef version
godef: cannot read : open : no such file or directory
What's happening?
I would suggest you to read the documentation found here: https://github.com/rogpeppe/godef/blob/master/doc.go
You can also try typing godef -h.
If you want more information, please explain what you are actually trying to do.
EDIT: Regarding your comment above, I think that this library can't help you to accomplish what you are trying to do.
I ran into an issue trying to use godef-describe (C-c C-d) which would output the following error:
No description found for expression at point
If I tried using godef directly on a file, I would receive the following error:
% godef -f path/to/file.go "SomeFunction()"
2020/08/26 14:57:46 internal error: nil Pkg importing "io" from "github.com/some/package"
I fixed this by reinstalling godef and using the master branch as described here:
go get -v github.com/rogpeppe/godef#master
since the latest updates on go and go.mod you might want to install it on your user so you should use install instead of get
if you want to install godef to your gopath:
go install -v github.com/rogpeppe/godef#master
ive been trying to edit a Debian installation CD,
followed tutorial on debian website
https://wiki.debian.org/DebianInstaller/Modify/CD,
successfully extract cd, use genisoimage to recreate iso, try to install debian, no problem.
and then the problem, when i tried to edit one of the package, say i want to change a picture in a package .deb, i used this command:
extract .deb:
mkdir directoryname
cd directoryname
dpkg-deb -x pathtopackage/package_name.deb .
dpkg-deb -e pathtopackage/package_name.deb
building .deb :
dpkg-deb -b . pathtopackage/new_package_name.deb
and replaced the very same package on /pool/main debian cd directory
however after built the iso, it failed to install my edited package,
i've tried to fix md5 sum inside cd, rebuild dist/Release, still no luck.
any advice?
thanks in advance
finally did it.
first mistake
building .deb :
dpkg-deb -b . pathtopackage/new_package_name.deb
correct command:
dpkg-deb -b -Zgzip . pathtopackage/new_package_name.deb
to recreate exact package as original one
and then following the rest tutorial on https://wiki.debian.org/DebianInstaller/Modify/CD,
except for debootstrap error, it can be done by following tutorial from this page
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1001131
edit my debootstrap.deb, repackage, and voila, done all the works.
apparently my error was because debootstrap error from official debian page doesnt work for me.
hope this information useful for anyone