From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] bad_elf_symbols detected
Date: Wed, 7 Aug 2019 15:31:33 +0300
Message-ID: <20190807123133.GB4819@altlinux.org> (raw)
In-Reply-To: <20204361565161564@myt4-a1257bff88cb.qloud-c.yandex.net>
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
On Wed, Aug 07, 2019 at 10:06:04AM +0300, Скрылевъ Малъ wrote:
> Приветствую,
>
> я так разумею, что показанные ниже ошибки говорят о том что, откуда-то есть ссылки на несуществующее имя, как это проверить поместно (локально)?
>
> x86_64: NEW bad_elf_symbols detected:
> gem-oga-2.15-alt1.x86_64.rpm /usr/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0/oga-2.15/liboga.so U Init_liboga_xml_lexer
> i586: NEW bad_elf_symbols detected:
> gem-oga-2.15-alt1.i586.rpm /usr/lib/ruby/gems/2.5.0/extensions/x86-linux/2.5.0/oga-2.15/liboga.so U Init_liboga_xml_lexer
> aarch64: NEW bad_elf_symbols detected:
> gem-oga-2.15-alt1.aarch64.rpm /usr/lib/ruby/gems/2.5.0/extensions/aarch64-linux/2.5.0/oga-2.15/liboga.so U Init_liboga_xml_lexer
> ppc64le: NEW bad_elf_symbols detected:
> gem-oga-2.15-alt1.ppc64le.rpm /usr/lib/ruby/gems/2.5.0/extensions/powerpc64le-linux/2.5.0/oga-2.15/liboga.so U Init_liboga_xml_lexer
В каждом из /usr/lib/ruby/gems/2.5.0/extensions/*/2.5.0/oga-2.15/liboga.so
есть ссылка на несуществующий символ Init_liboga_xml_lexer.
Тот, кто посмотрит в лог сборки пакета gem-oga на x86_64-linux, увидит
verify-elf: WARNING: ./usr/lib/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0/oga-2.15/liboga.so: undefined symbol: Init_liboga_xml_lexer
Аналогичные предупреждения есть и на всех остальных архитектурах.
Логи сборки - ценный источник информации. Смотрите логи сборки!
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2019-08-07 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 7:06 Скрылевъ Малъ
2019-08-07 12:31 ` Dmitry V. Levin [this message]
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=20190807123133.GB4819@altlinux.org \
--to=ldv@altlinux.org \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git