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

Failed to build on Linux #35

Open
hiepnh0 opened this issue Oct 23, 2023 · 7 comments
Open

Failed to build on Linux #35

hiepnh0 opened this issue Oct 23, 2023 · 7 comments

Comments

@hiepnh0
Copy link

hiepnh0 commented Oct 23, 2023

./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:32: installing './compile'
configure.ac:6: installing './missing'
configure.ac:125: error: required file 'src/libimobiledevice-glue-1.0.pc.in' not found
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 thread-safe mkdir -p... /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 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 whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
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... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /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... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
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 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... no
configure: error: Package requirements (libplist-2.0 >= 2.3.0) were not met:

Requested 'libplist-2.0 >= 2.3.0' but version of libplist is 2.2.0-172-g2cd858c-dirty

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

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

@JonasVautherin
Copy link

You need libplist. I would recommend building it manually, installing it locally and pointing PKG_CONFIG_PATH. But if you build and install it system-wide, you won't need to set PKG_CONFIG_PATH (though I wouldn't recommend doing that: if you want to install it system-wide, make a proper package 🙈).

@khang30
Copy link

khang30 commented Sep 18, 2024

@JonasVautherin
libplist was already installed:
Requested 'libplist-2.0 >= 2.3.0' but version of libplist is 2.2.0-172-g2cd858c-dirty

@JonasVautherin
Copy link

Sure. But not a sufficiently new version.

@khang30
Copy link

khang30 commented Sep 18, 2024

run ./git-version-gen command in the libplist directory then it returns 2.2.0-172-g2cd858c-dirty
if i create a new tag name 2.3.0 then it returns 2.3.0 and the error disapears

@JonasVautherin
Copy link

if i create a new tag name 2.3.0 then it returns 2.3.0 and the error disapears

Of course if you remove the check, then the error disappears 😅. But I would assume that there is a reason for the check in the first place (maybe it builds with 2.2.0, but it will fail at runtime).

I would personally build libplist from sources (with a version >= 2.3.0).

@nikias
Copy link
Member

nikias commented Sep 18, 2024

@khang30 why don't you pull the latest master branch in your libplist directory, and you'll have 2.6.0

@khang30
Copy link

khang30 commented Sep 19, 2024

@nikias
i got it.
$git pull origin master does not get new tags but git fetch does.

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