slibtool: 5018e1a sox: 14.4.2_p20200803
14.4.2_p20200803
When building sox it fails.
rdlibtool --tag=CC --silent --mode=link x86_64-pc-linux-gnu-gcc -O2 -pipe -fstack-protector -Wall -Wmissing-prototypes -Wstrict-prototypes -fopenmp -avoid-version -module -Wl,-O1 -Wl,--as-needed -Wl,-z,defs -o sox sox.o libsox.la -lm x86_64-pc-linux-gnu-gcc: error: .libs/sox.o: No such file or directory rdlibtool: exec error upon slbt_exec_link_create_library(), line 1566: (see child process error messages). rdlibtool: < returned to > slbt_exec_link(), line 1957. make[1]: *** [Makefile:1571: sox] Error 2 make[1]: Leaving directory '/var/tmp/portage/media-sound/sox-14.4.2_p20200803/work/sox-code-50857c46c03a85c72826e819f5e815aad4a4633d/src' make: *** [Makefile:656: all-recursive] Error 1
In src/Makefile.am sox is defined.
src/Makefile.am
bin_PROGRAMS = sox EXTRA_PROGRAMS = example0 example1 example2 example3 example4 example5 example6 sox_sample_test lib_LTLIBRARIES = libsox.la include_HEADERS = sox.h sox_SOURCES = sox.c if HAVE_WIN32_GLOB sox_SOURCES += win32-glob.c win32-glob.h endif sox_LDADD = libsox.la
The missing .o object file exists in the main directory and not in .libs, but other programs like pkgconf also do not put their object files in the .libs directory and work just fine. In both cases the only object files in the .libs directory correspond to the library component, not the program.
.o
.libs
pkgconf
<img alt="sox-build.log" src="/cross/slibtool/issue/raw/files/1267d310a23a4e511a64ff1f58b8948b02e9b20393c0dacc1b9b8ddbd9742f2e-sox-build.log" />
This is really a sox bug, but it was worked around in slibtool here.
https://dev.midipix.org/cross/slibtool/c/d0714f62cb22b3967837174e0e9f6993273a23a7
Metadata Update from @orbea: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.