Page 1 of 1

[SOLVED] RPM build fail: missing: No such file or directory

PostPosted: Jan 3rd, '20, 19:34
by minfrin
Hi all,

I am building the tarmux 1.0.2 package from https://github.com/minfrin/tarmux/releases/tag/1.0.2 through copr and every build is working fine except for Mageia.

While the initial package is built with autotools, and created with "make dist" and then "rpmbuild -bs tarmux-1.0.2.tar.bz2", and the resulting tarball definitely contains missing, depcomp, etc, I get the following failure when building across all versions of Mageia.

Does anyone know what I am doing wrong?

Code: Select all
+ CONFIGURE_TOP=.
+ /usr/lib/rpm/mageia/force-as-needed-for-shared-lib-in-libtool
Forcing -Wl,--as-needed in configure/libtool to workaround libtool bug (cf http://lists.gnu.org/archive/html/libtool-patches/2004-06/msg00002.html)
+ /usr/lib/rpm/mageia/drop-ld-no-undefined-for-shared-lib-modules-in-libtool
Modifying ltmain.sh underlinking for plugins (cf http://wiki.mandriva.com/en/Underlinking)
+ /usr/lib/rpm/mageia/fix-libtool-ltmain-from-overlinking
Fixing libtool's ltmain.sh to prevent overlinking (cf http://wiki.mandriva.com/en/Overlinking)
+ /usr/lib/rpm/mageia/fix-libtool-from-moving-options-after-libs .
Fixing libtool inside configure to pass -Wl,xxx options before libraries
+ /usr/lib/rpm/mageia/fix-dlsearch-path-in-libtool-for-multilib . lib64
+ cd .
+ '[' '!' -f configure.in -a '!' -f configure.ac ']'
+ libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
+ '[' -f ./configure.in -o -f ./configure.ac ']'
+ CONFIGURE_XPATH='--x-includes=/usr/include --x-libraries=/usr/lib64'
+ ./configure x86_64-mageia-linux-gnu --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --x-includes=/usr/include --x-libraries=/usr/lib64
configure: WARNING: you should use --build, --host, --target
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
[b]/bin/sh: /builddir/build/BUILD/tarmux-1.0.2/missing: No such file or directory
configure: WARNING: 'missing' script is too old or missing
[/b]checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-mageia-linux-gnu
checking host system type... x86_64-mageia-linux-gnu
checking how to print strings... printf
checking whether make supports the include directive... yes (GNU style)
checking for x86_64-mageia-linux-gnu-gcc... x86_64-mageia-linux-gnu-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 x86_64-mageia-linux-gnu-gcc accepts -g... yes
checking for x86_64-mageia-linux-gnu-gcc option to accept ISO C89... none needed
checking whether x86_64-mageia-linux-gnu-gcc understands -c and -o together... yes
checking dependency style of x86_64-mageia-linux-gnu-gcc... none
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 x86_64-mageia-linux-gnu-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/x86_64-mageia-linux-gnu-nm -p
checking the name lister (/usr/bin/x86_64-mageia-linux-gnu-nm -p) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-mageia-linux-gnu file names to x86_64-mageia-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-mageia-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for x86_64-mageia-linux-gnu-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for x86_64-mageia-linux-gnu-dlltool... no
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for x86_64-mageia-linux-gnu-ar... x86_64-mageia-linux-gnu-ar
checking for archiver @FILE support... @
checking for x86_64-mageia-linux-gnu-strip... no
checking for strip... strip
checking for x86_64-mageia-linux-gnu-ranlib... x86_64-mageia-linux-gnu-ranlib
checking command to parse /usr/bin/x86_64-mageia-linux-gnu-nm -p output from x86_64-mageia-linux-gnu-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 x86_64-mageia-linux-gnu-mt... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... x86_64-mageia-linux-gnu-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 x86_64-mageia-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-mageia-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
checking if x86_64-mageia-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
checking if x86_64-mageia-linux-gnu-gcc static flag -static works... no
checking if x86_64-mageia-linux-gnu-gcc supports -c -o file.o... yes
checking if x86_64-mageia-linux-gnu-gcc supports -c -o file.o... (cached) yes
checking whether the x86_64-mageia-linux-gnu-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 x86_64-mageia-linux-gnu-gcc... (cached) x86_64-mageia-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether x86_64-mageia-linux-gnu-gcc accepts -g... (cached) yes
checking for x86_64-mageia-linux-gnu-gcc option to accept ISO C89... (cached) none needed
checking whether x86_64-mageia-linux-gnu-gcc understands -c and -o together... (cached) yes
checking dependency style of x86_64-mageia-linux-gnu-gcc... (cached) none
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for inline... inline
checking for pid_t... yes
checking for size_t... yes
checking for ssize_t... yes
checking for uint32_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for clock_gettime... yes
checking archive_write_set_format_raw usability... no
checking archive_write_set_format_raw presence... no
checking for archive_write_set_format_raw... no
checking for x86_64-mageia-linux-gnu-pkg-config... /usr/bin/x86_64-mageia-linux-gnu-pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libarchive... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating tarmux.spec
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
+ /usr/bin/make -O -j2 V=1 VERBOSE=1
CDPATH="${ZSH_VERSION+.}:" && cd . && aclocal-1.16 "-Im4"
CDPATH="${ZSH_VERSION+.}:" && cd . && autoconf
 cd . && automake-1.16 --gnu
[b]configure.ac:11: error: required file './compile' not found
configure.ac:11:   'automake --add-missing' can install 'compile'
configure.ac:6: error: required file './missing' not found
configure.ac:6:   'automake --add-missing' can install 'missing'
Makefile.am: error: required file './depcomp' not found
Makefile.am:   'automake --add-missing' can install 'depcomp'[/b]
make: *** [Makefile:372: Makefile.in] Error 1
make: *** Waiting for unfinished jobs....

Re: RPM build failure: missing: No such file or directory

PostPosted: Jan 4th, '20, 17:13
by doktor5000
libtoolize deletes depcomp already before. If you replace %configure with %configure2_5x in the %build section then the build will complete just fine.

Re: RPM build failure: missing: No such file or directory

PostPosted: Jan 13th, '20, 18:34
by minfrin
Alas replacing %configure with %configure2_5x made the automake error go away, but this error remained:

Code: Select all
/bin/sh: ./build-aux/depcomp: No such file or directory


Is there a way to switch off the force-libtoolize behaviour?

Code: Select all
+ libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: You should add the contents of the following files to 'aclocal.m4':
libtoolize:   '/usr/share/aclocal/libtool.m4'
libtoolize:   '/usr/share/aclocal/ltoptions.m4'
libtoolize:   '/usr/share/aclocal/ltsugar.m4'
libtoolize:   '/usr/share/aclocal/ltversion.m4'
libtoolize:   '/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Remember to add 'LT_INIT' to configure.ac.
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.


Am I right in understanding that replacing %configure with %configure2_5x will fix the issue for Mageia, but break the spec file for everyone else (Fedora, SUSE, etc)?

Re: RPM build failure: missing: No such file or directory

PostPosted: Jan 14th, '20, 19:37
by doktor5000
That is interesting, because I rebuilt your src.rpm just fine after only replacing %configure with %configure2_5x
And %configure2_5x should also fix your error about depcomp.

Just for reference, this is what your .spec currently looks like, for the middle part ?

Code: Select all
%prep
%setup -q
rm -rf %{_builddir}/%{name}-%{version}/debian
%build
%configure2_5x
%make_build

%install
%make_install


minfrin wrote:Am I right in understanding that replacing %configure with %configure2_5x will fix the issue for Mageia, but break the spec file for everyone else (Fedora, SUSE, etc)?

Basically yes, as %configure2_5x is a Mageia-specific legacy thing, you would have to enclose it in conditionals that only evaluate to true for Mageia.

Re: RPM build failure: missing: No such file or directory

PostPosted: Jan 16th, '20, 11:36
by minfrin
What eventually worked for me was to disable libtoolize as follows in the spec file:

%define __libtoolize /bin/true

This switches off the "rebuild libtool" behaviour that keeps breaking the builds, and we are back to one spec file that works across all the COPR builds, including Mageia.

Re: RPM build failure: missing: No such file or directory

PostPosted: Jan 16th, '20, 12:27
by isadora
Would you please mark this topic [SOLVED]?
You can do so by editing the title/subject of the first message in the topic.
Place [SOLVED] in front of subject/title.

Thanks ahead. :)

Re: RPM build failure: missing: No such file or directory

PostPosted: Jan 20th, '20, 08:44
by minfrin
A quick heads up - the subject is arbitrarily length limited, so putting [SOLVED] in front sometimes isn't possible without altering the subject, which could alter the error message and make this difficult to google. Was able to work around it here.

Re: [SOLVED] RPM build fail: missing: No such file or direct

PostPosted: Jan 20th, '20, 09:25
by isadora
Well done minfrin. :)