Configuring usbmuxd v 1.0.7 in Fedora18, errors occurring
 

Hello,

I am new to the linux community; well, I loaded UBUNTU on a Windows laptop a while back, but I recently purchased a linuxed based machine and have Fedora18 installed. Unfortunately I also own two apple mobile devices (ipod touch4g and iphone3g). I would like to jailbreak them both and sync them with my new laptop. In my quest to jailbreak using evasi0n I have found that it is necessary to install a series of packages.

As of now I am building "usbmuxd-1.0.7" and recieving an error message. Here is the output from the terminal:



[cyclepath@localhost build]$ cmake ..
-- The CXX compiler identification is unknown
CMake Error: your CXX compiler: "CMAKE_CXX_COMPILER-NOTFOUND" was not found. Please set CMAKE_CXX_COMPILER to a valid compiler path or name.
-- Configuring usbmuxd v1.0.7
-- checking for module 'libplist'
-- package 'libplist' not found
* NOTE: libplist was not found!
* libusbmuxd/usbmuxd will be build WITHOUT support for version 1
* of the usbmux protocol (plist based).
-- Will build usbmuxd: YES
-- libusbmuxd will be built with inotify support
-- checking for module 'libusb-1.0>=1.0.3'
-- package 'libusb-1.0>=1.0.3' not found
USB_INCLUDE_DIR=USB_INCLUDE_DIR-NOTFOUND
USB_LIBRARY=USB_LIBRARY-NOTFOUND
CMake Error at Modules/LibFindMacros.cmake:74 (message):
Required library USB NOT FOUND.

Install the library (dev version) and try again. If the library is already
installed, use ccmake to set the missing variables manually.
Call Stack (most recent call first):
Modules/FindUSB.cmake:40 (libfind_process)
daemon/CMakeLists.txt:1 (find_package)


-- Configuring incomplete, errors occurred!
[cyclepath@localhost build]$
[/COLOR]



After reading the output I went to softpedia.com and found "libplist1.4". I downloaded the tar file, did the following and had more error messages:



[root@localhost libplist-1.4]# ls
AUTHORS COPYING include NEWS src
cmake COPYING.LESSER libplist.pc.in plutil swig
CMakeLists.txt doxygen.cfg libplist++.pc.in README test
[root@localhost libplist-1.4]# mkdir build
[root@localhost libplist-1.4]# cd build
[root@localhost build]# cmake ..
-- The C compiler identification is GNU 4.7.2
-- The CXX compiler identification is unknown
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
CMake Error: your CXX compiler: "CMAKE_CXX_COMPILER-NOTFOUND" was not found. Please set CMAKE_CXX_COMPILER to a valid compiler path or name.
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.27")
-- checking for module 'libxml-2.0'
-- package 'libxml-2.0' not found
-- Found LibXml2: /usr/local/lib/libxml2.so
-- checking for module 'glib-2.0'
-- package 'glib-2.0' not found
CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:97 (message):
Could NOT find GLIB2 (missing: GLIB2_LIBRARIES GLIB2_MAIN_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:291 (_FPHSA_FAILURE_MESSAGE)
cmake/modules/FindGLIB2.cmake:49 (find_package_handle_standard_args)
CMakeLists.txt:19 (FIND_PACKAGE)


-- Configuring incomplete, errors occurred!
[root@localhost build]#




I then downloaded and installed libxml2-2.8.0 with no error messages. I also downloaded glib-2.36.1 and had the following output:



[root@localhost glib-2.36.1]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... 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 we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for the BeOS... no
checking for Win32... no
checking for Mac OS X Carbon support... no
checking for Mac OS X Cocoa support... no
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking whether we are using the GNU C Library 2.1 or newer... yes
checking whether to enable garbage collector friendliness... no
checking whether to disable memory pools... no
checking for c++... no
checking for g++... no
checking for gcc... gcc
checking whether we are using the GNU C++ compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for gawk... (cached) gawk
checking for perl5... no
checking for perl... perl
checking for indent... no
checking for perl... /usr/bin/perl
checking for a Python interpreter with version >= 2.5... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib64/python2.7/site-packages
checking for iconv_open... yes
checking whether to cache iconv descriptors... no
checking for ZLIB... yes
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for LIBFFI... no
configure: error: Package requirements (libffi >= 3.0.0) were not met:

No package 'libffi' 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 LIBFFI_CFLAGS
and LIBFFI_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
[root@localhost glib-2.36.1]#




My last attempt to get somewhere was to download and install libffi-1.20 . Here was my configuration output:



[root@localhost libffi-1.20]# ./configure
creating cache ./config.cache
checking host system type... Invalid configuration `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized

checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking build system type... Invalid configuration `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized

checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
ltconfig: you must specify a host type if you use `--no-verify'
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
[root@localhost libffi-1.20]#




Is my approach to this problem correct or do I need to explore and different method? Am I trying to install packages that are not designed to be used with Fedora? I dont't have a clear grasp on linux. I know that UBUNTU and Fedora are two of the more popular distros and are based on different architectures. Is my attempt at configuring usbmuxd muddying to different linux worlds. It is as if I am compiling an entire operating system in my source folder...

Thank you for reading,

Occhi