You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This involves an x86 generic full build of 18.02.
This seems less to be a problem directly involving packages, and more a
problem involving the integration of packages.
The builds were finishing up to this point.
In make menuconfig, I added in a few packages to replace the weaker
binutils version of these utilities, e.g., the less package, because I
wanted the search capability.
Apparently these additions got tangled up with boost, which was not at
this point selected:
cp -fpR -v /home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/boost_1_68_0/ipkg-install/lib/.{a,so} /home/stuff/code/openwrt/repo/tmp/stage-boost/usr/lib/
'/home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/boost_1_68_0/ipkg-install/lib/libboost_exception.a' -> '/home/stuff/code/openwrt/repo/tmp/stage-boost/usr/lib/libboost_exception.a'
cp: cannot stat '/home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/boost_1_68_0/ipkg-install/lib/.so': No such file or directory
I searched for the unusual string {a,so*} and found it in feeds/packages/libs/boost/Makefile
line 473.
Apparently boost was being pulled in, but not creating any .so* files, even though boost was not yet selected.
So I went into make menuconfig and selected boost. Same problem.
Then I split line 473 to this form: $(CP) -v $(PKG_INSTALL_DIR)/lib/.a $(1)/usr/lib/
-$(CP) -v $(PKG_INSTALL_DIR)/lib/.so* $(1)/usr/lib/
(It had been {a,so*}).
This (I think) will execute the same if boost is creating any .so files,
but will otherwise get past this step if no .so files are being created.
It seemed to work at first. But then (using make -j1) I started getting
complaints about the newly selected packages overwriting busybox versions of
files.
If you look more closely you will see that these errors wrote in the middle
of the string "Configuring boost."
CoCollected errors:
check_data_file_clashes: Package logger wants to install file /home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/root-x86/usr/bin/logger
But that file is already provided by package * busybox
opkg_install_cmd: Cannot install package logger.
check_data_file_clashes: Package findutils-find wants to install file /home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/root-x86/usr/bin/find
But that file is already provided by package * busybox
check_data_file_clashes: Package findutils-xargs wants to install file /home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/root-x86/usr/bin/xargs
But that file is already provided by package * busybox
check_data_file_clashes: Package less-wide wants to install file /home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/root-x86/bin/less
But that file is already provided by package * less
Note that busybox doesn't like having logger, find, and xargs overwritten,
but I also selected find and less, which should have overwritten busybox
versions of the files. But that didn't generate any complaints.
Here is where my memory gets a little hazy... I found out about this time that
menuconfig/boost was set to not install any libraries, so I selected 'all
libraries', and that may have gotten rid of the boost .so problem, because the
boost build was now creating .so files.
But I was still getting the file overwrite problem, so I yanked out the
offending package selections. At that point the make process completed.
Anyway, that's what happened.
The text was updated successfully, but these errors were encountered:
reallyohwell:
This involves an x86 generic full build of 18.02.
This seems less to be a problem directly involving packages, and more a
problem involving the integration of packages.
The builds were finishing up to this point.
In make menuconfig, I added in a few packages to replace the weaker
binutils version of these utilities, e.g., the less package, because I
wanted the search capability.
Apparently these additions got tangled up with boost, which was not at
this point selected:
cp -fpR -v /home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/boost_1_68_0/ipkg-install/lib/.{a,so} /home/stuff/code/openwrt/repo/tmp/stage-boost/usr/lib/
'/home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/boost_1_68_0/ipkg-install/lib/libboost_exception.a' -> '/home/stuff/code/openwrt/repo/tmp/stage-boost/usr/lib/libboost_exception.a'
cp: cannot stat '/home/stuff/code/openwrt/repo/build_dir/target-i386_pentium4_musl/boost_1_68_0/ipkg-install/lib/.so': No such file or directory
I searched for the unusual string {a,so*} and found it in feeds/packages/libs/boost/Makefile
line 473.
Apparently boost was being pulled in, but not creating any .so* files, even though boost was not yet selected.
So I went into make menuconfig and selected boost. Same problem.
Then I split line 473 to this form:
$(CP) -v $ (PKG_INSTALL_DIR)/lib/.a $(1)/usr/lib/
-$(CP) -v $(PKG_INSTALL_DIR)/lib/.so* $(1)/usr/lib/
(It had been {a,so*}).
This (I think) will execute the same if boost is creating any .so files,
but will otherwise get past this step if no .so files are being created.
It seemed to work at first. But then (using make -j1) I started getting
complaints about the newly selected packages overwriting busybox versions of
files.
If you look more closely you will see that these errors wrote in the middle
of the string "Configuring boost."
CoCollected errors:
But that file is already provided by package * busybox
But that file is already provided by package * busybox
But that file is already provided by package * busybox
But that file is already provided by package * less
nfiguring boost.
Note that busybox doesn't like having logger, find, and xargs overwritten,
but I also selected find and less, which should have overwritten busybox
versions of the files. But that didn't generate any complaints.
Here is where my memory gets a little hazy... I found out about this time that
menuconfig/boost was set to not install any libraries, so I selected 'all
libraries', and that may have gotten rid of the boost .so problem, because the
boost build was now creating .so files.
But I was still getting the file overwrite problem, so I yanked out the
offending package selections. At that point the make process completed.
Anyway, that's what happened.
The text was updated successfully, but these errors were encountered: