dev March 2024

dev@openadk.org

2 participants
3 discussions

by Ingwie

Hello! I found an odd behaviour where pkgconf will not install it's shared library into the target root - although it is completely built: root@riscboi /n/o/openadk (master)# tar tvf firmware/generic-riscv64_musl/generic-riscv64-musl-archive+kernel.tar.xz | grep pkgconf -rwxr-xr-x root/root 26840 2024-03-12 01:59 usr/bin/pkgconf lrwxrwxrwx root/root 0 2024-03-12 01:59 usr/bin/pkg-config -> pkgconf drwxr-xr-x root/root 0 2024-03-12 04:09 usr/lib/pkgconfig/ -rw-r--r-- root/root 277 2024-03-12 03:38 usr/lib/pkgconfig/expat.pc -rw-r--r-- root/root 595 2024-03-12 01:26 usr/lib/pkgconfig/form.pc -rw-r--r-- root/root 245 2024-03-12 00:50 usr/lib/pkgconfig/gmp.pc -rw-r--r-- root/root 305 2024-03-12 01:39 usr/lib/pkgconfig/libarchive.pc -rw-r--r-- root/root 275 2024-03-12 01:17 usr/lib/pkgconfig/libcrypto.pc -rw-r--r-- root/root 1613 2024-03-12 01:21 usr/lib/pkgconfig/libcurl.pc -rw-r--r-- root/root 255 2024-03-12 03:33 usr/lib/pkgconfig/libelf.pc -rw-r--r-- root/root 378 2024-03-12 01:35 usr/lib/pkgconfig/liblzma.pc -rw-r--r-- root/root 296 2024-03-12 01:17 usr/lib/pkgconfig/libssl.pc -rw-r--r-- root/root 289 2024-03-12 01:17 usr/lib/pkgconfig/libtls.pc -rw-r--r-- root/root 456 2024-03-12 01:55 usr/lib/pkgconfig/libzstd.pc -rw-r--r-- root/root 595 2024-03-12 01:26 usr/lib/pkgconfig/menu.pc -rw-r--r-- root/root 272 2024-03-12 00:53 usr/lib/pkgconfig/mpfr.pc -rw-r--r-- root/root 595 2024-03-12 01:26 usr/lib/pkgconfig/ncurses.pc -rw-r--r-- root/root 251 2024-03-12 01:17 usr/lib/pkgconfig/openssl.pc -rw-r--r-- root/root 597 2024-03-12 01:26 usr/lib/pkgconfig/panel.pc -rw-r--r-- root/root 602 2024-03-12 01:26 usr/lib/pkgconfig/tinfo.pc -rw-r--r-- root/root 252 2024-03-12 01:06 usr/lib/pkgconfig/zlib.pc root@riscboi /n/o/openadk (master)# find root_generic-riscv64_musl/ -name "libpkgconf*" (no output) root@riscboi /n/o/openadk (master)# find build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/ -name "libpkgconf*" build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/include/pkgconf/libpkgconf build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/include/pkgconf/libpkgconf/libpkgconf.h build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/lib/libpkgconf.la build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/lib/libpkgconf.so build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/lib/pkgconfig/libpkgconf.pc build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/lib/libpkgconf.so.2.0.0 build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/lib/libpkgconf.so.2 What is odd though is that the pkgconf binary itself _is_ installed: # find root_generic-riscv64_musl/ build_generic-riscv64_musl/w-pkgconf-1.1.0-1/ -name pkgconf root_generic-riscv64_musl/usr/bin/pkgconf build_generic-riscv64_musl/w-pkgconf-1.1.0-1/pkgconf-1.1.0/.libs/pkgconf build_generic-riscv64_musl/w-pkgconf-1.1.0-1/pkgconf-1.1.0/pkgconf build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/bin/pkgconf build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/include/pkgconf build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/root/usr/share/doc/pkgconf build_generic-riscv64_musl/w-pkgconf-1.1.0-1/fake-riscv64/pkg-pkgconf/usr/bin/pkgconf And the package itself doesn't contain it either: # tar tvf firmware/generic-riscv64_musl/packages/pkgconf_1.1.0-1_riscv64.tar.xz drwxr-xr-x root/root 0 2024-03-12 08:42 ./ drwxr-xr-x root/root 0 2024-03-12 08:40 ./usr/ drwxr-xr-x root/root 0 2024-03-12 08:40 ./usr/bin/ lrwxrwxrwx root/root 0 2024-03-12 08:40 ./usr/bin/pkg-config -> pkgconf -rwxr-xr-x root/root 26840 2024-03-12 08:40 ./usr/bin/pkgconf Looking at the pkgconf-install target in package/pkgconf/Makefile shows that that library is never installed, causing the target system to run into numerous errors when trying to execute the tool. This is my current workaround. Not very elegant; but... it gets the job done. diff --git a/package/pkgconf/Makefile b/package/pkgconf/Makefile index cebfeb44d..640bce899 100644 --- a/package/pkgconf/Makefile +++ b/package/pkgconf/Makefile @@ -29,9 +29,13 @@ endif (cd $(STAGING_HOST_DIR)/usr/bin && ln -sf pkg-config $(GNU_TARGET_NAME)-pkg-config) pkgconf-install: - $(INSTALL_DIR) $(IDIR_PKGCONF)/usr/bin - $(INSTALL_BIN) $(WRKINST)/usr/bin/pkgconf \ - $(IDIR_PKGCONF)/usr/bin + for dir in bin lib include; do \ + $(INSTALL_DIR) $(IDIR_PKGCONF)/usr/$$dir; \ + find $(WRKINST)/usr/$$dir -type f \ + -exec ${INSTALL_BIN} "{}" "$(IDIR_PKGCONF)/usr/{}" \; ; \ + done + #$(INSTALL_BIN) $(WRKINST)/usr/bin/pkgconf \ + # $(IDIR_PKGCONF)/usr/bin (cd $(IDIR_PKGCONF)/usr/bin && ln -sf pkgconf pkg-config) include ${ADK_TOPDIR}/mk/host-bottom.mk Hope this'll be useful!

6 months, 1 week

Skip kernel building? (rootfs only mode)

by Ingwie

Hello there! This is a really simple one but I haven't been able to find it yet. Since there are various configurations in the tasks/ folder, I would like to know if it would be possible to make one, in which a kernel image is not built? Reason being that I am trying to construct a rootfs for a Docker container. So, a kernel is not needed - just the headers. Is that possible? Kind regards, Ingwie

6 months, 2 weeks

Re: [uclibc-ng-devel] Target GCC compiled via OpenADK can't find dl_iterate_phdr

by Waldemar Brodkorb

Hi Kevin, this might be better posted to the OpenADK mailinglist. > Hello there! > > Apologies if this is going into the wrong list, but I honestly was n't sure,e specially since this very issue was discussed a long time ago - found an exchange about this in the archive through Google - so I ended up just posting it here. > > I am currently building a toolset for RISC-V to use as a rootfs for a Docker Container that can then be used as a Jenkins agent to eventually build my way through Alpine's abuild/aports, so that I can reconstruct the alpine:3.19 image, but for RISC-V (there are only snapshots and the :edge image, right now). > > Most things built just fine; kernel, toolchain and alike. But when it tries to configure libatomic for the target, this happens: > > configure:14906: riscv64-openadk-linux-uclibc-cc -o conftest -g -O2 -g -Os -fno-sync-libcalls -pthread conftest.c >&5/nvme/opt/openadk/toolchain_generic-riscv64_uclibc-ng/usr/lib/gcc/riscv64-openadk-linux-uclibc/13.2.0/../../../../riscv64-openadk-linux-uclibc/bin/ld: /nvme/opt/openadk/toolchain_generic-riscv64_uclibc-ng/usr/lib/gcc/riscv64-openadk-linux-uclibc/13.2.0/libgcc.a(unwind-dw2-fde-dip.o): in function `_Unwind_Find_FDE': > (.text+0x1adc): undefined reference to `dl_iterate_phdr' > configure:14925: error: Pthreads are required to build libatomic > > I went and looked up what that function is, exactly, and learned quickly that this is caused by me having chosen a static build. That said, this was also already discussed: https://uclibc.uclibc.narkive.com/079V4ltx/dl-iterate-phdr-missing-in-libc > > So, I am at a loss on what to do right now. I changed my setting to also build dynamic objects, then cleaned uClibc-ng and rebuilt and then attempted again to let the normal build run. But, that too, did not help. > > My questions: > > - Is dl_iterate_phdr in libc.a? According to grep, it matches, but that doesn-ät mean much. > - I am using the 1.0.46 version of uClibc as openADK selects that. > - Is there anything I can do to fix this, or do I have to start over and just build with shared libraries? I honestly would not be surprised if GCC just didn#t want to be statically linked; static is the devil, after all. ;) > Do you have a OpenADK .config to check? But I think you might be right that you should build gcc with shared libraries supported. best regards Waldemar

6 months, 2 weeks

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

dev March 2024