From: manneorama <manneorama@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NEEDS TESTERS] rpi-kernel: build a subpackage for each flavor, add rpi4
Date: Tue, 29 Dec 2020 11:53:48 +0100 [thread overview]
Message-ID: <20201229105348.h2CNzkpCY6kBeHwOmwyj8yldwtJp9uqAOAer-xIyKGU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26000@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2704 bytes --]
New comment by manneorama on void-packages repository
https://github.com/void-linux/void-packages/pull/26000#issuecomment-751984525
Comment:
Currently trying to test this rebased on top of the current void-packages master (on top of `f66d93e241420fbb17f8c1fffadf897bba676382` to be specific). Kernel package builds fine but during building of base-system I run into a strange error while building `elfutils`.
```
Making all in debuginfod
CXXLD debuginfod
/usr/bin/ld: ../libelf/libelf.so: undefined reference to symbol 'inflateEnd'
/usr/bin/ld: /lib64/libz.so.1: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:581: debuginfod] Error 1
make[1]: *** [Makefile:502: all-recursive] Error 1
make: *** [Makefile:418: all] Error 2
=> ERROR: elfutils-0.182_4: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/gnu-configure.sh:13
```
I'm not exactly sure where to start digging, but I will do my best. Any help is appreciated.
**UPDATE:**
Building `libelf` from master at `f66d93e241420fbb17f8c1fffadf897bba676382` works fine. ~~So there may be something in these two commits causing the issue.~~
**UPDATE 2:**
Building `libelf` standalone (`./xbps-src -a aarch64 pkg libelf`) works fine even from the rebased branch so I'm guessing this is because, as opposed to using `-N pkg base-system`, the standalone build will use upstream packages for dependency resolution instead of local ones?
**UPDATE 3:**
Manually adding `-lz` to `masterdir/builddir/elfutils-0.182/debuginfod/Makefile +475` hacks around the missing symbol above. But then new errors, related to `zstd` instead, appears.
```
Making all in debuginfod
CXXLD debuginfod
/usr/bin/ld: ../libdw/libdw.so: undefined reference to symbol 'ZSTD_decompressStream'
/usr/bin/ld: /lib64/libzstd.so.1: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:581: debuginfod] Error 1
make[1]: *** [Makefile:502: all-recursive] Error 1
make: *** [Makefile:418: all] Error 2
=> ERROR: elfutils-0.182_4: do_build: '${make_cmd} ${makejobs} ${make_build_args} ${make_build_target}' exited with 2
=> ERROR: in do_build() at common/build-style/gnu-configure.sh:19
```
I can't quickly hack around this because adding `-lzstd` the linker is unable to find the lib. Currently stuck.
As far as I can determine, all packages relevant to this issue define the correct dependencies. But I’m unsure how transitive deps are handled and where/how link flags and options are defined/inherited.
next prev parent reply other threads:[~2020-12-29 10:53 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 16:17 [PR PATCH] " Piraty
2020-10-31 16:27 ` [PR PATCH] [Updated] " Piraty
2020-10-31 16:36 ` Piraty
2020-11-06 23:34 ` [NEEDS TESTERS] " liketechnik
2020-11-16 3:32 ` [PR REVIEW] " agausmann
2020-11-16 3:34 ` agausmann
2020-11-16 3:36 ` agausmann
2020-11-16 3:57 ` agausmann
2020-11-16 3:58 ` agausmann
2020-11-16 3:59 ` agausmann
2020-11-17 9:10 ` [PR REVIEW] " Piraty
2020-11-22 18:23 ` Piraty
2020-11-22 19:48 ` Piraty
2020-11-22 20:58 ` agausmann
2020-12-29 7:49 ` manneorama
2020-12-29 7:59 ` manneorama
2020-12-29 8:10 ` manneorama
2020-12-29 9:03 ` manneorama
2020-12-29 9:48 ` manneorama
2020-12-29 10:53 ` manneorama [this message]
2020-12-31 1:42 ` [PR PATCH] [Updated] " Piraty
2021-01-03 23:08 ` manneorama
2021-01-05 9:36 ` Anachron
2021-01-05 19:48 ` LeamHall
2021-01-06 19:21 ` manneorama
2021-01-07 1:18 ` CMB
2021-01-07 2:04 ` LeamHall
2021-01-07 2:20 ` LeamHall
2021-01-11 0:24 ` [PR REVIEW] " ahesford
2021-01-11 2:02 ` ericonr
2021-01-11 2:02 ` ericonr
2021-01-11 2:57 ` jsumners
2021-01-11 3:17 ` ericonr
2021-01-11 3:51 ` jsumners
2021-01-11 4:14 ` ericonr
2021-01-11 5:04 ` ahesford
2021-01-11 11:19 ` Piraty
2021-01-11 11:21 ` Piraty
2021-01-11 11:25 ` Piraty
2021-01-11 13:17 ` ahesford
2021-01-11 13:20 ` ericonr
2021-01-12 20:19 ` [PR PATCH] [Updated] " Piraty
2021-01-13 2:42 ` [PR REVIEW] " ahesford
2021-01-16 22:38 ` CameronNemo
2021-01-16 23:36 ` [PR PATCH] [Updated] " Piraty
2021-01-16 23:37 ` [PR REVIEW] " Piraty
2021-01-16 23:49 ` Piraty
2021-01-16 23:49 ` Piraty
2021-01-17 0:22 ` [WIP] " ahesford
2021-01-18 9:44 ` [PR REVIEW] " Piraty
2021-01-18 21:48 ` ericonr
2021-01-23 17:30 ` Bridouz
2021-01-23 20:22 ` jsumners
2021-01-28 6:28 ` Bridouz
2021-02-05 10:20 ` paper42
2021-02-10 19:03 ` jsav0
2021-02-11 19:45 ` [PR PATCH] [Updated] " Piraty
2021-02-11 20:01 ` [PR PATCH] [Updated] [WIP] rpi-kernel: split into flavor packages, " Piraty
2021-02-11 20:03 ` Piraty
2021-02-12 18:15 ` Piraty
2021-04-27 19:43 ` [WIP] rpi-kernel: build flavor subpackages, " Piraty
2021-04-27 19:43 ` [PR PATCH] [Closed]: " Piraty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201229105348.h2CNzkpCY6kBeHwOmwyj8yldwtJp9uqAOAer-xIyKGU@z \
--to=manneorama@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).