From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34728@debbugs.gnu.org
Subject: [bug#34728] [PATCH] Update Wireshark to 3.0.0
Date: Tue, 12 Mar 2019 12:19:22 +0100 [thread overview]
Message-ID: <877ed4qr0l.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ef7dt7s0.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 11 Mar 2019 22:34:23 +0100")
Hello,
Thank you for the review.
Ludovic Courtès <ludo@gnu.org> writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> skribis:
>
>> + ;; "CMakeLists.txt" uses $ORIGIN, which seems to confuse
>> + ;; `validate-runpath' phase.
>> + ;;
>> + ;; Errors are like the following:
>> + ;; "/gnu/store/...wireshark-3.0.0/lib/wireshark/plugins/3.0/epan/ethercat.so:
>> + ;; error: depends on 'libwireshark.so.12', which cannot be found in
>> + ;; RUNPATH". That is, "/gnu/store/...wireshark-3.0.0./lib" doesn't
>> + ;; seem to belong to RUNPATH.
>
> What’s the RUNPATH on ethercat.so?
>
> readelf -a ethercat.so | grep RUNPATH
0x000000000000001d (RUNPATH) Bibliothèque runpath:[:/gnu/store/...-glibc-2.28/lib:/gnu/store/...-gcc-5.5.0-lib/lib:/gnu/store/...-glib-2.56.3/lib:/gnu/store/...-libpcap-1.9.0/lib:/gnu/store/...-libgcrypt-1.8.3/lib:/gnu/store/...-libgpg-error-1.32/lib:/gnu/store/...-gnutls-3.6.5/lib:/gnu/store/...-gcc-5.5.0-lib/lib/gcc/x86_64-unknown-linux-gnu/5.5.0/../../..]
> And where is libwireshark.so.12?
In "/gnu/store/...wireshark-3.0.0/lib".
I don't understand why this is getting removed.
> ‘validate-runpath’ does interpret $ORIGIN, but maybe there’s a but
> there.
Then my remark about $ORIGIN is wrong.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-03-12 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 10:03 [bug#34728] [PATCH] Update Wireshark to 3.0.0 Nicolas Goaziou
2019-03-11 21:34 ` Ludovic Courtès
2019-03-12 11:19 ` Nicolas Goaziou [this message]
2019-03-13 10:10 ` Ludovic Courtès
2019-03-13 11:33 ` bug#34728: " Nicolas Goaziou
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ed4qr0l.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=34728@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).