-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorry, i know this is a beginner question, and i apologize #124
Comments
Hi there, According to your error it seems like you are missing libimobiledevice-glue Compile and install libimobiledevice-glue then try to compile libirecovery again P/S: You may need also to compile and install other requirements |
@snoopyonline78 please attach your full compile log here. |
I think you're trying to install in a non-default path try building and installing into for example |
Wow, thanks a lot, will try Thanks!!!!!! |
|
You installed it. Btw, don't run configure or make as root (sudo). Only for installation you need sudo ( |
Thanks a lot to all, but not helped. I try to install idevicerestore and this error comes: devicerestore$ ./autogen.sh No package 'libimobiledevice-1.0' found Consider adjusting the PKG_CONFIG_PATH environment variable if you Alternatively, you may set the environment variables libimobiledevice_CFLAGS |
You have installed libimobiledevice-glue but you are still need to install libimobiledevice |
Hallo, i install libimobiledevice, and in the installation of libimobiledevice i get the error message, that libimobledivice-glue is not installed |
Hi, maybe you are following the wrong order, please refer to this issue here |
Sorry for asking for this professional community something like that, but i can't continue or starting compiling because of this error:
configure: error: Package requirements (libimobiledevice-glue-1.0 >= 1.0.0) were not met:
I got the glue file in a other folder, but it isn't revealed.
Is there a guide to learn compiling this things. It's not the first time, i must give up because of this errors :(
The text was updated successfully, but these errors were encountered: