From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15634] New: fluidsynths refers to missing libgomp.so.1
Date: Sun, 18 Jun 2023 16:30:33 +0000 [thread overview]
Message-ID: <bug-15634-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15634
Bug ID: 15634
Summary: fluidsynths refers to missing libgomp.so.1
Product: buildroot
Version: 2023.05
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: stsp2@yandex.ru
CC: buildroot@uclibc.org
Target Milestone: ---
$ ldd /lib64/libfluidsynth.so
libgomp.so.1 => not found
<list of other deps that are not missing>
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-06-18 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 16:30 bugzilla [this message]
2023-06-18 19:36 ` [Buildroot] [Bug 15634] fluidsynths refers to missing libgomp.so.1 bugzilla
2023-06-18 19:47 ` bugzilla
2023-06-19 12:13 ` bugzilla
2023-06-19 16:05 ` bugzilla
2023-06-25 15:39 ` bugzilla
2023-08-31 14:43 ` bugzilla
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=bug-15634-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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