Skip to content
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

Open
snoopyonline78 opened this issue Dec 6, 2023 · 12 comments
Open

Sorry, i know this is a beginner question, and i apologize #124

snoopyonline78 opened this issue Dec 6, 2023 · 12 comments

Comments

@snoopyonline78
Copy link

snoopyonline78 commented Dec 6, 2023

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 :(

@mast3rz3ro
Copy link

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
Copy link
Author

Thanks a lot for your answer, i verry appreciate it!

i already Configured, make and make install the libimobiledevice-glue, but the installer don't recognize it :( see screenshots)
Uploading Screenshot from 2023-12-12 10-40-10.png…

@snoopyonline78
Copy link
Author

Screenshot from 2023-12-12 10-41-25
Screenshot from 2023-12-12 10-40-47

@mast3rz3ro
Copy link

@snoopyonline78 please attach your full compile log here.

@DanTheMann15
Copy link
Contributor

I think you're trying to install in a non-default path

try building and installing into /usr/local instead by also passing --prefix=/usr/local, if you must install elsewhere there are guides on the internet to add other paths, for path, include, library, and pkgconfig or pkgconf paths.

for example ./autogen.sh --prefix=/usr/local then make and then sudo make install

@snoopyonline78
Copy link
Author

Wow, thanks a lot, will try

Thanks!!!!!!

@snoopyonline78
Copy link
Author

snoopyonline78 commented Dec 21, 2023

xxxxxxx@Lat7400:~/libimobiledevice-glue$ sudo ./configure 
Place your finger on the fingerprint reader
Verification timed out
[sudo] password for xxxxxxx: 
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libplist-2.0 >= 2.3.0... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking for asprintf... yes
checking for strcasecmp... yes
checking for strdup... yes
checking for strerror... yes
checking for strndup... yes
checking for stpcpy... yes
checking for vasprintf... yes
checking for getifaddrs... yes
checking for endian.h... yes
checking for platform-specific build settings... linux-gnu
checking whether gcc is Clang... no
checking whether pthreads work with "-pthread" and "-lpthread"... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking whether more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for pthread_cancel... yes
checking for pthread_once... yes
checking wether the C compiler supports constructor/destructor attributes... yes
checking for struct dirent.d_type... yes
checking for supported compiler flags...  -Wall -Wextra -Wmissing-declarations -Wredundant-decls -Wshadow -Wpointer-arith -Wwrite-strings -Wswitch-default -Wno-unused-parameter -fsigned-char -fvisibility=hidden
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether make supports nested variables... (cached) yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/libimobiledevice-glue-1.0.pc
config.status: creating include/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands

Configuration for libimobiledevice-glue 1.0.0-4-ge314faa:
-------------------------------------------

  Install prefix: .........: /usr/local

  Now type 'make' to build libimobiledevice-glue 1.0.0-4-ge314faa,
  and then 'make install' for installation.

xxxxxxx@Lat7400:~/libimobiledevice-glue$ sudo ./make
sudo: ./make: command not found
xxxxxxx@Lat7400:~/libimobiledevice-glue$ sudo mak
sudo: mak: command not found
xxxxxxx@Lat7400:~/libimobiledevice-glue$ sudo make
make  all-recursive
make[1]: Entering directory '/home/xxxxxxx/libimobiledevice-glue'
Making all in src
make[2]: Entering directory '/home/xxxxxxx/libimobiledevice-glue/src'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue/src'
Making all in include
make[2]: Entering directory '/home/xxxxxxx/libimobiledevice-glue/include'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue/include'
make[2]: Entering directory '/home/xxxxxxx/libimobiledevice-glue'
make[2]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue'
make[1]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue'
xxxxxxx@Lat7400:~/libimobiledevice-glue$ sudo make install
Making install in src
make[1]: Entering directory '/home/xxxxxxx/libimobiledevice-glue/src'
make[2]: Entering directory '/home/xxxxxxx/libimobiledevice-glue/src'
 /usr/bin/mkdir -p '/usr/local/lib'
 /bin/bash ../libtool   --mode=install /usr/bin/install -c   libimobiledevice-glue-1.0.la '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/libimobiledevice-glue-1.0.so.0.0.0 /usr/local/lib/libimobiledevice-glue-1.0.so.0.0.0
libtool: install: (cd /usr/local/lib && { ln -s -f libimobiledevice-glue-1.0.so.0.0.0 libimobiledevice-glue-1.0.so.0 || { rm -f libimobiledevice-glue-1.0.so.0 && ln -s libimobiledevice-glue-1.0.so.0.0.0 libimobiledevice-glue-1.0.so.0; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libimobiledevice-glue-1.0.so.0.0.0 libimobiledevice-glue-1.0.so || { rm -f libimobiledevice-glue-1.0.so && ln -s libimobiledevice-glue-1.0.so.0.0.0 libimobiledevice-glue-1.0.so; }; })
libtool: install: /usr/bin/install -c .libs/libimobiledevice-glue-1.0.lai /usr/local/lib/libimobiledevice-glue-1.0.la
libtool: install: /usr/bin/install -c .libs/libimobiledevice-glue-1.0.a /usr/local/lib/libimobiledevice-glue-1.0.a
libtool: install: chmod 644 /usr/local/lib/libimobiledevice-glue-1.0.a
libtool: install: ranlib /usr/local/lib/libimobiledevice-glue-1.0.a
libtool: finish: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the '-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the 'LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the 'LD_RUN_PATH' environment variable
     during linking
   - use the '-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to '/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
 /usr/bin/mkdir -p '/usr/local/lib/pkgconfig'
 /usr/bin/install -c -m 644 libimobiledevice-glue-1.0.pc '/usr/local/lib/pkgconfig'
make[2]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue/src'
make[1]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue/src'
Making install in include
make[1]: Entering directory '/home/xxxxxxx/libimobiledevice-glue/include'
make[2]: Entering directory '/home/xxxxxxx/libimobiledevice-glue/include'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/include'
 /usr/bin/mkdir -p '/usr/local/include/libimobiledevice-glue'
 /usr/bin/install -c -m 644  libimobiledevice-glue/socket.h libimobiledevice-glue/thread.h libimobiledevice-glue/utils.h libimobiledevice-glue/collection.h libimobiledevice-glue/termcolors.h libimobiledevice-glue/cbuf.h libimobiledevice-glue/opack.h libimobiledevice-glue/tlv.h '/usr/local/include/libimobiledevice-glue'
make[2]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue/include'
make[1]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue/include'
make[1]: Entering directory '/home/xxxxxxx/libimobiledevice-glue'
make[2]: Entering directory '/home/xxxxxxx/libimobiledevice-glue'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue'
make[1]: Leaving directory '/home/xxxxxxx/libimobiledevice-glue'

@nikias
Copy link
Member

nikias commented Dec 22, 2023

You installed it. Btw, don't run configure or make as root (sudo). Only for installation you need sudo (sudo make install).
Now you might have to run:
sudo ldconfig
So the new library will become available.

@snoopyonline78
Copy link
Author

Thanks a lot to all, but not helped. I try to install idevicerestore and this error comes:

devicerestore$ ./autogen.sh
libtoolize: putting auxiliary files in '.'.
libtoolize: linking file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: linking file 'm4/libtool.m4'
libtoolize: linking file 'm4/ltoptions.m4'
libtoolize: linking file 'm4/ltsugar.m4'
libtoolize: linking file 'm4/ltversion.m4'
libtoolize: linking file 'm4/lt~obsolete.m4'
configure.ac:37: installing './compile'
configure.ac:6: installing './missing'
src/Makefile.am: installing './depcomp'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @file support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libirecovery-1.0 >= 1.0.1... yes
checking for libimobiledevice-1.0 >= 1.3.0... no
configure: error: Package requirements (libimobiledevice-1.0 >= 1.3.0) were not met:

No package 'libimobiledevice-1.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables libimobiledevice_CFLAGS
and libimobiledevice_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

@mast3rz3ro
Copy link

You have installed libimobiledevice-glue but you are still need to install libimobiledevice

@snoopyonline78
Copy link
Author

Hallo, i install libimobiledevice, and in the installation of libimobiledevice i get the error message, that libimobledivice-glue is not installed

@mast3rz3ro
Copy link

Hi, maybe you are following the wrong order, please refer to this issue here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants